Designing a custom Amazon Machine Image
Before you learn how to build a custom Amazon Machine Image, it is important to understand why you would want or need to build your own custom image.
The reasons for this vary depending on your use case or organizational requirements, however in general there are a number of reasons why you might want to build a custom image:
- Custom storage configuration: The default ECS-optimized AMI ships with a 30 GB volume that includes 8 GB for the operating system partition and a 22 GB volume for storing Docker images and container filesystems. One aspect of your configuration that I typically recommend to change is that, by default, Docker volumes, which do not use layered filesystems, are stored on the 8 GB operating system partition. This approach generally should be avoided for production use cases, and instead you should mount a dedicated volume for storing Docker volumes.
- Installation of additional packages and tools: In keeping with the minimalist philosophy...
