A company runs a microservices application across multiple AWS accounts managed under AWS Organizations. The application's compute resources consist entirely of AWS Fargate tasks and AWS Lambda functions. To reduce costs, the company wants to commit to a consistent amount of compute usage.
Which strategy should a solutions architect recommend to optimize the compute costs of this serverless architecture?
- Purchase Compute Savings Plans in the organization's management account.Answer
- BPurchase EC2 Instance Savings Plans in the organization's management account.
- CShare existing EC2 Reserved Instances across accounts using AWS Resource Access Manager (RAM) without enabling sharing within the organization.
- DConsolidate all outbound traffic through a single NAT Gateway in a shared services VPC and disable Multi-AZ NAT redundancy.
Answer
Purchase Compute Savings Plans in the organization's management account.
Compute Savings Plans provide the most flexibility and automatically apply to compute usage across Amazon EC2, AWS Fargate, and AWS Lambda regardless of instance family, size, Availability Zone, region, or operating system. Purchasing them at the AWS Organizations management account level ensures the discounts are shared across all consolidated member accounts.
Step-by-Step Solution
Key Concept
Compute Savings Plans for Serverless Workloads