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

Summary


In this chapter, you learned how to increase the network isolation and security of your Docker applications using ECS task networking. ECS task networking changes the default out-of-the-box Docker bridge and NAT network configuration to a model where each ECS task receives its own dedicated elastic network interface or ENI. This means that your Docker applications are assigned their own dedicated security groups and can be accessed directly via their published ports, which avoids the need to implement features, such as dynamic port mapping, that can affect performance and require more permissive security rules to work. ECS task networking, however, does come with its own set of challenges and limitations, which include a more complex network topology to accommodate the current private IP address-only restrictions, and the ability to only run a single ECS task per ENI.

ECS task networking currently does not support public IP addresses, which means you must provide a NAT gateway or...