Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Docker on Amazon Web Services

You're reading from   Docker on Amazon Web Services Build, deploy, and manage your container applications at scale

Arrow left icon
Product type Paperback
Published in Aug 2018
Publisher Packt
ISBN-13 9781788626507
Length 822 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Justin Menga Justin Menga
Author Profile Icon Justin Menga
Justin Menga
Arrow right icon
View More author details
Toc

Table of Contents (20) Chapters Close

Preface 1. Container and Docker Fundamentals FREE CHAPTER 2. Building Applications Using Docker 3. Getting Started with AWS 4. Introduction to ECS 5. Publishing Docker Images Using ECR 6. Building Custom ECS Container Instances 7. Creating ECS Clusters 8. Deploying Applications Using ECS 9. Managing Secrets 10. Isolating Network Access 11. Managing ECS Infrastructure Life Cycle 12. ECS Auto Scaling 13. Continuously Delivering ECS Applications 14. Fargate and ECS Service Discovery 15. Elastic Beanstalk 16. Docker Swarm in AWS 17. Elastic Kubernetes Service 18. Assessments 19. Other Books You May Enjoy

Chapter 12, ECS Auto Scaling

  1. False – you are responsible for autoscaling your ECS container instances.
  2. EC2 autoscaling.
  3. Application Auto Scaling.
  4. Configure the memoryReservation parameter with a value of 300 and the memory parameter with a value of 1,024 .
  5. Divide the ECS container-instance CPU-unit allocation evenly across each ECS task (that is, configure each task with a CPU allocation of 333 units).
  6. True.
  7. Three.
  8. You should disable autoscaling during rolling updates. You can do this by configuring the AutoScalingRollingUpdate.SuspendProcesses property of the CloudFormation UpdatePolicy attribute.
  9. Zero tasks – based upon the current state of the cluster, one ECS task is running on each instance.  Given each task has a static port mapping to TCP port 80, you cannot schedule another task as all ports are in use.
  10. Four – you should use...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image