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

Creating a continuous integration pipeline using CodePipeline


Now that you have established the prerequisites for supporting CodeBuild, you can create a continuous integration CodePipeline pipeline that will use CodeBuild to test, build, and publish your Docker image. Continuous integration focuses on continuously merging application source code changes into your master branch and validating the changes by creating a build and running automated tests against it. 

As per the first diagram in this chapter, this generally involves two stages when you configure a CodePipeline pipeline for continuous integration:

  • Source Stage: Downloads the source application repository and makes it available for subsequent stages. For our use case, you will connect CodePipeline to the master branch of your GitHub repository, and subsequent commits to this repository will automatically trigger a new pipeline execution.
  • Build Stage: Runs the build, test, and publish workflow defined in the source application repository...