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 10, Isolating Network Access


  1. True.
  2. You can use either the awsvpc (recommended) or host networking mode, which ensure your containers will obtain an IP address from the attached EC2 instance Elastic Network Interface (ENI).
  3. False – the awsvpc network mode is required for ECS task networking.
  4. You need to ensure the security groups configured for your ECS service permit access from the load-balancers.
  5. You enable ECS task networking for an ECS task definition, however your containers fail on startup with an error that states they are unable to reach a location that is located on the internet. How can you resolve this issue?
  6. Two – see https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI.
  7. One – a t2.micro supports a maximum of two ENIs, however, one ENI must be reserved for operating-system and ECS-agent communications.  Task-networking only allows a single task definition per ENI.
  8. 10 – given you can have a maximum of 1 ECS task definition running in task-networking mode (see previous answer) and you can run up to 10 containers in a single ECS task definition (see https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service_limits.html).
  9. You must use the IP target type when using the awsvpc network mode.
  10. You should remove the loadBalancers property from the ECS service definition.