Comment by VectorLock

I'm kind of surprised that people are this upset about how much AWS charges for bandwidth. They may charge more for bandwidth than a colo would but they're not a colo. A colo you get a network port and -thats it- you provide everything else yourself, with its attendant cost, and you roll that up into your total bill.

If a colo provides you a 1 Gbps connection if you use less, you don't get a refund. And most of the time you don't get 24/7 saturation, or you get charged on some 95th percentile billing, and their networks are almost always oversubscribed anyways.

AWS is trying to disincentivize using it as a dumb pipe. They want you to use it smartly and if you just want to push static data there are much more cost effective ways to do it, such as CDNs, which are more cost effective for both you AND AWS.

Comparing AWS bandwidth costs and Colo and even other clouds like Oracle isn't fair because different things are associated with that cost.