Q: An application successfully utilizes AWS EFS (Elastic File System) for shared WordPress storage. It performs beautifully for 3 months, then suddenly grinds to a catastrophic halt, dropping to 1 MB/s throughput daily. Why?
The application has exhausted its EFS Burst Credits.
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When an interviewer asks how I troubleshoot this in AWS, I frame it through my hands-on production experience. The interviewer is testing: EFS Burst Credits and Baseline Throughput.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Production Solution & Architecture
The application has exhausted its EFS Burst Credits. By default, EFS operates in "Bursting Throughput" mode. You are constantly awarded credits based purely on how much data you store. If you only store 10 GB of data, your baseline throughput is a microscopic 0.5 MB/s. The application was heavily utilizing accrued "Burst" credits (up to 100 MB/s) to mask the low baseline. After 3 months of heavy traffic, the credit bank hit absolute zero. *Fix:* Immediately switch the EFS configuration mode from "Bursting" to Provisioned Throughput (e.g., paying for a guaranteed 50 MB/s regardless of storage size) or "Elastic Throughput" mode to instantly restore performance.
- Immediate Triage: The application has exhausted its EFS Burst Credits.
- Run targeted verification commands before modifying configuration.
- Automate permanent guardrails (CI check, alerts, IaC policy) to prevent recurrence.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Purging compromised IAM user credentials immediately prior to querying CloudTrail forensic event logs when configuring application successfully utilizes Deactivating a compromised key prevents abuse while preserving identity records for CloudTrail forensic queries to assess blast radius.
- Conflating local IAM Permissions Boundaries with organizational Service Control Policies (SCPs) when configuring application successfully utilizes SCPs define maximum permission guards at the AWS Organization level across accounts, whereas permission boundaries limit delegate privileges within a single account.
- Deploying single-AZ cloud infrastructure for production workloads without multi-AZ failover resilience when configuring application successfully utilizes Availability Zone hardware failures or localized network partitions cause complete service downtime when resources are not distributed across >=2 AZs.
- Jumping straight to SSH or instance restarts without reviewing CloudWatch metrics and AWS Systems Manager logs when configuring application successfully utilizes Senior SREs triage control plane and hypervisor metrics via CloudWatch and SSM Session Manager before executing invasive host-level actions.