EC2 Network & Metrics Hidden Gaps Diagnostic Troubleshooter
Use the interactive troubleshooter below to identify your EC2 network or metrics hidden gap 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 | Network microbursts are invisible in CloudWatch instance metrics | CloudWatch metrics are not granular enough to reflect these microsecond spikes | CloudWatch metrics collected at 1-minute or 5-minute intervals average out microsecond-level network traffic spikes, hiding packet drops. | N/A |
| 2 | Baked AMIs publish metrics under the wrong Instance ID | emit metrics using the instance ID of the original instance | The CloudWatchClient.pm script caches instance metadata locally, causing cloned instances to silently report metrics under the original instance's ID until the TTL expires. | rm /var/tmp/aws-mon/instance-id |
| 3 | ENA Express silently falls back to standard UDP transmission | communication between these two instances over UDP uses standard ENA transmission | ENA Express requires identical configuration on both the sending and receiving instances; a mismatch causes UDP traffic to silently bypass SRD technology. | aws ec2 modify-network-interface-attribute --network-interface-id eni-0123f4567890a1b23 --ena-srd-specification 'EnaSrdEnabled=true,EnaSrdUdpSpecification={EnaSrdUdpEnabled=true}' |
| 4 | ENA Express SRD eligibility metric miscounts packets | the packet is still reflected as eligible in the counter | Packets exceeding the MTU limit are falsely tracked as eligible by ena_srd_eligible_tx_pkts but cannot transmit via SRD and silently revert to standard ENA. | sudo ip link set dev eth0 mtu 8900 |