EC2/EBS Command Reference Diagnostic Troubleshooter (Part 2)
Use the interactive troubleshooter below to identify your EC2/EBS command scenario, review the verbatim command, understand the trigger condition, and learn what it diagnoses or fixes.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Command Category | Verbatim Command | When to Run | What It Does |
|---|---|---|---|---|
| 5 | package/service management | sudo systemctl start nvidia-fabricmanager && sudo systemctl enable nvidia-fabricmanager | You are launching a p4d.24xlarge instance and need NV Switch Management for GPU workloads. | Starts the Nvidia Fabric Manager service, and ensures that it starts automatically when the instance starts. |
| 6 | network-test | TOKEN=\curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"` && curl -H "X-aws-ec2-metadata-token: $TOKEN" -v http://169.254.169.254/latest/meta-data/tags/instance` | You need to get all the instance tag keys associated with an instance using IMDSv2. | Creates a session token lasting six hours using a PUT request and uses that token to retrieve the instance tags from the local Instance Metadata Service. |
| 7 | diagnostic | df -hT | You need to verify the file system type before extending it after resizing an Amazon EBS volume. | Lists available file systems, showing their current size, mount points, and type (such as xfs or ext4) so you know which specific resize command to use. |
| 8 | fix | sudo resize2fs /dev/nvme0n1p1 | You have increased the size of an EBS volume and need to extend an Ext4 file system to use the new, larger size on a Nitro instance. | Extends the file system to match the new size of the underlying volume. |