Ask for evidence before changing a server size — Compute Optimizer

Your goal

Enroll the emulator account and save an EC2 recommendation preference.

Why this matters

Recommendations depend on enrollment, preferences, and useful workload data. You will save an EC2 metrics preference and read it back. No real workload recommendation or savings claim is made.

Words you will use

Rightsizing means matching resources to measured demand. A recommendation is a suggestion based on available metrics. Missing metrics can mean no recommendation yet.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Enable practice enrollment

Update Compute Optimizer enrollment to Active in your emulator. Enrollment allows the service to produce recommendations when suitable measurements exist. This lab has no real workload history.

2. Save a metrics preference

Enable enhanced infrastructure metrics for EC2 recommendations. This is a local setting with no AWS fee here. In real AWS, review the feature’s pricing and data requirements before enabling it.

3. Read the saved preference

Retrieve EC2 recommendation preferences and inspect the metrics setting. This lab checks configuration, not a proven cost-saving recommendation for your application.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.