A logistics company runs a fleet tracking application on AWS. The application consists of a backend data ingestion service deployed on Amazon ECS with AWS Fargate, which runs continuously 24/7 to process telemetry from vehicles. The application also uses an Amazon RDS for MySQL database to store tracking history. A solutions architect needs to recommend a purchasing strategy to minimize the costs of both Fargate and RDS, while maintaining the required availability. Which combination of purchasing options will achieve this goal most cost-effectively?
- Purchase a Compute Savings Plan to cover the Amazon ECS on AWS Fargate tasks, and purchase an Amazon RDS Reserved Instance for the database.Answer
- BPurchase a Compute Savings Plan to cover both the Amazon ECS on AWS Fargate tasks and the Amazon RDS database.
- CMigrate the continuous ingestion service to AWS Lambda, and purchase a Compute Savings Plan to cover the Lambda functions and the Amazon RDS database.
- DPurchase an EC2 Instance Savings Plan to cover the Amazon ECS on AWS Fargate tasks, and purchase an Amazon RDS Reserved Instance for the database.
Answer
Purchase a Compute Savings Plan to cover the Fargate tasks and an Amazon RDS Reserved Instance for the database.
The correct option combines a Compute Savings Plan to cover the AWS Fargate tasks (as Compute Savings Plans are the only plans that apply to Fargate) with an Amazon RDS Reserved Instance to cover the 24/7 database workload. This represents the most cost-effective combination of commitment-based discounts for the described services.
Step-by-Step Solution
Key Concept
Applying different AWS purchasing models to compute and database resources depending on their compatibility and scope.