Skip to content

Commit 240e691

Browse files
fix 208
"We strongly recommend that you use target tracking scaling policies to scale on metrics like average CPU utilization or average request count per target." Source: https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html
1 parent 5d9e38f commit 240e691

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2437,10 +2437,10 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
24372437

24382438
### A Developer has an e-commerce API hosted on Amazon ECS. Variable and spiking demand on the application is causing order processing to take too long. The application processes Amazon SQS queues. The ApproximateNumberOfMessagesVisible metric spikes at very high values throughout the day, which cause Amazon CloudWatch alarm breaches. Other ECS metrics for the API containers are well within limits. What can the Developer implement to improve performance while keeping costs low?
24392439

2440-
- [ ] Target tracking scaling policy.
2440+
- [x] Target tracking scaling policy.
24412441
- [ ] Docker Swarm.
24422442
- [ ] Service scheduler.
2443-
- [x] Step scaling policy.
2443+
- [ ] Step scaling policy.
24442444

24452445
**[⬆ Back to Top](#table-of-contents)**
24462446

0 commit comments

Comments
 (0)