I also block AWS/EC2 on my servers because it's a relentless source of badly behaved bots, freeloading SEO scrapers, and poorly misguided startup ideas (no, I d

I also block AWS/EC2 on my servers because it's a relentless source of badly behaved bots, freeloading SEO scrapers, and poorly misguided startup ideas (no, I don't want you to proxy SSL connections for my users--just think about it for a second, for crying out loud). Now with Fire & Silk in the mix, how do you even go about protecting your content from Amazon, if they can get it directly from the browser, cache it, and make it available to their own paying customers (who might have been blocked by your firewall, for whatever reason)? I can accept that since it's technically possible, they'll just do it, and resistance is futile. But if you want to locate bad netizens, AWS/EC2 is an excellent starting point. Remember, this isn't just about publicly-available content, it undermines the entire trust model of TLS/SSL (and exposes some of its underlying weaknesses, hopefully spurring development of a better solution in the long run).