A media company hosts a containerized video transcoding application on AWS Fargate. The transcoding tasks require a steady-state baseline of 12 tasks running 24/7, and scale up to 50 tasks during peak evening hours. The application's metadata database runs on Amazon RDS for MySQL and requires continuous 24/7 operation. Which combination of purchasing strategies will minimize compute costs while ensuring the application meets its availability requirements? (Select TWO.)
- Purchase a Compute Savings Plan to cover the baseline capacity of the AWS Fargate tasks.Cevap
- Purchase Amazon RDS Reserved Instances for the MySQL database.Cevap
- CPurchase a single Compute Savings Plan to cover both the AWS Fargate tasks and the Amazon RDS MySQL database.
- DMigrate the 24/7 video transcoding service from AWS Fargate to AWS Lambda to eliminate baseline compute costs.
- EUse On-Demand capacity for the baseline AWS Fargate tasks and purchase a Compute Savings Plan to cover the Amazon RDS MySQL database.
Cevap
Purchase a Compute Savings Plan to cover the baseline capacity of the AWS Fargate tasks, and purchase Amazon RDS Reserved Instances for the MySQL database.
To minimize compute costs for a 24/7 baseline containerized workload on AWS Fargate, purchasing a Compute Savings Plan is the most effective approach. For the database tier running on Amazon RDS that also operates 24/7, purchasing Amazon RDS Reserved Instances provides the necessary discount. Together, these two strategies minimize the steady-state baseline costs of both compute components.
Adım Adım Çözüm
Anahtar Kavram
Selecting cost-optimized purchasing options (Savings Plans and Reserved Instances) for heterogeneous AWS workloads.