Hacker News Reader

Comment by mgaunard | Hacker News Reader

My understanding is that S3 egress is only a problem if you need to take data out of AWS, which you can simply avoid by having some kind of dedicated AWS direct connect or some such to route the traffic yourself?

View on HN

Connecting to an AWS egress point for direct connect reduces the egress price (about half) but doesn't eliminate it. It also costs thousands of dollars a month just to have the connection, so it's not great for small operations. :-/

To my knowledge direct connect is a fixed cost, as is running your own dedicated infrastructure, so you don't pay for bandwidth.

I just pulled the DirectConnect prices from the AWS API, and I think there is still a per/GB charge. Here's a description of a random direct connect point in Amsterdam (Equinix AM3). https://gist.github.com/arashpayan/a91c46c3787ac610e7884b77b...

If I'm reading the description correctly, egress from there is 2 cents/GB, while the regular price for egress (less than 10 TB) from eu-south-1 is 9 cents/GB.

That's Milan to Amsterdam though. Aren't there some mechanisms to have a handoff as close to Milan as possible?

I was pretty sure there was a way to have something that's just a fixed cost, maybe with a partner third party service.

Yeah, you're right. A direct connect in Milan at Equinix ML2 is $2.48/port-hour.

> "description": "$2.48 per connected HC-10G port-hour (or partial hour) (EU (Milan), Equinix ML2, Milano, Italy)"

https://gist.github.com/arashpayan/b115e834191fbc89ac1bc1cdc...

Reply on news.ycombinator.com