What should a solutions architect recommend?

By:
In: SAA-C02
Tagged:
With: 1 Comment
A company is launching a new application deployed on an Amazon Elastic Container Service (Amazon ECS) cluster and is using the Fargate launch type for ECS tasks.The company is monitoring CPU and memory usage because it is expecting high traffic to the application upon its launch.However, the company wants to reduce costs when utilization decreases.

What should a solutions architect recommend?

Use Amazon EC2 Auto Scaling to scale at certain periods based on previous traffic patterns.

Use an AWS Lambda function to scale Amazon ECS based on metric breaches that trigger an Amazon CloudWatch alarm.

Use Amazon EC2 Auto Scaling with simple scaling policies to scale when ECS metric breaches trigger an Amazon CloudWatch alarm.

Use AWS Application Auto Scaling with target tracking policies to scale when ECS metric breaches trigger an Amazon CloudWatch alarm.

Explanations:

Amazon EC2 Auto Scaling is used for EC2 instances, not Fargate tasks. Fargate is serverless, so EC2 Auto Scaling is not applicable for scaling ECS tasks.

While Lambda can trigger scaling actions, it’s not the recommended approach for scaling ECS tasks. AWS services like Application Auto Scaling are more suited for this task.

EC2 Auto Scaling is not applicable to ECS with Fargate tasks, as they do not run on EC2 instances directly. It is meant for EC2-based instances.

AWS Application Auto Scaling with target tracking policies is designed for dynamically scaling ECS tasks based on CloudWatch metrics, which is ideal for Fargate deployments.

2025-10-13

1 Comment

  1. Jerry
    Author

    I weigh that the answer is:
    Use AWS Application Auto Scaling with target tracking policies to scale when ECS metric breaches trigger an Amazon CloudWatch alarm.

Leave a Reply

Your email address will not be published. Required fields are marked *

18 + 17 =