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
Packt Upsell

Chapter 14. Fargate and ECS Service Discovery

So far in this book, we have spent a considerable amount of time focused on building infrastructure that supports your ECS clusters, detailing how to build custom Amazon machine images for your ECS container instances and how to create EC2 Auto Scaling groups that can dynamically add or remove ECS container instances to your ECS cluster, with chapters dedicated to managing the life cycle and capacity of your clusters.

Imagine not having to worry about ECS clusters and ECS container instances. Imagine that somebody else managed them for you, to the extent that you didn't even really know they existed. For some use cases, having a strong level of control over hardware selection, storage configuration, security posture, and other infrastructure related concerns, is very important; by now, you should have a pretty strong understanding of exactly how ECS provides such capabilities. However, in many cases, having that level of control is not necessary...