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 7, Creating ECS Clusters


  1. False – EC2 autoscaling groups only support dynamic IP addressing.
  2. The Base64 encoding.
  3. Use the AWS::Region pseudo-parameter.
  4. False – the Ref intrinsic function can refer to both resources and parameters in a CloudFormation template.
  5. You need to first run cfn-init to download the CloudFormation Init metadata, and then cfn-signal to notify CloudFormation the result of running cfn-init.
  6. You need to ensure that you are writing the name of the ECS cluster that each instance should join to /etc/ecs/ecs.config in the UserData script – for example, echo "ECS_CLUSTER=<cluster-name>" > /etc/ecs/ecs.config.
  1. False – this command is only used to create stacks.  You should use the aws cloudformation deploy command to create and update stacks as required.
  2. The ECS agent on each instance cannot communicate with the ECS service API, which at the time of writing is only available as a public endpoint.