191–200 of 1001 posts
Wow this is a fun one. I almost pooped my pants when I saw all of our elastic beanstalk architecture disappear. It's so relieving to see it's not our fault and the internet feels our pain. We're in this together boys! I'm curious how much $ this will lose today for the economy. :)
is this affecting dockerhub for anyone?
A piece of hard-earned advice: us-east-1 is the worst place to set up AWS services. You're signing up for the oldest hardware and the most frequent outages. For legacy customers, it's hard to move regions, but in general, if you have the chance to choose a region other than us-east-1, do that. I had the chance to transition to us-west-2 about 18 months ago and in that time, there have been at least three us-east-1 ou…
I'm getting the same outage in us-west-2 right now.
is this affecting dockerhub for anyone?
Yup, same here. It has been a few minutes already. Wanna bet the green checkmark[1] will stay green until the incident is resolved? [1] https://status.aws.amazon.com/
These service health boards are more like advertisement page then actual status of the service.
Seriously: I don't understand why you guys stay with AWS.
Its unreal watching key web services fall like dominoes. Its too bad the concept of "too big to fail" applies only to large banks and countries.
"To big [to allow] to fail" is what that term means. This would extend to a service like amazon actually, where survival of the service would be an extraordinary effort in case this problem lasted for a long time. The way you imagined it, as 100% uptime, is incorrect.
We've seen this story play out in other industries and it never works out well for average people. It's been astounding for me to watch the pace of this centralizing and who is helping it along.
The tldr; point is that a single service provider should not have the amount of control Amazon does over the Internet. At least that's my take.
I know my opinion on this wildly differs from the HN crowd and SV "decision makers" these days - what is so curious to me is that this is a complete 180 from that same demographic even 10 years ago.
A piece of hard-earned advice: us-east-1 is the worst place to set up AWS services. You're signing up for the oldest hardware and the most frequent outages. For legacy customers, it's hard to move regions, but in general, if you have the chance to choose a region other than us-east-1, do that. I had the chance to transition to us-west-2 about 18 months ago and in that time, there have been at least three us-east-1 ou…
I'm getting the same outage in us-west-2 right now.
[1]: https://s3.amazonaws.com/restocks.io/robots.txt
[2]: https://s3-us-west-2.amazonaws.com/restocks.io/robots.txt
This seems like an appropriate time as any... Anyone want to list some competitors to S3? Bonus if it also provides a way to host a static website.
GitLab Pages [0] is pretty good for static websites IMO, you can use GitLab CI to build more complex sites as well [1]. Disclosure: I work for GitLab [0]: pages.gitlab.io [1]: https://about.gitlab.com/2016/12/07/building-a-new-gitlab-do...
what's truly incredible is that S3 has been offline for h̶a̶l̶f̶ ̶a̶n̶ ̶h̶o̶u̶r̶ two hours now and Amazon still has the audacity to put five shiny green checkmarks next to S3 on their service page. they just now put up a box at the top saying "We are investigating increased error rates for Amazon S3 requests in the US-EAST-1 Region." increased error rates? really? Amazon, everything is on fire. you are not fooling an…