Cloud concept · Updated

Right-Sizing - Right-sizing is matching cloud resource types, configurations, and capacity to workload requirements without unnecessary cost or unacceptable performance risk.

In short

Right-sizing uses observed demand and application requirements to choose appropriate compute, memory, storage, and throughput capacity. It reduces waste while preserving performance and reliability, and it requires regular review as workloads change.

Cloud Concepts Hub →

6 key aspects of Right-Sizing

Effective right-sizing combines measured demand, appropriate resource selection, service-level safeguards, and repeated validation to reduce waste without impairing workloads.

01
Evidence-based capacity selection

Use utilization metrics and application performance indicators from representative operating periods. Include peak demand and failure conditions rather than relying only on averages.

02
Multidimensional resource fit

Evaluate CPU, memory, storage capacity, storage performance, and network limits independently. A workload may need a different resource family rather than a smaller version of its current configuration.

03
Balanced cost and service objectives

Remove unnecessary capacity while preserving latency, throughput, availability, and recovery requirements. Retain headroom when it has a measurable operational purpose.

04
Continuous reassessment

Review sizing as traffic patterns, software, and data volumes change. Combine periodic reviews with monitoring that detects sustained waste or resource pressure.

05
Controlled implementation

Validate recommendations through testing and staged deployment. Account for restart requirements, maintenance windows, and rollback before changing production resources.

06
Distinct from scaling and discounts

Automatic scaling adjusts capacity over time, while right-sizing establishes an appropriate resource configuration. Pricing commitments can complement right-sizing but do not correct an unsuitable configuration.

Cloud services for Right-Sizing

CloudWatch supplies utilization and application signals, while Compute Optimizer turns supported resource telemetry into sizing recommendations. Engineers validate those recommendations and adjust EC2 instance configurations or RDS database capacity, accounting for compatibility, maintenance windows, and service objectives. EC2 Auto Scaling then helps an appropriately configured fleet respond to changing demand. These services support a repeated process of measuring, recommending, testing, changing, and observing; neither a recommendation nor an automatic scaling policy guarantees that a workload is correctly sized.

AWS Compute OptimizerAWS Compute Optimizer

Analyzes utilization and configuration data to recommend changes for supported resources, including Amazon EC2 instances. Treat its recommendations as candidates to validate against application requirements, peak demand, and operational constraints.

Amazon CloudWatchAmazon CloudWatch

Provides metrics, dashboards, and alarms for evaluating utilization and validating sizing changes. Guest operating system memory utilization on EC2 generally requires the CloudWatch agent or another custom metric collection mechanism rather than default EC2 metrics.

Amazon EC2Amazon EC2

Offers instance families and sizes with different compute, memory, storage, and networking characteristics. Right-sizing can involve changing instance size or family, subject to compatibility checks and any required stop/start or replacement procedure.

Amazon RDSAmazon RDS

Provides database instance classes and storage settings that can be adjusted to workload requirements. Evaluate database load, memory, connections, and storage performance together, and account for availability effects during modifications.

Amazon EC2 Auto ScalingAmazon EC2 Auto Scaling

Adjusts the number of EC2 instances in a group according to configured policies and demand. It complements right-sizing by varying fleet capacity, but the instance configurations and minimum capacity still need appropriate sizing.

Right-Sizing exam questions

Real practice exam questions on Right-Sizing, with the correct answer and its explanation. Answer them with every option in the exam simulator.

AIB-C01 (beta)

A distribution company hosts an AI inventory assistant on an Amazon SageMaker AI real-time endpoint. The endpoint runs 12 identical instances continuously because warehouse employees submit a predictable surge of requests at the start of each shift. Each surge lasts 20 minutes. Representative load tests confirm that 12 instances are required during surges and two instances meet all performance and availability requirements between surges. New instances take approximately 10 minutes to become ready, and requests must receive immediate responses without queuing. The instance type and model must remain unchanged. Which plan should the business strategist recommend to reduce unused capacity while meeting these requirements?

Show answerCORRECT ANSWER

Schedule capacity increases early enough for 12 instances to be ready before each shift surge, return to two instances afterward, and regularly review demand and performance.

This plan matches instance count to demonstrated demand while accounting for startup time. It preserves peak performance and the tested availability baseline, removes unnecessary capacity between surges, and includes ongoing review as demand changes.

MLA-C02 (beta)

A company plans to deploy a PyTorch model on an Amazon SageMaker AI real-time endpoint. The ML engineer has identified several compatible CPU and GPU inference instance types but does not know which provides the best price-performance.

The company has representative inference payloads and a required load-test profile consisting of a gradual traffic increase followed by a sustained peak. The selected configuration must maintain p95 model latency below 100 milliseconds at the required peak request rate. The engineer must automate benchmarking of the candidate instance types with this traffic profile and compare the costs of configurations that satisfy the performance requirements. The company does not want to build or maintain a custom load-generation framework.

Which approach best meets these requirements?

Show answerCORRECT ANSWER

Run an advanced SageMaker Inference Recommender job with the candidate instance types, representative payloads, custom traffic phases, and performance thresholds. Compare costs among configurations that meet the peak throughput and p95 latency requirements.

Advanced Inference Recommender jobs support customized load tests, including candidate endpoint configurations, traffic patterns, and performance thresholds. This enables workload-specific instance comparisons without maintaining a custom load generator. Cost should be compared only among configurations that meet the required throughput and latency.

SAP-C03

A company operates a fleet of Amazon EC2 workers that process large scientific datasets. Each worker requires 6 TiB of scratch storage on a single Amazon EBS data volume. The workload performs large, sequential reads and writes continuously for 18 hours each day. Testing establishes a requirement for sustained throughput of 300 MiB/s, including performance headroom. The solution must not depend on accumulated burst credits. HDD latency is acceptable, and the data can be regenerated if necessary.

Each EC2 instance supports sustained EBS throughput of 1,000 MiB/s. The application generates enough concurrent I/O to achieve the required throughput. On SSD volumes, the workload requires no more than 3,000 EBS IOPS.

In the company's AWS Region, st1 storage costs $0.045 per GiB-month. gp3 storage costs $0.08 per GiB-month, including 3,000 IOPS and 125 MiB/s of throughput. Additional gp3 throughput costs $0.04 per MiB/s-month. The company uses On-Demand pricing without discounts.

Which proposed configuration meets the requirements at the LOWEST monthly EBS cost per worker?

Show answerCORRECT ANSWER

Use one 8 TiB st1 volume.

st1 provides baseline throughput of 40 MiB/s per TiB, so an 8 TiB volume provides 320 MiB/s without relying on burst credits. It meets the capacity and sustained-throughput requirements for $368.64 per month (8 × 1,024 × $0.045), less than the qualifying gp3 configuration. Paying for extra HDD capacity is cheaper here than using SSD storage with additional provisioned throughput.

Practice Right-Sizing in a full exam

Questions on Right-Sizing in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Right-Sizing

2 min read

Right-sizing means selecting resources that fit a workload rather than simply choosing the smallest or cheapest option. An appropriately sized resource provides enough processing power, memory, storage performance, and network capacity to meet business requirements, with justified headroom for demand variation and failures. Both overprovisioning and underprovisioning are sizing problems: one wastes money, while the other can cause slow responses, failed jobs, or outages.

In the AWS Well-Architected Framework, right-sizing is most directly associated with Cost Optimization when the goal is eliminating unnecessary resource spending. It also supports Performance Efficiency by matching resource types and configurations to workload needs. The distinction depends on the outcome emphasized in a question: reducing the cost of an oversized instance points to Cost Optimization, while selecting the most suitable compute or storage technology points to Performance Efficiency. Reducing unnecessary resource consumption also supports Sustainability. Reliability concerns maintaining service through disruption and meeting availability requirements; Operational Excellence concerns operating, observing, and improving workloads; Security concerns protecting systems, data, and assets. Right-sizing must respect these requirements rather than treating cost reduction as the only objective.

Start with measurements collected over a representative period. Examine CPU utilization, memory pressure, storage latency, input/output operations per second, network throughput, request latency, and application error rates as relevant. Include business peaks, batch processing, seasonal demand, and failure scenarios. A low average CPU value alone does not establish that an instance is oversized: the application might require substantial memory, experience short CPU spikes, or be constrained by storage or network limits.

For example, a web application running on a large virtual machine might use little CPU and memory even during its busiest period. An engineer can test a smaller configuration, compare high-percentile response times and error rates, and deploy the change with a rollback plan. By contrast, an analytics worker with low CPU usage but high memory consumption may benefit from a memory-optimized resource rather than a uniformly smaller one. A database might need fewer virtual CPUs but still require its existing storage throughput.

Right-sizing is related to elasticity, but they are not identical. Right-sizing determines the appropriate resource shape and capacity for the work; elasticity adjusts capacity as demand changes. An automatically scaling fleet can still use oversized instances. Similarly, purchasing a discount commitment changes the price paid for capacity, not whether that capacity fits the workload. Validate sizing before making long-term purchasing commitments, and account for existing commitments when estimating actual bill reductions.

Changes involve trade-offs. Downsizing can reduce headroom, alter throughput limits, or require a restart or maintenance window. Reducing replica counts may weaken availability even if average utilization remains low. Use load tests, staged changes, monitoring, and rollback criteria to protect service objectives. Review sizing after application releases, traffic changes, and architectural changes; it is an ongoing engineering practice, not a one-time migration task.

Learn Right-Sizing in lessons

17 short lessons on Right-Sizing in 9 certification courses.

and 11 more lessons

Open the lessons