Soru

Zorluk: Çok zorReserved Instances and Savings Plans Optimization

An organization uses AWS Organizations with consolidated billing enabled. The SysOps administrator is tasked with optimizing costs for the following steady-state resources over the next 12 months using 1-year, No Upfront commitments:

* Account A:
* 10 Linux `m5.2xlarge` EC2 instances in `us-east-1` running 24/7. These instances will be upgraded to `m6i.2xlarge` in 3 months.
* An Amazon ECS on AWS Fargate workload in `us-east-1` with a constant cost of 3.50perhour.AccountB:Abaselineof4Linuxc5.xlargeEC2instancesinuseast1running24/7,whichwillremainunchanged.AnAWSLambdaworkloadinuswest2withaconstantcostof3.50 per hour. * **Account B**: * A baseline of 4 Linux `c5.xlarge` EC2 instances in `us-east-1` running 24/7, which will remain unchanged. * An AWS Lambda workload in `us-west-2` with a constant cost of 1.50 per hour.

Which commitment strategy provides the highest overall cost savings while meeting the operational flexibility requirements?

  1. Purchase a 1-year EC2 Instance Savings Plan for the c5 family in us-east-1 in Account B, and purchase a 1-year Compute Savings Plan in Account A to cover the m5/m6i instances, Fargate workload, and Lambda workload.Cevap
  2. B
    Purchase a 1-year EC2 Instance Savings Plan for the m5 family in us-east-1 in Account A, a 1-year EC2 Instance Savings Plan for the c5 family in us-east-1 in Account B, and a 1-year Compute Savings Plan to cover Fargate and Lambda.
  3. C
    Purchase a 1-year Compute Savings Plan in Account A to cover the m5/m6i instances and Fargate workload, and a 1-year Compute Savings Plan in Account B to cover the c5 instances and Lambda workload.
  4. D
    Purchase 1-year Standard Reserved Instances for the m5.2xlarge instances in Account A, and a 1-year Compute Savings Plan in Account B to cover the c5 instances, Fargate workload, and Lambda workload.

Cevap

Purchase a 1-year EC2 Instance Savings Plan for the c5 family in us-east-1 in Account B, and purchase a 1-year Compute Savings Plan in Account A to cover the m5/m6i instances, Fargate workload, and Lambda workload.
The correct strategy leverages the higher discount rates of EC2 Instance Savings Plans for the stable c5 workload that is not expected to change, while using the flexibility of Compute Savings Plans for the m5 workload that will migrate to the m6i family. Furthermore, Fargate and Lambda compute types are only eligible for Compute Savings Plans, and consolidated billing ensures the unused commitment from Account A is shared with Account B's Lambda workload.

Adım Adım Çözüm

1
Analyze the flexibility needs of the EC2 instances in Account A.
Determine that since the instances will migrate from m5 to m6i within 3 months, any family-locked commitment (like Standard RIs or EC2 Instance Savings Plans) will become invalid after the migration.
A Compute Savings Plan is required for the Account A instances to ensure the discount applies to both m5 and m6i families.
2
Analyze the workload characteristics of the c5 instances in Account B.
Determine that the baseline of 4 c5.xlarge instances is stable and will not change family or region over the 1-year term.
An EC2 Instance Savings Plan is the most cost-effective choice for stable, single-family workloads because it offers higher discount rates than Compute Savings Plans.
3
Determine the coverage for the Fargate and Lambda workloads.
Fargate and Lambda are only eligible for Compute Savings Plans; they cannot be covered by EC2 Instance Savings Plans or Reserved Instances.
A Compute Savings Plan must be sized to cover the Fargate and Lambda workloads in addition to the migrating EC2 instances.
4
Evaluate consolidated billing sharing dynamics.
Confirm that the Compute Savings Plan purchased in Account A will first apply to Account A's usage, and any remaining commitment will automatically flow to Account B's Lambda workload.
AWS consolidated billing ensures that unused Savings Plans commitments are shared across all linked accounts in the organization, preventing waste.

Anahtar Kavram

Reserved Instances and Savings Plans Optimization
Bu soruyu puanla