Live data from Hacker News

AWS drops bandwidth pricing

aws.amazon.com

91–96 of 96 posts

Re: AWS drops bandwidth pricing

#91
post #3

Good lord, about time. Why was incoming bandwidth ever on the list?

Because incoming still takes up bandwidth so it makes sense to count it is such. I however do remember it being free at some point in time.

It's in their best interest to get as much in as possible considering they charge for storage and deletion.

Re: AWS drops bandwidth pricing

#93
post #73

Earlier quoted context omitted.

Shitloads of rogue bots doing "social media monitoring". Shitloads of rogue bots stealing content for black-hat SEO. Shitloads of rogue bots harvesting email addresses. Shitloads of rogue bots submitting spammy replies.

So maintain a blacklist of elastic IPs. If it's too big for you, make it a community effort. Those are bad reasons to close your site to all of AWS. As nupark2 mentioned, there are legitimate users routing traffic through EC2, even some bots that you'd want to visit your site. Archive.org comes to mind (many of there scrapers are or were behind AWS). Closing your site or app to a large swath of the web is the wrong s…

Unlike the assumptions you're limited to making, I know how much of my AWS traffic is human, and it's really very very very small. The sad reality is I'm sick and tired of rogue bots, and the tiny sliver of collateral damage can fill out the CAPTCHA validation every so often.

(I also blacklist GWS, rackspace, linode, softlayer, reliablehosting, ovh.net, node4, netdirect, layer42, all TOR exits... it's actually a pretty huge list.)

Re: AWS drops bandwidth pricing

#94
post #59

Earlier quoted context omitted.

Shitloads of rogue bots doing "social media monitoring". Shitloads of rogue bots stealing content for black-hat SEO. Shitloads of rogue bots harvesting email addresses. Shitloads of rogue bots submitting spammy replies.

That's unfortunate. I don't know what the answer is, but real people do route their traffic out of AWS endpoints.

Far fewer than you might think.

Re: AWS drops bandwidth pricing

#95
post #73

Earlier quoted context omitted.

Shitloads of rogue bots doing "social media monitoring". Shitloads of rogue bots stealing content for black-hat SEO. Shitloads of rogue bots harvesting email addresses. Shitloads of rogue bots submitting spammy replies.

So maintain a blacklist of elastic IPs. If it's too big for you, make it a community effort. Those are bad reasons to close your site to all of AWS. As nupark2 mentioned, there are legitimate users routing traffic through EC2, even some bots that you'd want to visit your site. Archive.org comes to mind (many of there scrapers are or were behind AWS). Closing your site or app to a large swath of the web is the wrong s…

I whitelist archive.org, and they've never hit through AWS.

Re: AWS drops bandwidth pricing

#96
post #69
post #58

Earlier quoted context omitted.

I don't think this is accurate. I have seen download speeds of around 6/8MBps on windows micro instances. The lowest I got was around 3MBps. But I only tried with downloads of around 30MB files at the maximum.

This wget -O /dev/null http://cachefly.cachefly.net/100mb.test gives me about 30 MBytes/s from a micro instance in EU-West

Sorry yeah it looks like my test was disk IO bound rather than network bound.
Post reply on HN