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 (20 chapters)

Summary


In this chapter, you successfully deployed the sample Docker application to AWS using ECS. You learned how to define key supporting application and infrastructure resources, including how to create an application database using the AWS RDS service, and how to integrate your ECS applications with application load balancers provided by the AWS Elastic Load Balancing service.

With these supporting resources in place, you learned how to create ECS task definitions that control the runtime configuration of your containers, and then deployed instances of your ECS task definitions to your ECS cluster by creating an ECS service for the sample application. You learned how an ECS task definition can define volumes and multiple container definitions, and you used this capability to create a separate non-essential container definition that always runs whenever your ECS task definition is deployed and generates static web files for the sample application. You also integrated the ECS service for...