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

Configuring ECS task networking


Now that you have established networking infrastructure that will support the private IP addressing requirement of ECS task networking, you can proceed to configure ECS task networking on your ECS resources. This requires the following configurations and considerations:

  • You must configure your ECS task definitions and ECS services to support ECS task networking.
  • The network mode of your task definition must be set to awsvpc.
  • An elastic network interface used for ECS task networking can only have one ECS task associated with it. Depending on your ECS instance type, this will limit the maximum number of ECS tasks you can run in any given ECS container instance.
  • Deployment of ECS tasks with ECS task-networking-configured takes longer than traditional ECS deployments, as an elastic network interface needs to be created and bound to your ECS container instance.
  • Because your container applications have a dedicated network interface, dynamic port mapping is no longer...