6 ms·
AWS EC2 Having Issues
- deleted 6y ago[deleted]
- bashinator 6y agoNever run prod in us-east-1.
- meepmorp 6y agoIt's the one with the chaos monkey built in.
- acdha 6y agoThat joke is getting pretty tired by now and restating it seems unlikely to be helpful for anyone who's affected by the rate-limited API calls in question.
- igetspam 6y agoIt's not a joke. The us-east-1 region is one of if not the oldest. Some of the infrastructure is aging because it's hard to phase out. Amazon has learned a lot since then and the newer regions have reaped all the benefits, where Virginia hasn't. There are components that exist in that region and don't exist in others but as a rule, I use those as remote resources and keep all my critical infra in Ohio, if I need to be near east.
- acdha 6y agoHave you actually measured it? I’ve had production workloads in us-east-1 for over a decade and haven’t seen it be notably different than the other regions. There’ve been a handful of times where there’s been a truly regional outage (17 minutes of network connectivity in 2011) and a couple of broader service outages (S3, IAM), but it’s not like the other regions never have problems. In general most of the time when I’ve heard people say “us-east-1 is unreliable” it’s ended up that they’re really telling you that they were in just one AZ, thought the RDS multiple AZ mode was too expensive, etc. and standard architectural guidance would have taken care of it.
- johncena33 6y agoI see this a lot. Is there any reason why this particular region will have so many issues?
- notatoad 6y agoA big reason is it’s the largest region. More servers = more likely to have problems
- TheDong 6y agoEC2 existed in us-east-1 only for 2 years before it was launched in a second region. Those 2 years were already enough to pick up some legacy cruft and special cases. us-east-1 is also the first region for various other old services, like s3 and route53. I think it's also the largest region across many axis, which naturally means it will hit various scaling issues before other regions.
- ufoolme 6y agoNot sure if it is related but it is usually one of the first to get or be trialing new features. I believe a few global services are run out of us-east-1 as well.
- guidedlight 6y agoThis is my understanding as well. New features are rolled out in us-east-1 first, then progressively through the remainder of the regions.
- pclmulqdq 6y agoSome of us have to. Weirdly, the bitcoin exchanges are all there.
- pg_bot 6y agoI would argue the opposite. Run in us-east-1 if you want to have truly reliable infrastructure.
- bigiain 6y agoAWS cost saving pro tip: Save that 10c per minute Fault Injection Simulator charge by running in us-east-1...
- busterarm 6y agoAgree. 10s of millions in infrastructure running in us-east-1 here. Honestly it seems to be the only reliable way to teach people about failure and the importance of reserving capacity.
- WatchDog 6y agoI remember being bitten by an RDS update, running in ap-southeast-2. Took out a few of our production databases, seems like Australia is the beta testing region for at least a few services. At least in the US you have the choice of other regions.
- berniemadoff69 6y agointeresting they use blue as the color that indicate an "issue". at a glance, looks like nothing to see here. i have a feeling that if the entire AWS infrastructure were to go offline somehow they would refer to that as 'increase error rates'
- ashtonkem 6y ago100% is technically an increase, if you’re rules lawyering.
- jacques_chester 6y agoI suspect it's an accessibility decision. Blue is more distinguishable from green by colour-blind folks. Red is not distinguishable.
- Spivak 6y agoDowntime is kinda hard to grok for huge distributed services like this. If you’re down when anyone gets errors you’ll probably always be down — not really useful. If you’re down when everyone gets errors you’ll probably always be up — again not really useful. From a customer perspective an increase in errors means nothing if it doesn’t affect you or everything if it does so even a flat percentage is likely not all that useful except as a probability that any issues you’re seeing are your fault.
- temp-dude-87844 6y agoOn this topic, a popular previous post on HN is 'Your nines are not my nines' [1] by rachelbythebay. [1] https://news.ycombinator.com/item?id=20451714 https://news.ycombinator.com/item?id=20451714
- obnauticus 6y agoHence why they people use percentile measurements for alerting at places like AMZN. This person worked on Alexa and wrote an article about it: https://medium.com/@djsmith42/how-to-metric-edafaf959fc7 https://medium.com/@djsmith42/how-to-metric-edafaf959fc7
- random5634 6y agoI run mostly us-west-2 - and when talking about AWS I've always felt reliability was pretty good. us-east-1 really is the one that seems to get hammered the hardest on the error counts.
- igetspam 6y agoSome day people will learn that us-east-1 is the least reliable region.
- cryptoz 6y agoNobody uses us-east-1 anymore. It's too crowded.
- esotericimpl 6y agothis should be the top comment.
- bruce_the_bruce 6y agoI see what you did there- famous Yogi Berra quote.
- mgore 6y agoAll the new instance types seem to get deployed on US-EAST-1 first. It may be crowded, but it always gets the good stuff first.
- luhn 6y agoAs much as I can remember, us-west-2 gets new instances and features at the same time as us-east-1. (And IIRC eu-west-1 gets new stuff as well, but I don't pay much attention to that.) Was there anything in the past few years where this hasn't been true?
- geoduck14 6y agoI hear 70% of all internet traffic goes through us-east-1
- LogicX 6y agoI see what you did there...
- gshakir 6y agoInterestingly I couldn’t submit this URL to HN because it would take me to an original story that was posted 6 months ago. So I had to put it a random query string at the end of the URL like this https://status.aws.amazon.com/?x=1000 https://status.aws.amazon.com/?x=1000 @Dang, any way HN can allow new submissions to the same URL? Thank you .
- thayne 6y agoIt's also annoying that AWS doesn't have a seperate url for a specefic incident.
- wdb 6y agoGCP also experienced problems. A really nice one were if you deleted a service account you end up with restart loop: > We are experiencing an issue with Google Kubernetes Engine. Removing Service Account from GKE might lead to infinite cluster master restarts. Please refrain from removing GKE service accounts.
- ithkuil 6y ago"Doctor, it hurts when I do this." "Well, then don't do that"
- don-code 6y agoThere actually are several good reasons to run in us-east-1. Something I hear a good lot is the latency argument - if you're a startup based in Boston, and your roundtrip to us-west-2 is 80ms (this is actually my roundtrip to us-west 2 right now), it doesn't matter - your customers on the west coast will see 80ms if you go into us-east-1, too. That's true, but your first customers will probably be local, and you almost certainly don't have the resources to be doing true multi-region deployments right out of the gate. So my personal feeling is - deploy into us-east-1 to give your first customers a good experience - _fully understanding that you are taking on some extra risk_, and pay it down as tech debt in time. Another plays off this, but in a very different way: a hybrid cloud deployment, where the public cloud is used as an on-demand extension of the datacenter. Something I once saw was that the 80ms round trip from a Boston datacenter to us-west-2 actually expanded to massive connection latencies: 80ms for a DNS lookup, and then another 500+ms (!) for the round-trips for TCP and TLS handshakes to take place, all before a SQL query or REST call actually started. That was a complete non-starter.
- mwcampbell 6y agoThat would all make sense, except that AWS has had a us-east-2 region in Ohio for a few years now.
- nodesocket 6y agoI run and own a DevOps consulting company, and NEVER provision AWS resources in us-east-1. If a east coast location is need, I use us-east-2 (Ohio).
- randmeerkat 6y agoDoes no one else think it’s odd that the general assumption of the tech community is to avoid an entire region of the largest cloud provider in the world, and then to assume these “newer” regions won’t have stability issues in a few years?
- jeppesen-io 6y agoNot really
- maxtollenaar 6y agofriends don't let friends run on us-east-1
- mwcampbell 6y ago> Existing instances and networks continue to work normally. This suggests that one can minimize certain failure modes by making the configuration as static as possible, i.e. creating a fixed number of long-running instances. But then, using immutable, ephemeral instances can make for a more resilient system when the EC2 control plane is working normally. There are always tradeoffs.
- psanford 6y agoIts a good idea to have a big red button that you can hit to pause your auto scaling groups when incidents like this are in progress.