Closed julialeague closed 3 years ago
I’m not sure what this means — would you be able to provide more detail? 🤔
I’m not sure what this means — would you be able to provide more detail? 🤔
I updated the description to provide actual detail, sorry about that!
Our current strategy is active-active for API calls and active-passive for static files.
All API Gateway resources are latency-routed between us-east-1 and us-west-1 in Route53. This includes:
api.dawson.ustaxcourt.gov
api-blue.dawson.ustaxcourt.gov
api-green.dawson.ustaxcourt.gov
dynamsoft-lib.dawson.ustaxcourt.gov
public-api.dawson.ustaxcourt.gov
public-api-blue.dawson.ustaxcourt.gov
public-api-green.dawson.ustaxcourt.gov
ws-blue.dawson.ustaxcourt.gov
ws-green.dawson.ustaxcourt.gov
All Cloudfront resources are failover-routed (frontend, frontend-public) through Cloudfront Origin Groups, preferring us-east-1
and failing over to us-west-1
. This includes:
dawson.ustaxcourt.gov
www.dawson.ustaxcourt.gov
blue.dawson.ustaxcourt.gov
green.dawson.ustaxcourt.gov
app.dawson.ustaxcourt.gov
app-blue.dawson.ustaxcourt.gov
app-green.dawson.ustaxcourt.gov
Outstanding ot have this documented. Thank you @adunkman !
There are two standard types of failover strategies used within AWS - active-active and active-passive.
From the AWS documentation:
Failover Strategy AWS Documentation: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover-types.html
We should take some time to determine which of these strategies we want to follow so that we have a holistic plan for failover configuration for all of the components in the EF-CMS application.
Acceptance Criteria