EC2 Warning Signal Diagnostic Troubleshooter (Part 4)
Use the interactive troubleshooter below to identify your EC2 warning signal, review the verbatim warning, understand the target service, and note the consequence of ignoring.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Signal Type | Verbatim Warning | Target | Consequence of Ignoring |
|---|---|---|---|---|
| 5 | prohibition | "Important Do not use this parameter unless your AMI software supports IMDSv2. After you set the value to v2.0, you can't undo it." | AMI imds-support parameter (v2.0) | You can't undo it (the only way to "reset" your AMI is to create a new AMI from the underlying snapshot). |
| 6 | warning | "If Enable is selected, when Amazon EC2 creates the new AMI, it does not shut down and reboot the instance. Warning If you choose to enable No reboot, we can't guarantee the file system integrity of the created image." | Amazon EC2 Create Image API (No reboot option) | We can't guarantee the file system integrity of the created image. |
| 7 | warning | "Warning Data on instance store volumes is lost when an instance is stopped, hibernated, or terminated. This includes instance store volumes that are attached to an instance that has an EBS volume as the root device." | Instance store volumes | Data on instance store volumes is lost. |
| 8 | warning | "Warning Diagnostic interrupts are intended for use by advanced users. Incorrect usage could negatively impact your instance. Sending a diagnostic interrupt to an instance could trigger an instance to crash and reboot, which could lead to the loss of data." | Diagnostic interrupts | Trigger an instance to crash and reboot, which could lead to the loss of data. |