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

Customizing Elastic Beanstalk applications


As discussed in the previous section, we need to add an ebextension, which is simply a configuration file that can be used to customize your Elastic Beanstalk environment to our existing Elastic Beanstalk application.  This is an important concept to understand, as we will ultimately use this same approach to resolve all of the issues that our application currently has.

To configure ebextensions, you first need to create a folder called .ebextensions in the eb folder where you are currently storing your Dockerrun.aws.json file (note that you will need to disconnect from the SSH session, go to your Elastic Beanstalk EC2 instance, and perform this in your local environment):

todobackend/eb> mkdir .ebextensions
todobackend/eb> touch .ebextensions/init.config

Each file with a .config extension in the .ebextensions folder will be treated as an ebextension and processed by Elastic Beanstalk during an application deployment. In the preceding example...