EC2/EBS Conditional Failure Patterns (Part 4)
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
| # | Pattern | Verbatim Conditional Sentence | Trigger Condition | Consequence |
|---|---|---|---|---|
| 5 | If... might not be able to | "If you create a snapshot or AMI from an instance that is hibernated or has hibernation enabled, you might not be able to connect to a new instance that is launched from the AMI, or from an AMI that was created from the snapshot." | Creating an Amazon EBS snapshot or AMI from an EC2 instance that is currently hibernated or has hibernation enabled. | Inability to connect to any new EC2 instances launched from that AMI or snapshot. (Visible) |
| 6 | When... is lost | "When an instance is stopped, all data on the instance store volumes is lost." | Stopping an Amazon EC2 instance that relies on temporary instance store volumes. | Complete data loss on the instance store volumes. (Visible) |
| 7 | If... might encounter | "If you attach two or more network interfaces from the same subnet to an instance, you might encounter networking issues such as asymmetric routing." | Attaching two or more Elastic Network Interfaces (ENIs) from the same Amazon VPC subnet to a single EC2 instance. | Networking issues such as asymmetric routing occur. (Visible) |
| 8 | If... fails | "If the selected Capacity Reservation does not have sufficient capacity for the number of instances you selected, the instance launch fails." | Targeting an Amazon EC2 instance launch by ID into a Capacity Reservation that lacks the required available capacity. | The EC2 instance launch fails. (Visible) |