Live data from Hacker News

AWS Restored My Account: The Human Who Made the Difference

seuros.com

91–95 of 95 posts

Re: AWS Restored My Account: The Human Who Made the Difference

#91

Earlier quoted context omitted.

The article says so: > AWS blamed the termination on a “third-party payer” issue. An AWS consultant who’d been covering my bills disappeared, citing losses from the FTX collapse. The arrangement had worked fine for almost a year—about $200/month for my testing infrastructure. He essentially got screwed over by the consultant. Everything else is a side-effect but not material to the cause.

Immediately after that it clearly states there was an alternate payment on file, and the termination was not handled like a payment issue.

AWS has no such thing. It also is not an alternate either way since the owner of the first payment method would have this in an MPA, not in a member account, and in AWS, member accounts are not considered payers and any payment methods are ignored.

The article makes a variety of claims, some of which can be dismissed because they factually do not exist with AWS, and some of which cannot be verified at all. But precedent shows that when your middleman in a savings scheme drops out, you are screwed, and that is what happened here.

That doesn't make this fun, and it would be better if everyone had a personal account manager, but that's not the reality of today.

Re: AWS Restored My Account: The Human Who Made the Difference

#92

Earlier quoted context omitted.

> July 10: AWS sends verification request. 5-day deadline (including weekend). > July 14: Form expired. I contact support. Simple question: “What do you need from me?” > July 16-20: Four days of silence. Then: “We’re escalating to the appropriate > team.” > July 20: New form finally arrives. > July 21: I submit ID and utility bill (clear PDF). Response time: 10 hours. > July 22: AWS: “Document unreadable.” The same P…

July 10: Fill out the form.

July 14th, at first glance falls within the stated 5 day deadline.

Re: AWS Restored My Account: The Human Who Made the Difference

#93

One of the questions we always ask of cloud hosted companies what their plan is in case they ever lose their cloud account. Typically this is met with incredulity: nobody has ever lost their AWS account and all it's data? Right? Right??? Well, not normally, no. But it does happen. Not often enough to be a meaningful statistical issue, but if it were to happen to you then a little forethought can turn a complete disas…

We have a slack channel with more than 20 external @amazon.com engineers and salespeople that instantly respond to all our queries, sometimes proactively inform us of stuff or offer advice... Doesn't everyone has this?

> Doesn't everyone has this?

What you're asking is “Isn't everyone a giant corporation?”

Judging from the incredulous tone of your question, the answer may come as a surprise to you: No, not everyone is a giant corporation.

(Sheesh...)

Re: AWS Restored My Account: The Human Who Made the Difference

#94
post #50

Author here: Let’s be clear on backups: Yes, I had backups everywhere. Across providers, in different countries. But I built a system tied to my AWS account number, my instances, my IDs, my workflows. When that account went down, all those “other” backups were just dead noise encrypted forever. Bringing them up to the story only invites the 'just use your other backups' fallback, and ignores the real fragility of cen…

> When that account went down, all those “other” backups were just dead noise encrypted forever.

How and why? Are you saying you had encrypted backups on other providers, but... Didn't keep the encryption keys to those backups somewhere handy and unencrypted? Why not? Can you even call that “backups”?

BTW, this is the first time in all this saga I've seen you mention other providers. Smells fishy.

Re: AWS Restored My Account: The Human Who Made the Difference

#95

Earlier quoted context omitted.

July 10: Fill out the form.

July 14th, at first glance falls within the stated 5 day deadline.

Depending on the user’s time zone, it could already be July 15th somewhere (where the form is hosted) when the user is still in July 14th.
Post reply on HN