SAA-C03 ยท Cost-optimized compute
Right-sizing and idle capacity: stop paying for what you do not use
Right-sizing with Compute Optimizer, EC2 hibernation versus stop, scheduling non-production shutdowns and matching availability to workload class.
Key points
- AWS Compute Optimizer (opt-in): 14 days of CloudWatch metrics by default, 93 with paid enhanced infrastructure metrics; right-sizes or flags idle EC2, Auto Scaling groups, EBS, Lambda, ECS on Fargate.
- Stop ends compute charges; hibernation also saves RAM to the encrypted EBS root, app resumes warm.
- Hibernation must be enabled at launch.
- Production: Multi-AZ, always on; non-production: one AZ, stopped off-hours.
Source: https://docs.aws.amazon.com/compute-optimizer/latest/ug/what-is-compute-optimizer.html
Practice questions
By default, how many days of CloudWatch utilization metrics does AWS Compute Optimizer analyze?
- 7 days
- 14 days
- 30 days
- 93 days
Show answer
Answer: B. 14 days
The default lookback is 14 days. Activating the paid enhanced infrastructure metrics extends it to 93 days for the selected resources.
Which are prerequisites for hibernating a Linux EC2 instance?
- An encrypted EBS root volume large enough to hold the RAM
- Hibernation enabled when the instance is launched
- Instance memory below 150 GiB
- An instance store root volume for faster RAM writes
- Hibernation switched on later while the instance is stopped
Show answer
Answer: A. An encrypted EBS root volume large enough to hold the RAM, B. Hibernation enabled when the instance is launched, C. Instance memory below 150 GiB
The root volume must be an encrypted EBS volume large enough for the RAM, hibernation must be enabled when the instance is launched, and a Linux instance must have less than 150 GiB of RAM. An instance store root is not allowed, and hibernation cannot be turned on for an existing instance.
You can stop an existing instance, turn on hibernation support, and hibernate it from then on.
Show answer
Answer: False
False. Hibernation support can only be enabled when the instance is launched, not on an existing running or stopped instance. Stopping with the hibernate option on an instance that was not enabled at launch does not hibernate it.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
