QuestionQ10

VerifiedResilient Cloud Solutions

A company operates an application in an Amazon Elastic Container Service (Amazon ECS) service using the AWS Fargate launch type. The application consumes messages from an Amazon Simple Queue Service (Amazon SQS) queue. It can take several minutes for the application to process each queue message. While processing a message, the application reads a file from an Amazon S3 bucket and processes the file’s data. The application writes the processed output to a second S3 bucket. The company uses Amazon CloudWatch Logs to monitor processing errors and confirm that the application processes messages successfully.

The SQS queue generally receives a low message volume. Occasionally, however, the queue receives larger message volumes. A DevOps engineer must implement a solution that reduces the processing time for message bursts.

Which solution meets this requirement in the MOST cost-effective manner?

Explanation

For asynchronous job processors, queue depth is the appropriate scaling signal because an increasing queue indicates that pending work exceeds processing capacity. Registering the ECS service as an Application Auto Scaling target and applying target tracking to an SQS queue-depth CloudWatch metric increases the number of concurrent Fargate tasks during bursts and reduces it when demand subsides, avoiding continuously provisioned EC2 capacity. Optimizing Amazon ECS service auto scaling

Learn more

Community Discussion

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