Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Amazon Fargate Quick Start Guide

You're reading from   Amazon Fargate Quick Start Guide Learn how to use AWS Fargate to run containers with ease

Arrow left icon
Product type Paperback
Published in Jul 2018
Publisher Packt
ISBN-13 9781789345018
Length 190 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Deepak Vohra Deepak Vohra
Author Profile Icon Deepak Vohra
Deepak Vohra
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
1. Getting Started with Amazon ECS and Amazon Fargate FREE CHAPTER 2. Networking 3. Using CloudWatch Logs 4. Using Auto Scaling 5. Using IAM 6. Using an Application Load Balancer 7. Using Amazon ECS CLI 1. Other Books You May Enjoy Index

Updating auto scaling policy 


The auto scaling policy only scales the number of running (desired) tasks and does not modify the auto scaling policy, which is still set to a range of 1-5 tasks. The service may be updated to modify any or all of the minimum number of tasks, desired count, maximum number of tasks, and scaling action for auto scaling. In this section, we shall discuss updating the auto scaling configuration:

  • Click on Update for the service as before. The Desired number of tasks is set to 5, as shown here, when auto scaling is performed:
  • Reduce the Desired number of tasks to 3, as shown here
  • To modify the scaling policy, click on the AutoScaler link, as shown here:
  • In Edit policy, select Use an existing policy and select the AutoScaleBasedOnCPUUtilization policy. The scaling action does not have to be performed when the alarm threshold is breached. Modify the scaling action to Add1tasks when 0.9<=CPUUtilization, as shown here. The alarm threshold is CPUUtilization> 0.1 for...
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 $15.99/month. Cancel anytime
Visually different images