Book Image

Docker on Amazon Web Services

By : Justin Menga
Book Image

Docker on Amazon Web Services

By: Justin Menga

Overview of this book

Over the last few years, Docker has been the gold standard for building and distributing container applications. Amazon Web Services (AWS) is a leader in public cloud computing, and was the first to offer a managed container platform in the form of the Elastic Container Service (ECS). Docker on Amazon Web Services starts with the basics of containers, Docker, and AWS, before teaching you how to install Docker on your local machine and establish access to your AWS account. You'll then dig deeper into the ECS, a native container management platform provided by AWS that simplifies management and operation of your Docker clusters and applications for no additional cost. Once you have got to grips with the basics, you'll solve key operational challenges, including secrets management and auto-scaling your infrastructure and applications. You'll explore alternative strategies for deploying and running your Docker applications on AWS, including Fargate and ECS Service Discovery, Elastic Beanstalk, Docker Swarm and Elastic Kubernetes Service (EKS). In addition to this, there will be a strong focus on adopting an Infrastructure as Code (IaC) approach using AWS CloudFormation. By the end of this book, you'll not only understand how to run Docker on AWS, but also be able to build real-world, secure, and scalable container platforms in the cloud.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Chapter 12, ECS Auto Scaling


  1. False – you are responsible for autoscaling your ECS container instances.
  2. EC2 autoscaling.
  3. Application Auto Scaling.
  4. Configure the memoryReservation parameter with a value of 300 and the memory parameter with a value of 1,024 .
  5. Divide the ECS container-instance CPU-unit allocation evenly across each ECS task (that is, configure each task with a CPU allocation of 333 units).
  6. True.
  7. Three.
  8. You should disable autoscaling during rolling updates. You can do this by configuring the AutoScalingRollingUpdate.SuspendProcesses property of the CloudFormation UpdatePolicy attribute.
  9. Zero tasks – based upon the current state of the cluster, one ECS task is running on each instance.  Given each task has a static port mapping to TCP port 80, you cannot schedule another task as all ports are in use.
  10. Four – you should use the worst-case scenario of 500 MB memory per container.