EC2 Silent Monitoring Failures Diagnostic Troubleshooter
Use the interactive troubleshooter below to identify your EC2 silent monitoring failure 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 | Instances silently launch without tags | IamFleetRole does not include the CreateTags permission | The user and the IamFleetRole have mismatched permissions where the fleet's IAM role lacks ec2:CreateTags, breaking tag-based monitoring. | N/A |
| 2 | Incorrect CPU credit metric aggregations | use the Sum statistic instead of the Average statistic | The Average statistic is improperly applied to CPU credit metrics when querying periods larger than 5 minutes. | N/A |
| 3 | Silently dropped EBS metrics | data is reported only when there is read activity on the volume | Amazon EBS silently stops sending metric data points to CloudWatch when Xen instances experience zero disk activity. | N/A |
| 4 | Impaired instance passes status checks | If your experience differs from our check results | The default Amazon EC2 instance status checks fail to detect certain underlying system impairments. | N/A |