EC2 Visibility & Console Access Diagnostic Troubleshooter
Use the interactive troubleshooter below to identify your EC2 visibility or console access issue by symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific monitoring blind spot are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 1 | Instance Tags Invisible to Local Monitoring Agents | access to the tags in instance metadata is not allowed | Local monitoring agents cannot read instance tags via the Instance Metadata Service (IMDS) because tag exposure is disabled by default. | Select Enable for Allow tags in metadata |
| 2 | Capacity Reservation Eventual Consistency Blind Spot | it can take up to 5 minutes | API eventual consistency causes up to a 5-minute observability gap where active Capacity Reservations are falsely reported as pending. | N/A |
| 3 | EC2 Serial Console Silent Failure (Black Screen) | If the screen remains black | An unresponsive getty service or misconfigured serial console access policy results in a silent black screen instead of an explicit error prompt. | sudo systemctl restart serial-getty@ttyS |