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

Deploying ECS services


Now that you have successfully created an ECS service, let's examine how ECS manages new deployments of container applications. It is important to understand that ECS task definitions are immutable—that is, you cannot modify a task definition once it has been created, and instead you need to either create a completely new task definition or create a revision of your current task definition, which you can think of as a new version of a given task definition.

ECS defines the logical name of an ECS task definition as the family, and a given revision of an ECS task definition is expressed in the form family:revision—for example, my-task-definition:3 refers to revision 3 from the my-task-definition family.

This means that in order to deploy a new version of a container application, you need to perform a couple of steps:

  1. Create a new revision of your ECS task definition with configuration settings that have been changed for the new version of your application. This often will...