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


In this chapter, you created an end-to-end continuous delivery pipeline that automatically tests, builds, and publishes Docker images for your application, continuously deploys new application changes into a non-production environment, and allows you to perform controlled releases into production that generate change sets and require manual approval before deployment to production can commence.

You learned how to integrate your GitHub repositories with CodePipeline by defining them as source actions in a source stage, and then created a build stage that used CodeBuild to test, build, and publish Docker images for your application. You added a build specification to the todobackend repository, which CodeBuild uses to execute your builds, and you created a custom CodeBuild container that was able to run Docker in Docker, to allow you to build a Docker image and perform integration and acceptance tests in a Docker Compose environment. 

Next, you created a deploy stage in CodePipeline...