Question

Difficulty: Very hardReserved Instances and Savings Plans Optimization

A company has a single-account high-performance data processing environment. The environment consists of the following workloads in the us-east-1 Region:

- An Auto Scaling group of EC2 instances running r6i.2xlarger6i.2xlarge (Intel-based) that scales dynamically between 44 and 1616 instances depending on queue depth.
- AWS Lambda functions performing preprocessing tasks with a steady daily average consumption of 80,00080,000 GB-seconds.
- AWS Fargate tasks running on Amazon ECS using the c6gc6g (Graviton2-based) architecture, consuming a constant 88 vCPUs and 1616 GB of memory.

The development team plans to upgrade the Fargate tasks to c7gc7g (Graviton3-based) architecture within the next 9090 days. The EC2 instance family (r6ir6i) will remain unchanged for the next 1212 months.

Which TWO purchase options should a SysOps administrator combine to achieve the maximum cost savings for these workloads with the least operational overhead? (Select TWO.)

  1. An EC2 Instance Savings Plan for the r6ir6i instance family in the us-east-1 RegionAnswer
  2. A Compute Savings Plan to cover the AWS Fargate tasks and AWS Lambda functionsAnswer
  3. C
    An EC2 Instance Savings Plan for the c6gc6g instance family in the us-east-1 Region to cover the Fargate tasks
  4. D
    A 1-year Standard Regional Reserved Instance for r6i.2xlarger6i.2xlarge instances to cover the EC2 fleet
  5. E
    A 1-year Amazon ECS Savings Plan to cover both the Fargate tasks and the Lambda functions

Answer

The SysOps administrator should purchase an EC2 Instance Savings Plan for the r6ir6i instance family in the us-east-1 Region to cover the EC2 instances, and a Compute Savings Plan to cover the AWS Fargate tasks and AWS Lambda functions.
The correct strategy combines an EC2 Instance Savings Plan for the stable r6ir6i EC2 instance family and a Compute Savings Plan for the Fargate and Lambda workloads. EC2 Instance Savings Plans offer the highest discount rates (similar to Standard RIs) for a specific family within a region, and they automatically apply to any instance size or OS within that family, which perfectly matches the scaling behavior of the Auto Scaling group. For the Fargate and Lambda workloads, a Compute Savings Plan is the correct choice because it is the only Savings Plan type that covers Fargate and Lambda, and its flexibility allows the Fargate tasks to migrate from the c6gc6g to the c7gc7g family without losing the discount.

Step-by-Step Solution

1
Analyze the EC2 instances requirements
The EC2 instances run on a stable family (r6ir6i) in a single region (us-east-1) but scale dynamically from 44 to 1616 instances. To maximize savings and cover scaling without manual modification overhead, an EC2 Instance Savings Plan for the r6ir6i family is chosen over RIs or Compute Savings Plans.
EC2 Instance Savings Plans offer up to 72% savings (matching Standard RIs) and automatically apply to any instance size, OS, or tenancy within the specified family, making them ideal for scaling groups within a single family.
2
Analyze the Fargate tasks and Lambda requirements
The Fargate tasks are scheduled to migrate from c6gc6g to c7gc7g architecture within 9090 days, and the Lambda functions run regularly. A Compute Savings Plan is selected to cover both workloads.
Compute Savings Plans are the only plan type that covers Fargate and Lambda. Their flexibility allows changes in instance family (c6gc6g to c7gc7g), region, or compute type while maintaining cost savings.
3
Combine the purchase options
Combine the r6ir6i EC2 Instance Savings Plan with a Compute Savings Plan.
This combination maximizes the discount for the stable EC2 fleet (using the higher-discount EC2 Instance Savings Plan) while preserving full flexibility for the evolving Fargate and Lambda workloads (using the Compute Savings Plan).

Key Concept

Selecting the optimal combination of Savings Plans (EC2 Instance vs. Compute) based on workload stability, scaling requirements, instance family migrations, and service compatibility (EC2 vs. Fargate vs. Lambda).
Rate this question