Live data from Hacker News

AWS multiple services outage in us-east-1

health.aws.amazon.com

71–80 of 1001 posts

Re: AWS multiple services outage in us-east-1

#76
Meanwhile my pair of 12 year old raspberry pi's hangling my home services like DNS survive their 3rd AWS us-east-1 outage.

"But you can't do webscale uptime on your own"

Sure. I suspect even a single pi with auto-updates on has less downtime.

Re: AWS multiple services outage in us-east-1

#77

Can't resolve any records for dynamodb.us-east-1.amazonaws.com However, if you desperately need to access it you can force resolve it to 3.218.182.212. Seems to work for me. DNS through HN curl -v --resolve "dynamodb.us-east-1.amazonaws.com:443:3.218.182.212" https://dynamodb.us-east-1.amazonaws.com/

Dude!! Life saver.

Re: AWS multiple services outage in us-east-1

#80

"Never choose us-east-1"

Never choose a single point of failure.

Or rather

Ensure your single point of failure risk is appropriate for your business. I don't have full resilience for my companies AS going down, but we do have limited DR capability. Same with the loss of a major city or two.

I'm not 100% confident in a Thames Barrier flood situation, as I suspect some of our providers don't have the resilience levels we do, but we'd still be able to provide some minimal capability.

Post reply on HN