EC2 Interface Naming & ENA Express Diagnostic Troubleshooter
Use the interactive troubleshooter below to identify your EC2 interface naming or ENA Express issue by symptom, review the raw error log, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 1 | Network interface fails to be named eth0 on boot, causing complete network unreachability | systemd-208-11.el7_0.2.x86_64 | The OS uses systemd/udev versions 197 or greater which predictably rename Ethernet devices rather than guaranteeing the eth0 name that EC2 requires. | sudo sed -i '/^GRUB_CMDLINE_LINUX/s/"$/ net.ifnames=0"/' /etc/default/grub |
| 2 | ENA Express performance degrades, falling back to standard ENA with dropped packets | ena_srd_resource_utilization: 0 | The instance is exhausting its available SRD resources by approaching 100% of the maximum allowed memory utilization for concurrent SRD connections. | Scale the instance out to improve network performance. |