alt Hacker NewsI've been working on that for a client since yesterday (as a fractional CTO). Pretty hectic, basically nothing really works and we don't know yet if all data is lost or if anything is recoverable or when AWS UAE will become functional again so we can recover that region.
Finally, I have a very good argument for multi-region deployments ;))
that's my go to website atm: https://health.aws.amazon.com/health/status
Replies
Severity: Disrupted
So if data won't be recoverable you all will mark it something like "Status: FUBAR" or some equivalent term?
We didn't do multi-region deployments, but we did store database backups in a separate region just in case something really bad happened and our AWS region became unavailable. Also had a plan/some ready Terraform stuff in order to start setting up a deployment if it became apparent that the region wasn't coming back anytime soon.
IMO, if you're using AWS and not replicating your data somewhere else, this should be an eye-opener for you.
What do you mean 'finally' - surely 'redundancy' or 'natural disaster' is reason enough.