Hacker News Reader

Comment by whinehands | Hacker News Reader

This doesn't block any site using AWS, only sites which are fronted by a server hosted within AWS.

I've toyed with the idea of setting up a no-FAANG VPN that implements these restrictions based on the ip networks advertised by the relevant ASNs. This would provide more complete coverage, and be useful as a testing tool, allowing you to verify that your own web properties still function without assets being loaded from a global active adversary.

That actually is a great idea.

It still doesn't actually block everything on those clouds. I can go get my own ASN, run my own edge server (or use a small CDN company not on your list) and use whatever I want on the back end for database, queue, backup, storage, compute, etc. All you'll know my IP is where the edge node is.

A VPN would still be effective at suppressing the tracking effects of all the "like buttons" while also revealing issues such as jquery being loaded off a CDN that also directly hosts content for 40% of the web.

For users wanting to thwart pervasive CDNs from receiving packets every time they visit almost any site on the web, it's matters less if a service they visit is using an amazon resource on the back end; as long as all services aren't using the same database backend, this puts e.g. AWS back in the position of only having a little of your consumer/browsing information instead of nearly all of it.

i would be willing to throw up to $50 for this

Someone didn't get an offer!

Please ping me if you ever get this set up.

It still wouldn’t stop an application where some back end or data store is using AWS.

Reply on news.ycombinator.com