Search code examples
dockeramazon-ec2amazon-ami

Which AMI to Select (Sever 2016 Base or Server 2016 Base with Containers)


I am creating a new EC2 instance in AWS. As I am new to this, i am confused with the AMI.

Current Usage:

  • General Purpose web server
  • Hosting Web API (.net 4.6.2)

Future Needs

  • Need to support .net core as I am planning to migrate the Web API to core
  • Planning to integrate CI/CD with AWS Code pipeline

Environment Selected

  • Instace Type : m5 large

When i check AMI t select i have 2 options:

  • Microsoft Windows Server 2016 Base (I think 2016 is enough)
  • Microsoft Windows Server 2016 Base with Containers

I am confused here. I understood that later have docker containers. But i didn't get the advantage on that in the server. I am planning to learn docker. But as of now, i need your quick help to continue. As i specified, the application may need docker for the build server while configure with Code pipeline.

Please suggest the best option and the needs of that added feature


Solution

  • If you are interested in Docker and plan to run Docker on ECS then you should choose ECS-Optimized Windows Server Amazon Machine Image.

    As far you Future Needs it does not depend on AMI but you container do depend on AMI.

    This week, we’re adding support for running production workloads in Windows containers using Amazon Elastic Container Service (Amazon ECS). Now, Amazon ECS provides an ECS-Optimized Windows Server Amazon Machine Image (AMI). This AMI is based on the EC2 Windows Server 2016 AMI, and includes Docker 17.06 Enterprise Edition and the ECS Agent 1.16. This AMI provides improved instance and container launch time performance. It’s based on Windows Server 2016 Datacenter and includes Docker 17.06.2-ee-5, along with a new version of the ECS agent that now runs as a native Windows service.

    This will help to maintain your ECS services in future also have some advantage over Microsoft Windows Server 2016 Base with out ECS optimized.

    • The ECS agent ran as a process that made it difficult to monitor and manage. As a service, the agent can be health-checked, managed, and restarted no differently than other Windows services.

    • The AMI also includes pre-cached images for Windows Server Core 2016 and Windows Server Nano Server 2016. By caching the images in the AMI, launching new Windows containers is significantly faster

    • The Windows-compatible ECS-optimized AMI also reports CPU and memory utilization and reservation metrics to Amazon CloudWatch.

    You can explore more about here