EC2/EBS Conditional Failure Patterns (Part 1)
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 |
|---|---|---|---|---|
| 1 | can result in | "Using Multi-Attach with a standard file system can result in data corruption or loss, so this is not safe for production workloads." | Attaching an Amazon EBS volume to multiple EC2 instances using a standard file system (like XFS or EXT4) instead of a clustered file system. | Data corruption or loss (Silent initially, visible upon data retrieval failure). |
| 2 | will result in | "Enabling FileVault will result in the host failing to boot due to the partitions being locked." | Enabling FileVault encryption on the macOS guest operating system of an EC2 Mac instance. | Host fails to boot (Visible outage). |
| 3 | could lead to | "Currently, the EFA provider does not support LL protocols. Enabling them could lead to data corruption." | Enabling Low Latency (LL) protocols in the NVIDIA Collective Communications Library (NCCL) when using the Elastic Fabric Adapter (EFA) provider. | Data corruption (Silent data degradation). |
| 4 | if...fail / cascade | "If another instance boots with this file, the operating system will be unable to find the device and eth0 might fail, causing boot issues." | Creating an AMI without first deleting the /etc/udev/rules.d/70-persistent-net.rules file (which hardcodes the original instance's MAC address), and booting a new instance from it. | OS fails to find the network device, eth0 fails, system becomes unbootable/unreachable (Visible outage). |