-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
documentationImprovements or additions to documentationImprovements or additions to documentation
Description
Should detail:
- General failover model
- Active/Active except for Redis - theoretically we could run in active/active but S3 and other processes could have conflicts - easiest to just not do it
- When to failover
- Risks to failover:
- For example, in-progress locks are released if Redis is also down.
- S3 replication is not in time, so S3 data could be not accurately reflected in the new region in time.
- How to failover (modify Cloudfront targets).
- provide an automated failover script
- Prepare a disaster recovery account which can perform failover.
Metadata
Metadata
Assignees
Labels
documentationImprovements or additions to documentationImprovements or additions to documentation