Question

Difficulty: MediumCost-Optimized Compute Selection and Purchasing Strategies

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?

  1. 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
  2. B
    Purchase a Compute Savings Plan to cover both the Amazon ECS on AWS Fargate tasks and the Amazon RDS database.
  3. C
    Migrate the continuous ingestion service to AWS Lambda, and purchase a Compute Savings Plan to cover the Lambda functions and the Amazon RDS database.
  4. D
    Purchase 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

1
Analyze the compute requirements for the ingestion service.
The ingestion service runs continuously 24/7 on Amazon ECS with AWS Fargate.
Identifying the hosting model and runtime profile helps determine the correct savings plan type.
2
Select the appropriate purchasing option for AWS Fargate.
Select Compute Savings Plans because they apply to Fargate (unlike EC2 Instance Savings Plans or EC2 Reserved Instances).
Compute Savings Plans offer up to 66% savings on EC2, Fargate, and Lambda usage.
3
Identify the database hosting model and purchasing options.
The database runs continuously on Amazon RDS for MySQL, which requires RDS Reserved Instances for reservation discounts.
Compute Savings Plans do not cover database engines like Amazon RDS.

Key Concept

Applying different AWS purchasing models to compute and database resources depending on their compatibility and scope.
Rate this question