A media processing company is building a system to process daily video transcoding workloads. The architecture includes a continuous, steady-state orchestration queue worker that runs on Amazon ECS Fargate, and a highly variable fleet of transcoding workers running containerized tasks to process jobs from an Amazon SQS queue. Each transcoding job takes between to minutes to complete, can be safely interrupted and retried from the start, and must be completed within hours of submission. The transcoding tasks retrieve source videos from an Amazon S3 bucket and write the output back to the same bucket. Which combination of purchasing strategies and compute configurations will meet these requirements MOST cost-effectively? (Select TWO.)
- Purchase a -year Compute Savings Plan to cover the baseline usage of the orchestration queue worker running on Amazon ECS Fargate.Answer
- Run the transcoding worker tasks on Amazon ECS Fargate using the Fargate Spot capacity provider.Answer
- CPurchase a -year Compute Savings Plan to cover both the orchestration queue worker and the application's Amazon RDS database instances.
- DDeploy the transcoding worker logic as AWS Lambda functions configured with maximum timeout to continuously poll and process the SQS queue.
- EProvision a NAT Gateway in the VPC to route the data transfer of source videos and transcoded files between the private ECS container instances and Amazon S3.
Answer
Purchasing a Compute Savings Plan for the orchestration worker and using Fargate Spot for the transcoding tasks provides the most cost-optimized solution.
The correct combination involves purchasing a Compute Savings Plan to cover the predictable, steady-state orchestration worker running on ECS Fargate, and running the variable, interruptible video transcoding tasks on ECS Fargate using the Fargate Spot capacity provider to leverage deep discounts.
Step-by-Step Solution
Key Concept
Selecting cost-optimized AWS compute models requires matching steady-state workloads to Savings Plans/Reserved Instances and matching interruptible, flexible workloads to Spot instances.