Soru

Zorluk: ZorReserved Instances and Savings Plans Optimization

A company manages a multi-account environment using AWS Organizations with consolidated billing. The workloads are distributed as follows:
- The production account runs a steady-state fleet of Amazon EC2 m6i.large instances.
- The staging account runs microservices on Amazon ECS with AWS Fargate.
- The analytics account runs batch processing using AWS Lambda functions.

The SysOps administrator must implement a cost optimization strategy that achieves the maximum possible savings across Fargate, Lambda, and EC2 workloads while allowing the EC2 instance families to be changed in the future. Which of the following actions should the SysOps administrator take to meet these requirements? (Select TWO.)

  1. Purchase a Compute Savings Plan to cover the Fargate, Lambda, and EC2 workloads.Cevap
  2. Ensure that Savings Plan sharing is enabled in the billing preferences of the Organizations management account.Cevap
  3. C
    Purchase an EC2 Instance Savings Plan for the m6i instance family to cover both the EC2 instances and the Fargate tasks.
  4. D
    Purchase Standard Reserved Instances at the management account level to cover the Lambda functions.
  5. E
    Purchase Regional Reserved Instances for the Fargate tasks to cover their steady-state run time.

Cevap

Purchase a Compute Savings Plan to cover all three workloads, and ensure that Savings Plan sharing is enabled in the Organizations billing preferences.
The correct options are to purchase a Compute Savings Plan and ensure Savings Plan sharing is enabled. Compute Savings Plans are the only commitment discount type that covers Amazon EC2, AWS Fargate, and AWS Lambda simultaneously. Enabling sharing across AWS Organizations ensures that the commitment applies to workloads running in the staging and analytics member accounts, maximizing overall savings.

Adım Adım Çözüm

1
Analyze the workload requirements and resource types.
Identify that the workloads span EC2 instances, AWS Fargate, and AWS Lambda across different accounts in an AWS Organization.
Understanding the resource mix determines which Savings Plans or Reserved Instances are eligible.
2
Evaluate the eligibility of each service for commitment-based discounts.
Confirm that Compute Savings Plans cover EC2, Fargate, and Lambda, whereas EC2 Instance Savings Plans and Reserved Instances do not apply to Fargate or Lambda.
This narrows down the eligible purchase options to satisfy the requirement of covering all three workloads.
3
Select the correct Savings Plan type that supports flexibility.
Choose a Compute Savings Plan because it allows changing EC2 instance families in the future, unlike standard Reserved Instances or EC2 Instance Savings Plans which limit flexibility.
The scenario requires maintaining the ability to change EC2 instance families.
4
Configure the organization-wide sharing of the Savings Plan benefits.
Ensure that Savings Plan sharing is active in the management account's preferences so that the staging and analytics accounts can utilize the purchased commitment.
By default, consolidated billing shares benefits, but if sharing is disabled, the member accounts running Fargate and Lambda will not receive the discounted rates.

Anahtar Kavram

Compute Savings Plans offer the greatest flexibility and automatically apply across EC2, Fargate, and Lambda, even across multiple accounts in an AWS Organization when sharing is enabled.
Bu soruyu puanla