A company runs a combination of Amazon EC2 instances and AWS Lambda functions for its applications. The finance team wants to reduce costs by making a commitment to a consistent amount of compute usage (measured in dollars per hour) for a 1-year term. The team wants the flexibility to change instance families, sizes, and AWS regions, and also wants the commitment to cover both EC2 and Lambda usage. Which AWS pricing option should the team purchase?
Compute Savings Plans offer the broadest flexibility among AWS savings plans, applying automatically to EC2, Lambda, and Fargate usage across any instance family, region, or operating system. This makes them the ideal choice for a team running a heterogeneous mix of EC2 instances and serverless workloads, as the same hourly commitment covers all compute usage. By committing to a consistent dollar amount per hour (typically 1 or 3 years), the team achieves significant discounts without being locked to a specific instance type or size.
Why this answer
Compute Savings Plans provide the required flexibility to change instance families, sizes, and AWS regions, and they automatically apply to both EC2 and Lambda usage. This plan offers a discounted hourly rate in exchange for a 1-year commitment to a consistent amount of compute spend (measured in dollars per hour), making it the only option that meets all the stated requirements.
Exam trap
The trap here is that candidates often confuse Compute Savings Plans with EC2 Instance Savings Plans, mistakenly thinking the latter offers the same flexibility, but EC2 Instance Savings Plans are restricted to a single instance family and do not cover Lambda or Fargate.
Why the other options are wrong
EC2 Instance Savings Plans apply only to EC2 instance usage, not to Lambda functions, and they require commitment to a specific instance family in a region, lacking the flexibility to change instance families, sizes, or regions.
Reserved Instances require a commitment to a specific instance family and region, and they do not cover Lambda usage. The question demands flexibility across instance families, sizes, regions, and coverage of both EC2 and Lambda.
Spot Instances are not a pricing commitment option; they are spare compute capacity offered at variable discounts with potential interruptions, and they cannot cover Lambda usage or provide a consistent dollar-per-hour commitment.