EC2 Warning Signal Diagnostic Troubleshooter (Part 6)
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 | caution | "Important For security purposes, if you are not moving on to the next procedure immediately, stop the Apache web server (httpd) now. After you move your installation under the Apache document root, the WordPress installation script is unprotected and an attacker could gain access to your blog if the Apache web server were running." | WordPress Installation on Amazon Linux | An attacker could gain access to your blog |
| 6 | warning | "Warning If your instance store-backed instance passes its retirement date, it is terminated and you cannot recover the instance or any data that was stored on it." | Instance Store-Backed Instances / Instance Retirement | It is terminated and you cannot recover the instance or any data that was stored on it |
| 7 | known limitation | "Important We currently do not support resource-level permissions for the create-fleet resource. If you specify create-fleet as a resource, you will get an unauthorized exception when you try to tag the fleet." | EC2 Fleet / IAM Policies | You will get an unauthorized exception when you try to tag the fleet |
| 8 | caution | "Important If you have retention rules for AMIs and for their associated snapshots, make the retention period for the snapshots the same or longer than the retention period for the AMIs. This ensures that Recycle Bin does not delete the snapshots associated with an AMI before deleting the AMI itself, as this would make the AMI unrecoverable." | Recycle Bin Retention Rules (EBS-backed AMIs) | This would make the AMI unrecoverable |