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 14, Fargate and ECS Service Discovery


  1. True.
  2. Only the awsvpc networking mode is supported.
  3. False – you must ensure the ECS agent can communicate via the ENI allocated to your Fargate ECS task.
  4. You need to ensure the IAM role referenced by the ExecutionRoleArn property of the task definition permits access to the ECR repository.
  5. No – Fargate only supports CloudWatch logs.  
  6. False – ECS service discovery uses Route53 zones to publish service-registration information.
  7. A service discovery namespace.
  8. You must configure a supported CPU/memory configuration when configuring Fargate ECS task definitions.  See https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-cpu-memory-error.html for supported configurations.
  9. UDP Port 2000.
  10. False – traces must be published to an X-Ray daemon running in your environment.