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

Questions


  1. True/false: When you use ECS and deploy your own ECS container instances, ECS automatically scales your clusters up and down for you.
  2. Which AWS service do you use to scale your ECS clusters?
  3. Which AWS service do you use to scale your ECS services?
  4. Your application requires a minimum of 300 MB and maximum of 1 GB of memory to run. What parameters would you configure on your ECS task definition to support this configuration? 
  5. You deploy 3 different ECS tasks that each run a different application to a single instance ECS cluster, and configure each ECS task to reserve 10 CPU units. During busy periods, one of the ECS tasks hogs CPU, slowing down the other ECS tasks. Assuming the ECS container instance has 1,000 CPU units' capacity, what could you do to avoid one ECS task hogging CPU?
  6. True/false: If you only use dynamic port mapping for your ECS tasks, you do not need to worry about network port resources.
  7. You deploy an instance to AWS that supports four network interfaces in total. What...