Solutions Architect

Compute costs

Paying the lowest price for the capacity a workload really needs: the right purchase option, the right size and only the hours it runs. This is Domain 4: Design Cost-Optimized Architectures, 20% of the scored content.

Purchase options

Amazon EC2 billing and purchasing options

Official page

The same instance costs very different amounts depending on how you buy it. Match the option to how steady, how long and how interruptible the workload is.

Key points

  • Steady baseline: cover it with Savings Plans or Reserved Instances, then let Auto Scaling add On-Demand or Spot capacity for the peaks.
  • On-Demand billing: per second with a 60-second minimum for Linux and Windows. SUSE Linux Enterprise Server is billed per full hour.
  • Payment options: All Upfront, Partial Upfront or No Upfront. The more you pay upfront, the lower the rate.
  • Capacity is not a discount: zonal Reserved Instances and Capacity Reservations hold capacity in one AZ. Regional Reserved Instances and Savings Plans give a discount but reserve no capacity.
  • Stacking: a Capacity Reservation has no discount of its own, but Savings Plans or regional Reserved Instances apply to it.

On the exam

"Steady 24/7 load for 3 years, lowest price" -> Savings Plans or Standard Reserved Instances. "Guarantee capacity in one AZ for a launch, no long commitment" -> On-Demand Capacity Reservation, not a Reserved Instance.

Purchase options at a glance

OptionFit and maximum discount
On-DemandNo commitment. Short, spiky or unknown workloads. Full price.
Compute Savings PlansUSD per hour for 1 or 3 years across EC2, Fargate and Lambda, any family, size or Region. Up to 66%.
EC2 Instance Savings PlansOne instance family in one Region, any size, OS or tenancy. Up to 72%.
Standard Reserved InstancesFixed configuration for 1 or 3 years. Up to 72%. Can be sold in the Reserved Instance Marketplace.
Convertible Reserved InstancesCan be exchanged for another family, type, platform, scope or tenancy. Up to 66%.
Spot InstancesSpare capacity, interruptible with a 2-minute notice. Up to 90%.
Dedicated HostsA whole physical server with socket and core visibility, for server-bound licenses.
Capacity ReservationsCapacity in one AZ, no term for immediate use, billed whether instances run or not.

Savings Plans vs RIs

Savings Plans and Reserved Instances

Official page

Both trade a commitment for a lower rate. Savings Plans commit to an hourly spend and follow the workload, Reserved Instances commit to an instance configuration.

Key points

  • Compute Savings Plans: the most flexible. Apply to EC2 regardless of family, size, AZ, Region, OS or tenancy, and also to Fargate and Lambda. Up to 66%.
  • EC2 Instance Savings Plans: tied to one family in one Region, free to change size, OS and tenancy. Up to 72%.
  • Convertible vs Standard RIs: Convertible can be exchanged during the term but cannot be sold. Standard cannot be exchanged but can be sold in the Reserved Instance Marketplace.
  • Database Savings Plans: 1-year, No Upfront commitment across Aurora, RDS, DynamoDB, ElastiCache, DocumentDB, Neptune, Keyspaces, Timestream, DMS and OpenSearch Service. Up to 35%.
  • Sharing: by default the discount flows to every account in the organization. The management account can restrict it to groups or turn it off per account.

On the exam

"Workloads may move from EC2 to Fargate or Lambda, or to another Region" -> Compute Savings Plans. "Highest discount, the instance family will not change" -> EC2 Instance Savings Plans or Standard RIs. Convertible RIs are the distractor when Fargate or Lambda appear.

Spot Instances

Amazon EC2 Spot Instances

Official page

Spare EC2 capacity at up to 90% off On-Demand. EC2 can reclaim it at any time, so the workload must tolerate interruption.

Key points

  • Interruption notice: a 2-minute warning arrives as an EventBridge event and in instance metadata. The behavior can be terminate, stop or hibernate.
  • Rebalance recommendation: an earlier signal of elevated risk. Capacity Rebalancing in Auto Scaling groups and EC2 Fleet replaces the instance before the notice.
  • Diversify: be flexible across instance types (at least 10 per workload is the rule of thumb) and every AZ, or use attribute-based instance type selection.
  • Allocation strategy: price-capacity-optimized picks the pools with the most spare capacity at the lowest price, which lowers the chance of interruption.
  • Mixed instances group: one Auto Scaling group with an On-Demand base and Spot above it, across several types. EC2 Fleet does the same when you manage the lifecycle yourself. Spot Fleet (RequestSpotFleet) is a legacy API.
  • Fit: stateless web tiers, batch, CI/CD, big data, HPC, rendering and containers. Not for stateful, tightly coupled or interruption-intolerant work.

On the exam

"Batch job, can restart, lowest cost" -> Spot with checkpoints. "Database that must stay up" -> never Spot. "Always keep 2 instances, scale out cheaply" -> mixed instances group with an On-Demand base and Spot on top.

Dedicated capacity

Dedicated Hosts, Dedicated Instances and Capacity Reservations

Official page

Single-tenant hardware answers compliance and licensing needs, and Capacity Reservations answer capacity needs. Neither is the cheap option on its own.

Key points

  • Dedicated Hosts: a whole physical server with visibility of sockets and physical cores, host affinity and per-host billing. Bring per-socket, per-core or per-VM licenses.
  • Dedicated Instances: instances on single-tenant hardware, billed per instance, without control over placement on the host.
  • On-Demand Capacity Reservations: capacity in one AZ for any duration, no commitment for immediate use, cancel at any time. Billed whether instances run or not.
  • Future-dated reservations: request capacity for a future date with a commitment period, for planned events and launches.
  • Capacity Blocks: reserve a cluster of GPU instances for machine learning.

On the exam

"License priced per socket or per core, keep using it on AWS" -> Dedicated Hosts. "Only needs single-tenant hardware, no license visibility" -> Dedicated Instances.

Rightsizing

AWS Compute Optimizer

Official page

A discount on an oversized instance still wastes money. Rightsize and remove idle resources first, then commit to the new baseline.

Key points

  • Compute Optimizer: analyzes the last 14 days of CloudWatch metrics and recommends sizes and idle resources for EC2, Auto Scaling groups, EBS, Lambda, ECS on Fargate, RDS, Aurora and more.
  • Enhanced infrastructure metrics: a paid option that extends the lookback to 93 days, so monthly or quarterly peaks count.
  • Instance family: pick by the bottleneck. General purpose (M, T), compute optimized (C), memory optimized (R, X), storage optimized (I).
  • Graviton: Arm-based instances cost up to 20% less than comparable x86 instances and use up to 60% less energy for the same performance. Also offered in RDS, Aurora and EKS.
  • Order of work: rightsize, then buy Savings Plans or Reserved Instances, so the commitment is not sized to waste.

On the exam

"Instances average 10% CPU, cut cost with least effort" -> Compute Optimizer recommendations and a smaller size. "Same performance, lower price, code runs on Arm" -> Graviton.

Lambda and Fargate

AWS Lambda and AWS Fargate

Official page

Serverless removes idle cost: you pay per request and duration, or per task second. At a high, steady load, well-used instances can be cheaper.

Key points

  • Lambda: billed by requests and duration in GB-seconds, so memory size drives cost. Nothing is billed while idle.
  • Lambda on Arm: the arm64 architecture (Graviton2) offers up to 34% better price performance than x86.
  • Provisioned Concurrency: removes cold starts, but you pay for the configured concurrency for as long as it is set, even with no traffic.
  • Fargate: billed per second for vCPU, memory and storage above the 20 GB included, with a 1-minute minimum (5 minutes for Windows). No instances to patch or bin-pack.
  • Fargate Spot and Savings Plans: Fargate Spot is up to 70% off for interruption-tolerant ECS tasks. Compute Savings Plans cut steady Fargate use by up to 50%.
  • Trade-off: EC2 with Auto Scaling for constant high utilization, Lambda for spiky or event-driven loads, Fargate for containers without cluster management.

On the exam

"Runs a few times a day, a few seconds each time" -> Lambda, not an always-on instance. "Containers, no servers to manage, can be interrupted" -> Fargate Spot.

Scheduling and hibernation

Instance Scheduler on AWS

Official page

Non-production environments rarely need to run at night or need production availability. Stop them off hours, run them smaller and in fewer AZs.

Key points

  • Instance Scheduler on AWS: an AWS Solution that starts and stops EC2 instances, Auto Scaling groups and RDS instances on tag-based schedules, across accounts and Regions.
  • Stopped EC2: no instance charge, but EBS volumes and public IPv4 or Elastic IP addresses are still billed.
  • Hibernation: saves RAM to the encrypted EBS root volume and resumes the processes with the same instance ID. Enabled at launch, Linux RAM under 150 GiB. Pre-warms apps with slow startup.
  • Stopped RDS: no instance-hour charge, but storage and backups are billed, and RDS starts the instance again after 7 consecutive days.
  • Availability by class: production gets Multi-AZ and headroom. Dev and test can run in one AZ, smaller and only in working hours.

On the exam

"Dev environment used only in business hours" -> scheduled stop and start with Instance Scheduler. "App needs 20 minutes to warm its memory before serving" -> hibernation, not a plain stop.