Compare/contrast to https://status.heroku.com/incidents/151 where they did talk about moving to multiregion, etc., but then never executed on it, which is probably worse. Maybe they will underpromise and overdeliver.
Personally, I'd shitcan EBS to the extent possible, RDS I never would have used, and it looks like ELB is non-viable as well.
If you're a large site (particularly a PaaS) on AWS and care about availability, you need to have spare capacity in your region (using RIs, like Netflix does) to cover when a single AZ disappears, and your own external to AWS load balancing (not dns based), with your own per-AZ subsidiary load balancers (nginx or whatever) running within EC2. You need a robust database layer, ideally multi-region or AWS+nonAWS, but that's more site specific.
Going multiregion is the next step, and the above is an essential part of getting to that point.
Personally, I'd shitcan EBS to the extent possible, RDS I never would have used, and it looks like ELB is non-viable as well.
If you're a large site (particularly a PaaS) on AWS and care about availability, you need to have spare capacity in your region (using RIs, like Netflix does) to cover when a single AZ disappears, and your own external to AWS load balancing (not dns based), with your own per-AZ subsidiary load balancers (nginx or whatever) running within EC2. You need a robust database layer, ideally multi-region or AWS+nonAWS, but that's more site specific.
Going multiregion is the next step, and the above is an essential part of getting to that point.