Loading…
Topic
Fault Injection
2 posts about Fault Injection. Every summary links to the original.
- 2 posts
- 1 company
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
Validating your DR commitment: From controlled test to real-world readiness
Disaster recovery commitments defined on paper need validation under conditions that expose coordination, dependency, and provisioning gaps. A scheduled failover with advance notice confirms traffic shifts, data consistency in the recovery Region, and application function afterward, but it does not test who declares failover or whether teams coordinate under pressure. The post describes four progressive validation levels: tabletop exercise, planned failover, surprise drill, and game day with fault injection using AWS Fault Injection Service. In one engagement, stopped DR instances depended on launching capacity and database replicas during the exercise without confirming Regional capacity or account quotas; a planned failover found Route 53 records still resolving to the primary Region 45 minutes in, and recovery took more than twice the 5-hour target. Findings map back to the recovery boundary, business-anchored target, and dependency-reconciled commitment, and a later exercise passed.
Recommended resilience testing in the next generation of AWS Resilience Hub
AWS Resilience Hub introduced recommended resilience testing, which uses AWS Fault Injection Service to automatically create fault injection experiments from existing policies and resource knowledge. The feature offers four pre-configured tests: Availability Zone recovery, dependency validation, Multi-Region isolation, and Multi-Region recovery. Dependency validation blocks connectivity to selected dependencies using DNS query log analysis with a 35-day look-back window, and validates whether the application remains healthy when they are unavailable, surfacing misclassified dependencies. Each test run produces a pass or fail outcome evaluated against success criteria and the recovery time objective defined in your resilience policy, with an auto-generated report capturing a point-in-time snapshot of resources. This capability removes manual experiment design, helps organizations prove their architecture holds under failure, and feeds results into compliance and reporting workflows.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.