QuestionQ5

Resilient Cloud Solutions

A DevOps engineer manages a Java-based application running in an Amazon Elastic Container Service (Amazon ECS) cluster on AWS Fargate. Auto scaling is not configured for the application.

The DevOps engineer has identified the Java Virtual Machine (JVM) thread count as a good indicator for when the application should scale. The application serves customer traffic on port 8080 and exposes JVM metrics on port 9404.

Application usage has recently increased. The DevOps engineer must configure auto scaling for the application.

Which solution meets these requirements with the LEAST operational overhead?

Choose two
Explanation

Amazon ECS Service Auto Scaling uses CloudWatch metrics. JVM thread count can be collected by the CloudWatch agent and used either with CloudWatch alarms and a step scaling policy or as a custom CloudWatch metric for a target tracking policy. Target tracking automatically creates and manages the associated CloudWatch alarms. Amazon Managed Service for Prometheus is a Prometheus-compatible metrics store and query service; its metrics and rules are not direct ECS Application Auto Scaling metric targets. ECS service auto scaling, Application Auto Scaling target tracking, CloudWatch JVM metrics

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!