Hacker News Reader

AWS publishes which IPs it owns, so scrubbing headers is not enough for secrecy. (Not that doing something that relies on secrecy is a smart plan for a business, anyway.) https://isitonaws.com/

View on HN

Using your own ips works against you anyway - it’s easy for someone to backlist your ip range to keep people from seeing content that they don’t agree with. However blacklisting all of AWS, GCP, or Cloudflare breaks so many things that nobody does it - and that would be the same for any large CDN. DNS is still an issue but increasingly less so since all the work being done to bypass censorship by authoritarian regimes (aka keeping people from blocking internet ads) works just as well for controversial content.

I think you can bring your own public IP assignments to AWS. Wouldn't that do the trick? I mean, there's always tracerouting, I suppose.

You can‘t transfer single ips to aws, only complete networks. And then this networks is limited to a single region.

So it sounds easy, but is only usefull for companies with multiple networks. But even then i guess aws is publishing that they handle your networks.

Reply on news.ycombinator.com