WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

455

(post is archived)

[–] 4 pts

Use the jew, you lose!

[–] 1 pt

Cuck to Jews

Get the screws.

[–] 3 pts

How the fuck could they do that with all their shit suspended?

Fuck AWS. I am actively shutting down our company shit with them. I was just tolerating it, without personally buying any more things from amazon, but now they can get by without our $30k a month on AWS crap that would be better served elsewhere anyhow.

[–] 1 pt

So I guess azure?

[–] 2 pts

I...

You know what's embarrassing. I literally did consider that for a moment, but we had SO MUCH downtime last time we used them, AND it cost about twice as much as AWS... so probably not.

We have a colo down south where we could build out a little more of our own hardware so I'm going to have my guys do that, but that's not a replacement for AWS, obviously, just for some systems which can be in one place or whatever. Dunno what I'm going to do for CDN shit just yet. S3 and Cloudfront are kind of decent for that kind of thing. Pretty sure I'll leave that for last. Civilization will probably be over by that point and it won't matter anymore anyway, so... winning?

Managed Vps are so much fvcking cheaper than those two giants

[–] 0 pt

I wonder if you could roll your own and build your own hard/software for $30,000/month? Hell, you could probably hire experts in the field to do it for you for that kind of cash. Plus you get your own personalized shit.

Because they shut down a part of their service creating a hole in the other part?

[–] 2 pts

Good. If that is the case it just illustrates how shit AWS security is and provides another reason not to use it!

[–] 1 pt

no, that cannot be right, for the dns to work with a local balancer on amazon it must still be active, that cannot be it. either they had dns entries for their background servers that were not on AWS so they were still up and the "hackers" discovered that and that would happened just the same if they had just copied the DNS zone before it was shut down or they changed the entries when it was shut down and then it is their own fault, maybe to put a error message page up.

In any case, it is not the fault of amazon and it is not deliberate.

[–] 0 pt

The backup servers were registered with Amazon, and were not Amazon servers. So, when Amazon took down the Amazon-servers, Amazon automatically routed people to the backup servers. Otherwise, no one would ever have known who those servers were.

Essentially, Amazon told everyone trying to connect to Parler, who the backups were. It wouldn't have told them before the Amazon-servers were down. And it shouldn't have told them ANYTHING after, but unfortunately, it did.

[–] 0 pt

They make huge piles of cash money off Amazon Web Services every time you click on someone's site using it - and you can block that from your home.

https://bigboy.us/other/aws/

Censor amazon

[–] 2 pts

Parler is run by retards who tried to capitalize on the Twitter-alternative conservative market.

[–] 0 pt

Parler people were twenty years out of date Imagine. wanting to use communist jewamerican big business. The progressives that want them dead are going to let them be conservative and promote family over child trafficking. Not likley.

[–] 0 pt

Nah, that's gab. They're actively feeding off people who can't wait for Parler to come back.

[–] 1 pt

that claim is bullshit, DNS is not even necessary to attack the sites, this works with cached DNS entries and the IP addresses

[–] 0 pt

You misunderstand - no one was being routed to their backup servers. No one had their addresses cached. And if Amazon had brought down their DNS at the same time that they brought down their Amazon servers, then no one would ever have known who those servers were.

[–] 0 pt

how does the DNS help to discover hidden servers when they are not listed in DNS?

[–] 0 pt

That's what they are saying. They WERE listed, as backups. So, you would never have been routed to them, if the main servers were up. Only because Amazon took the servers down, their own system failed-over to the backup servers. Exposing them.

[–] 1 pt

Amazon failed. They deserve to be sued for damages. Award Parler. Let it go. It's done.

[–] 0 pt

Allegedly, AWS is run on Amazon's own hardware. Switches, routers, OSes - everything designed and built by Amazon.

[–] 0 pt

I bet this leads to a defamation suit.

If you are fucking stupid enough to use Amazon as your host - you get what you deserve.

this is not at all how route53 works but ok

[–] 0 pt

If I am not mistaken- everyone that verified via driver’s license, Telephone number, and email address had their info spread far and wide, correct? Doesn’t that make the investors liable- assuming their user agreement states they do not retain that information....?

Load more (1 reply)