An enterprise manages a multi-account AWS environment under a single organization in AWS Organizations with consolidated billing. The architecture includes the following workloads running 24/7:
| Workload | Current Configuration | CloudWatch CPU Utilization | CloudWatch Memory Utilization |
|---|---|---|---|
| ECS Fargate Tasks (Account A) | tasks across AZs; vCPU, RAM per task | Average: , Peak: | Average: , Peak: |
| EC2 Instances (Account B) | instances of `m6i.xlarge` ( vCPU, RAM) in an ASG across AZs | Average: , Peak: | Average: , Peak: |
| AWS Lambda (Account A) | requests/month; memory, avg duration | N/A | N/A |
Outbound traffic to the internet from the Fargate tasks in Account A is routed through a dedicated NAT Gateway in each of the Availability Zones. The company requires maximum cost optimization across all compute and network resources while maintaining high availability with no single points of failure, and ensuring that no workloads experience performance degradation or out-of-memory errors under peak loads.
Which of the following strategies should a Solutions Architect recommend to achieve the most cost-effective architecture?
- Right-size the ECS Fargate tasks in Account A to vCPU and RAM. Right-size the EC2 instances in Account B to `m6i.large`. Maintain the NAT Gateways in Account A. Purchase a single Compute Savings Plan at the AWS Organizations management account level.Cevap
- BRight-size the ECS Fargate tasks in Account A to vCPU and RAM. Right-size the EC2 instances in Account B to `m6i.large`. Decommission two NAT Gateways in Account A and route all outbound traffic through a single NAT Gateway in one Availability Zone. Purchase a single Compute Savings Plan at the AWS Organizations management account level.
- CRight-size the ECS Fargate tasks in Account A to vCPU and RAM. Right-size the EC2 instances in Account B to `m6i.large`. Maintain the NAT Gateways in Account A. Purchase an EC2 Instance Savings Plan for the `m6i` family at the AWS Organizations management account level to cover the EC2 instances, and purchase a Compute Savings Plan in member Account A to cover the Fargate and Lambda workloads.
- DRight-size the ECS Fargate tasks in Account A to vCPU and RAM. Right-size the EC2 instances in Account B to `m6i.large`. Share the NAT Gateways in Account B's VPC with Account A's VPC using AWS Resource Access Manager (RAM) to eliminate NAT Gateway hourly charges in Account A. Purchase a single Compute Savings Plan at the AWS Organizations management account level.
Cevap
Right-size the ECS Fargate tasks in Account A to vCPU and RAM. Right-size the EC2 instances in Account B to `m6i.large`. Maintain the NAT Gateways in Account A. Purchase a single Compute Savings Plan at the AWS Organizations management account level.
The correct strategy combines precise right-sizing with organizational-level financial planning. Sizing the Fargate tasks to and RAM meets the peak memory requirement of , preventing OOM crashes, while `m6i.large` matches the peak memory of the EC2 instances. Buying a Compute Savings Plan at the AWS Organizations management level covers Fargate, Lambda, and EC2 workloads across all accounts and ensures flexibility. Keeping NAT Gateways ensures high availability without cross-AZ data transfer charges.
Adım Adım Çözüm
Anahtar Kavram
Multi-account cost optimization requires a combination of precise performance-based right-sizing (ensuring headroom for peak utilization without OOM), high-availability networking design, and selecting Compute Savings Plans at the AWS Organizations management level for dynamic sharing.