Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Docker on Amazon Web Services
  • Toc
  • feedback
Docker on Amazon Web Services

Docker on Amazon Web Services

By : Justin Menga
4.2 (5)
close
Docker on Amazon Web Services

Docker on Amazon Web Services

4.2 (5)
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)
close

Deploying and testing Auto Scaling life cycle hooks

You can now deploy your complete Auto Scaling life cycle hooks solution using the aws cloudformation deploy command as demonstrated earlier in this chapter.

Once deployment is complete, to test life cycle management is working as expected, a simple change you can perform to force replacement of the current ECS container instance in your ECS cluster is to revert the AMI change you made earlier in this chapter:

ApplicationDesiredCount=1
ApplicationImageId=ami-ec957491
ApplicationImageTag=5fdbe62
ApplicationSubnets=subnet-a5d3ecee,subnet-324e246f
VpcId=vpc-f8233a80
Reverting the ECS AMI

Once you now deploy this change, again using the  aws cloudformation deploy command as demonstrated in earlier example, next switch to the CloudFormation console and when the event to terminate the existing EC2 instance is raised, quickly...

bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete