Examkin

Question

Difficulty: HardReserved Instances and Savings Plans Optimization

A company manages a multi-account AWS environment using AWS Organizations with consolidated billing enabled. The environment has two member accounts:

* Account A (Production) runs a steady-state web application on Amazon EC2 m6i.largem6i.large instances and Amazon ECS on AWS Fargate.
* Account B (Testing) runs temporary development workloads using various EC2 instance families (such as t3t3 and c6gc6g) that are frequently stopped, started, or terminated.

The company wants to optimize its compute costs. The SysOps administrator must ensure that the commitment discount is applied to both the Fargate tasks and the EC2 instances in Account A as a priority, and is not consumed by the fluctuating workloads in Account B.

Which strategy should the SysOps administrator implement to meet these requirements?

  1. Purchase a Compute Savings Plan in Account A.Answer
  2. B
    Purchase an EC2 Instance Savings Plan in Account A.
  3. C
    Purchase a Compute Savings Plan in the Management Account.
  4. D
    Purchase Regional Reserved Instances for m6im6i instances in Account A.

Answer

Purchase a Compute Savings Plan in Account A.
Purchasing a Compute Savings Plan in Account A is correct because Compute Savings Plans apply to compute usage across Amazon EC2, AWS Fargate, and AWS Lambda. Additionally, in an AWS Organization with consolidated billing, Savings Plan discounts are applied first to the account that purchased the plan. Buying the plan in Account A ensures that Account A's steady-state EC2 and Fargate workloads receive the discount first, with any excess sharing to other accounts like Account B.

Step-by-Step Solution

1
Identify the compute resource types in the production workload.
Account A runs both Amazon EC2 instances and AWS Fargate tasks.
EC2 Instance Savings Plans and Reserved Instances only apply to EC2 instances, meaning Fargate usage would remain at On-Demand rates. A Compute Savings Plan is required to cover both services under a single commitment.
2
Determine the optimal account for purchasing the Savings Plan.
Purchase the Compute Savings Plan directly within Account A.
AWS billing consolidated billing logic applies Savings Plan discounts to the purchasing account's usage first. If purchased in the Management Account, the discount is distributed across the organization based on where it yields the highest discount, which could cause Account B's testing workloads to consume the commitment first.
3
Confirm sharing behavior for any excess commitment.
Enable Savings Plan sharing across the Organization.
Buying the plan in Account A prioritizes Account A's usage. If Account A has periods of lower usage, any excess commitment can still automatically scale to cover Account B's eligible workloads, maximizing the investment.

Key Concept

AWS Savings Plans application order and scope in consolidated billing environments.
Rate this question

Topics

Reserved Instances and Savings Plans Optimization

More questions from this topic