Skip to content

docs: Normalize structure: Chaos Engineering — Route 53 Failover #257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: Normalize structure: Chaos Engineering — Route 53 Failover #257

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 13 additions & 1 deletion src/content/docs/aws/tutorials/route-53-failover.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,7 @@ test.hello-localstack.com.
.....
```

### Creating a controlled outage
### Testing the application

Our setup is now complete and ready for testing.
To mimic a regional outage in the `us-west-1` region, we'll configure the [Chaos API](/aws/capabilities/chaos-engineering/chaos-api) to halt all service invocations in this region, including the health check function.
Expand Down Expand Up @@ -290,3 +290,15 @@ The LocalStack logs will confirm which API Gateway was called based on the resol
2023-11-07T11:59:28.292 DEBUG --- [ asgi_gw_9] l.s.l.i.version_manager : > {resource: /productApi,path: /productApi,httpMethod: GET,headers: {Host=67890.execute-api.localhost.localstack.cloud:4566,
User-Agent=python-requests/2.31.0, accept-encoding=gzip, deflate, accept=*/*, Connection=keep-alive, x-localstack-tgt-api=apigateway ....
```

### Conclusion

This tutorial demonstrated how to build a resilient, self-healing infrastructure using Route53 failover routing in combination with LocalStack's Chaos Engineering capabilities. Key takeaways include:

- **Automatic Failover**: Route53 health checks continuously monitor endpoint health and automatically redirect traffic to standby regions when primary regions become unavailable
- **Data Resilience**: Cross-region data replication ensures business continuity during regional outages
- **Testing in Production-like Environments**: LocalStack's Chaos API enables safe testing of failure scenarios without impacting production systems
- **Reduced Recovery Time**: Automated failover mechanisms significantly reduce recovery time objectives (RTO) compared to manual intervention
- **Cost-Effective Testing**: LocalStack provides a cost-effective platform for validating disaster recovery procedures and ensuring organizational readiness for actual outage scenarios

By implementing this architecture, organizations can achieve higher availability SLAs and ensure uninterrupted service delivery even during regional disruptions. The combination of Route53 for intelligent traffic routing and cross-region replication for data redundancy creates a robust foundation for mission-critical applications.