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 11, Managing the ECS Infrastructure Life Cycle


  1. False – you are responsible for invoking and managing ECS container-instance draining.
  2. EC2_INSTANCE_LAUNCHING and EC2_INSTANCE_TERMINATING.
  3. ABANDON or CONTINUE.
  1. False – you can publish life cycle hooks to SNS, SQS, or CloudWatch Events.
  2. It is likely that your Lambda function is failing due to reaching the maximum function-execution timeout of 5 minutes, meaning the life cycle hook will never complete and eventually times out. You should ensure your Lambda function republishes the life cycle hook if the function execution-timeout is about to be reached, which will automatically re-invoke your function.
  3. You should configure the UpdatePolicy attribute.
  4. Set the MinSuccessfulInstancesPercent property to 100.
  5. A Lambda permission.