101–110 of 173 posts
>For years, I’ve watched developers on Reddit and Facebook desperately seeking US or EU billing addresses, willing to pay $100+ premiums to avoid MENA region assignment. >When I asked why, a colleague warned me: “AWS MENA operates differently. They can terminate you randomly.” Huh.
(I did have to look it up.)
Editorial comment: It’s a bit weird to see AI-written (at least partially; you can see the usual em-dashes, it’s-not-X-it’s-Y) blog posts like this detract from an author’s true writing style, which in this case I found significantly more pleasant to read. Read his first ever post, and compare it to this one and many of the other recent posts: https://www.seuros.com/blog/noflylist-how-noflylist-got-clea... I’m not mu…
BTW, I actually use the em-dash symbols very frequently myself — on a Mac and on Android, it's very easy through the standard keyboard, with Option-Dash being the shortcut on the Mac.
If you are given only 5 days to comply with some request, that's how complicated your infra at AWS should be - so you can migrate to another provider in that time. Just use EC2 and basic primitives which are easy to migrate (ie S3, SES)
My fear of this sort of thing happening is why I don't use github or gitlab.com for primary hosting of my source code; only mirrors. I do primary source control in house, and keep backups on top of that. It's also why nothing in my AWS account is "canonical storage". If I need, say, a database in AWS, it is live-mirrored to somewhere within my control, on hardware I own, even if that thing never sees any production t…
I often have my git configured to push to multiple upstreams, this means that basically all of your mirrors can be primaries.
This is a really good part about GitHub. Every copy is effectively a mirror, too, and it's cryptographically verified as well, so, you don't have to worry about the mirror going rogue without anyone noticing.
Earlier quoted context omitted.
EC2? S3? Yes. That kind of "cloud" tech was invented at AWS. Nothing like the ec2 API existed before Amazon. It's what made AWS big. Maybe my graybeard is showing, but I remember when that kind of pre-containerization cloud provisioned VM resources was a radically new idea.
FreeBSD jail predates Amazon Web Services, and so does SWsoft's Virtuozzo that was subsequently open-sourced as OpenVZ. For Amazon SES, DJB's qmail made it possible to send a ridiculous amount of subscription emails very efficiently, too. I've been using a VPS powered by Virtuozzo since like 2002 or 2003, how is EC2 all that different? Just the API? Per https://en.wikipedia.org/wiki/Virtuozzo_(company) , SWsoft was f…
This is smelling like the classic "Dropbox isn't anything new" HN comment.
TODAY amazon services are just re-packaged OSS packages, yes. That wasn't the case before.
Earlier quoted context omitted.
Happened to me as well (permaban). Without any warning. You can request via help site data takeout under ccpa or gdpr. Took about two weeks but i got all my data
You still get access to log in and delete comments. I'll probably just use a tool to delete all my comments. Fuck em.
Earlier quoted context omitted.
You still get access to log in and delete comments. I'll probably just use a tool to delete all my comments. Fuck em.
i can't login. i can change password but no login for me.
I started losing my shit at people posting anti trans hysteria. Part of me wants to send spez a bill for 14 years of deleting dick pics and local kkk posting. And then there was COVID...
Earlier quoted context omitted.
The lede buried under that lede is that (according to an insider?) some AWS employee accidentally wiped everything immediately (contrary to typical practice in such situations of retaining data while things get sorted out), leading to a chain of brushing-off / covering-up percolating through whatever support chain the OP was talking to.
That does seem to be a mistake on their part. And the comms we’re seeing look bad. But the overall post and the double buried ledes make me question the degree to which we’re getting the whole story.
Right or wrong, those messages look like very standard AWS-speak for "this is your mistake, not ours".
I have no idea if that's a reasonable stance or not, but I _will_ say that AWS's internal culture contributes to this sort of bad press. If they would respond to their customers with even a trace of empathy and ownership, this post would likely never have been written.
The amount of self-aggrandizing and lack of self awareness tells me this author is doing to do all of this again. This post could be summed up with "I should have had backups. Lesson learned", but instead they deflect to whining about how their local desktop is a mess and they NEED to store everything remotely to stay organized. They're going to dazzle you with all of their hardened bunker this, and multiple escape r…
> I’d done everything right. Vault encryption keys stored separately from my main infrastructure. Defense in depth. Zero trust architecture. The works.
Did you? Is putting all your eggs in one basket "defense in depth"? Is total trust in AWS "zero trust architecture"?
I'm not defending AWS here; they fully deserve all the fallout they can get from this, and I do feel for the dev who lost all their stuff through AWS's fuckup. Lots of people do the same.
My current employer does the same. It's a major bank, and all of their stuff is Microsoft. Azure, SharePoint, Office, Teams, the works. I think it's foolish to trust a single foreign company with all your vital data and infrastructure, operating in q country where the government demands access to everything, but this is what everybody does now.
We trust "the cloud" way too much, and expose ourselves to these sort of fuckups.
Earlier quoted context omitted.
The author doesn't grasp what putting all your eggs into one basket means: > Before anyone says “you put all your eggs in one basket,” let me be clear: I didn’t. I put them in one provider, with what should have been bulletproof redundancy: That's one basket. A single point of failure. "But it should have been impossible to fail!" Backups are to handle the "impossible" failure (in reality nothing is 100% reliable).
This one time, traveling through Asia, a simple merchant transaction triggered a fraud alarm on my card. The default for my bank at the time was to cancel my card automatically. This was before the days where cards could become unblocked. I had to travel to another city to pick up a new card in 10 working ways. This was a Mastercard credit card. I thought I was smart traveling with both a mastercard and a Visa card.…