8 ms·
I don't think a lot of people are really understanding how much of a larger issue this would be for us if AWS didn't patch a major security issue before it was
by monjinan 12y ago
I don't think a lot of people are really understanding how much of a larger issue this would be for us if AWS didn't patch a major security issue before it was made public.
The company has treated me very well over the years, from AWS to retail. My stuff arrives on time, if it doesn't I get reimbursed, most of the time with an extra few bucks for my trouble. The AWS platform is more mature and feature rich than anyone else and keeps getting better.
These reboots are going to save a lot of peoples butts, they wouldn't give a 48 hour notice if they had a better option.
That being said, I'm very curious to see what info is released next week.
- dvidsilva 12y agoyeah, we had a few minutes downtime but nothing too bad; definitely rather have some few time off than a security threat.
- fleitz 12y agoYup, fundamentally it's not following best practices vs. a few minutes of downtime. It's a far better call than not forcing the update. Of course all the people who built shoddy cloud presences are going to be screaming blue murder that their 'oh so successful' but 'couldn't be fucked to run in multiple AZs' businesses are going to be down for a few minutes. It reminds me of doing tech support during the dotBomb, every daytrader would phone about how they were losing thousand per second while their internet was down, I'd ask them to switch to their backup connection, and then explain that they had the cheapest residential connection available that's inappropriate for day trading and that if they are making thousands per second they should have a backup connection in place. Then I'd upsell them on a business package and have a guy there in 24 hours.
- madaxe_again 12y agoYou get reimbursed?!?! We've been pleading for several months now for a service credit or at least an acknowledgment that they screwed up. Discovered an arcane issue with ARPing to elasticache from within a vpc. Cost us ~$8000 in instances we left running at their request to diagnose, and about the same in man time from our side. Took them 6 weeks to diagnose, too - bloody pathetic. We spend $30k a month with AWS and they treat us like crap. The tech is ok, but their communications and customer service are mindblowingly atrocious. If I can give one bit of advice - don't pay for either their support or an account manager. They don't provide either, and their staff turnover is severe, so your account manager will be a noob to their business every few weeks.
- nicobn 12y agoWhen a script mistakingly provisioned a ridiculous amount of read/write capacity on hundreds of DynamoDB tables, we were presented with a bill in the thousands of dollars. We got reimbursed after talking with our account manager for 15 minutes. Maybe my experience is the exception, but my account manager has always been extremely helpful at resolving whatever issues we had.
- jlouvel 12y agoWe had a similar experience regarding DynamoDB.
- theshrike79 12y agoHow much do you have to spend on AWS monthly to get an "Account Manager" you can call?
- nicobn 12y agoWe had one with barely $7,000 of spending per month, but it might be because I already had my foot in the door with a previous account that brought them about $40,000/month.
- npinguy 12y agoI apologize for your poor experience with Amazon, and have no doubt that many mistakes were made with your account. But you should recognize that your experience is the exception not the rule. The vast majority of customers have nothing but good things to say, and Amazon works tirelessly to maintain that reputation.
- xtrumanx 12y agoNot sure if you actually work for Amazon, but your apology would probably be worth something if you actually decided to take steps to rebuild Amazon's reputation with madaxe_again rather than telling them they're the exception not the rule.