Skip to main content

EC2/EBS Conditional Failure Patterns (Part 2)

Data strictly extracted from official AWS troubleshooting documentation. Click the symptom below to get the targeted conditional failure pattern and its consequence.

🚨 Step 1: What specific error symptom are you experiencing?

Please click the most accurate description:


Quick Reference Table

#PatternVerbatim Conditional SentenceTrigger ConditionConsequence
5if...cannot"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."Failing to migrate or back up an instance store-backed EC2 instance before its scheduled underlying hardware retirement date passes.Instance is forcibly terminated and all local data is permanently lost (Visible outage/data loss).
6if...no longer"If the snapshots that are associated with the AMI are deleted from the Recycle Bin, the AMI is no longer recoverable."Deleting the underlying EBS snapshots associated with an Amazon Machine Image (AMI) from the Recycle Bin before the AMI itself expires.The AMI is permanently broken and no longer recoverable (Visible failure during launch attempts).
7if...otherwise...fails"If you use targeted Capacity Reservations in your EC2 Fleet, there must be enough Capacity Reservations to fulfil the target On-Demand capacity, otherwise the launch fails."Specifying targeted Capacity Reservations in an EC2 Fleet configuration when there is insufficient unused reserved capacity to meet the request.EC2 Fleet instance launch fails (Visible failure).
8if...unable to"Grub is typically installed on only one device in a RAID array, and if one of the mirrored devices fails, you may be unable to boot the operating system."A device failure occurs on the specific mirrored volume in an EBS RAID 0 array that happens to house the Grub bootloader.Unable to boot the EC2 instance's operating system (Visible outage).