Soru

Zorluk: Çok zorOptimizing Resource Costs and Sizing

An enterprise runs a multi-tenant SaaS application across multiple member accounts in an AWS Organization with consolidated billing enabled. The application architecture consists of:

* A stateless web tier hosted on Amazon ECS on AWS Fargate across three Availability Zones (AZs) that scales dynamically based on request traffic.
* A legacy queue-processing worker tier running 24/7 on a fleet of 100100 `c6i.2xlarge` EC2 instances (88 vCPUs, 1616 GiB RAM) across three AZs. The application is compiled for x86 architecture and cannot be ported to Graviton due to legacy dependency constraints.
* A batch processing tier utilizing AWS Lambda functions triggered by objects uploaded to Amazon S3.
* Network infrastructure where outbound internet traffic, including data transferred to Amazon S3 and Amazon DynamoDB, is routed through a NAT Gateway in each AZ.

AWS Compute Optimizer and Amazon CloudWatch metrics for the worker tier over the last 30 days show:

* Average CPU utilization is 15%15\%, with a maximum peak of 28%28\%.
* Average memory utilization is 72%72\%, with a maximum peak of 84%84\%.

The Solutions Architect must optimize the infrastructure costs over a 3-year period. The solution must minimize operational management overhead, maintain the high availability SLA across three AZs, and deliver the highest cost savings.

Which combination of actions should the Solutions Architect recommend?

  1. Right-size the EC2 worker tier instances to `m6i.xlarge` (44 vCPUs, 1616 GiB RAM). Create VPC Gateway Endpoints for Amazon S3 and Amazon DynamoDB in the route tables of all VPCs. Purchase a 3-year Compute Savings Plan at the Organization's management account level.Cevap
  2. B
    Right-size the EC2 worker tier instances to `m6i.xlarge` (44 vCPUs, 1616 GiB RAM). Create VPC Gateway Endpoints for Amazon S3 and Amazon DynamoDB. Purchase a 3-year EC2 Instance Savings Plan for the `c6i` family in the management account, and purchase a 3-year Compute Savings Plan to cover Fargate and Lambda.
  3. C
    Right-size the EC2 worker tier instances to `m6i.xlarge` (44 vCPUs, 1616 GiB RAM). Consolidate outbound traffic by deploying a single NAT Gateway in one AZ to replace the multi-AZ NAT Gateways, routing all public and S3/DynamoDB traffic through it. Purchase a 3-year Compute Savings Plan at the management account level.
  4. D
    Right-size the EC2 worker tier instances to `m6i.xlarge` (44 vCPUs, 1616 GiB RAM). Create VPC Gateway Endpoints for Amazon S3 and Amazon DynamoDB. Purchase a 3-year EC2 Instance Savings Plan for the `m6i` family in the management account, and use AWS Resource Access Manager (RAM) to share the savings plan with the member accounts.

Cevap

Right-size the EC2 worker tier instances to m6i.xlarge, create VPC Gateway Endpoints for Amazon S3 and Amazon DynamoDB, and purchase a 3-year Compute Savings Plan at the Organization's management account level.
The correct answer combines proper right-sizing, cost-effective routing, and a flexible commitment model. Moving from `c6i.2xlarge` to `m6i.xlarge` maintains the necessary 1616 GiB RAM to satisfy the 84%84\% peak memory footprint while decreasing the vCPU count from 88 to 44, which is still sufficient to handle the 28%28\% peak CPU demand (equivalent to 2.242.24 vCPUs). Creating VPC Gateway Endpoints for S3 and DynamoDB is a free architectural modification that stops these services from routing traffic through NAT Gateways, eliminating data processing fees. Finally, purchasing a 3-year Compute Savings Plan at the management account level applies discounts to all EC2 instances, ECS Fargate tasks, and Lambda functions across all member accounts, providing the lowest risk and highest discount coverage.

Adım Adım Çözüm

1
Analyze EC2 utilization metrics to determine the right-sizing target.
The current instances are `c6i.2xlarge` (88 vCPUs, 1616 GiB RAM). Peak CPU utilization is 28%28\% (2.242.24 vCPUs) and peak memory utilization is 84%84\% (13.4413.44 GiB). Since memory must be maintained above 13.4413.44 GiB and CPU needs are low, migrating to `m6i.xlarge` (44 vCPUs, 1616 GiB RAM) meets all resource demands while reducing instance size by 50%50\%.
To optimize costs, instances must be right-sized based on the bottleneck dimension (memory) while ensuring sufficient CPU capacity.
2
Evaluate network data transfer and processing charges.
Traffic to Amazon S3 and DynamoDB is currently routed through NAT Gateways, incurring data processing charges of $0.045 per GB. Implementing free VPC Gateway Endpoints for S3 and DynamoDB bypasses the NAT Gateways entirely for this traffic, reducing network charges without affecting availability.
NAT Gateway processing fees are a common source of high data transfer costs that can be mitigated for free using VPC endpoints.
3
Determine the optimal Savings Plan strategy for a multi-account organization with diverse compute workloads.
The workload consists of EC2, ECS on Fargate, and AWS Lambda. A Compute Savings Plan applies automatically to all three of these compute services across all member accounts within the Organization. Purchasing this at the management account level ensures consolidated application of discount rates.
Compute Savings Plans offer the highest flexibility and cover Fargate and Lambda, unlike EC2 Instance Savings Plans which only cover EC2 and are bound to specific families.

Anahtar Kavram

Compute resource optimization requires right-sizing instances based on performance bottlenecks, minimizing network data processing costs via VPC endpoints, and leveraging the flexibility of Compute Savings Plans for heterogeneous compute architectures.
Bu soruyu puanla