The main issue appears to be DynamoDB Here's a copy from the status page. 3:00 AM PDT We are investigating increased error rates for API requests in the US-EAST-1 Region. 3:26 AM PDT We are continuing to see increased error rates for all API calls in DynamoDB in US-East-1. We are actively working on resolving the issue. 4:05 AM PDT We have identified the source of the issue. We are working on the recovery. 4:41 AM PD…
6:19 AM PDT The metadata service is now stable and we are actively working on removing throttles. 7:12 AM PDT We continue to work on removing throttles and restoring API availability but are proceeding cautiously. 7:22 AM PDT We are continuing to remove throttles and enable traffic progressively. 7:40 AM PDT We continue to remove throttles and are starting to see recovery. 7:50 AM PDT We continue to see recovery of r…
AWS US East is experiencing high error rates on several services
61–70 of 184 posts
Re: AWS US East is experiencing high error rates on several services
#62Re: AWS US East is experiencing high error rates on several services
#63This is manifesting itself as downtime for a lot of companies, including Heroku: https://status.heroku.com If you want alerts on this sort of thing, my side project StatusGator https://statusgator.io will alert you when services post downtime on their status pages. My dashboard blew up this morning with a ton of red and yellow as soon as Amazon started flaking. Edit: I suppose it's time to invest in a multi-region se…
> Our service provider is still working towards resolution of this issue. We will update when we have news, or in 1 hour.
I wonder why they don't tell that AWS is their service provider. Is it wrong to make the information less obscure?
Re: AWS US East is experiencing high error rates on several services
#64This seems like another reason to not rely on Amazon-specific services, other than the obvious vendor lock-in. At least in the event of an instance outage you could conceivably migrate off Amazon to another VPS provider. No one using DynamoDB has an alternative.
This was as also part of the strategy when we decided to open source kubernetes. Having an open alternative made the commercial offering (Google Container Engine -- GKE) much stronger because of the reduced dev lock-in.
Re: AWS US East is experiencing high error rates on several services
#65Re: AWS US East is experiencing high error rates on several services
#66Re: AWS US East is experiencing high error rates on several services
#67This seems like another reason to not rely on Amazon-specific services, other than the obvious vendor lock-in. At least in the event of an instance outage you could conceivably migrate off Amazon to another VPS provider. No one using DynamoDB has an alternative.
You can create a Datomic backup from any of these databases and restore them into a different one with the exact same semantics.
Re: AWS US East is experiencing high error rates on several services
#68Re: AWS US East is experiencing high error rates on several services
#69Earlier quoted context omitted.
Source for service with better uptime than Amazon?
I believe he meant things like using RabbitMQ instead of SQS (SQS isn't very good anyway IMHO) and things like that. More services running on plain old instances rather than AWS specific APIs, Azure specific APIs, etc. This prevents you from getting too locked in and losing control over your application. I honestly can't believe that Netflix can't even load their home page without DynamoDB and all this other stuff. E…
I mean, if even Netflix can't stay up during this, what hope does a startup have?
Re: AWS US East is experiencing high error rates on several services
#70You say you don't use SQS or SNS? When they go down, you might not be able to get Logs or even login to the web Console.
Same goes for things like AutoScaling, OpsWorks, etc.