5 ms·
Plus $0.045 per gigabyte of data that passes through it. AWS has notoriously high egress fees.
by cj 3y ago
Plus $0.045 per gigabyte of data that passes through it.
AWS has notoriously high egress fees.
- CSSer 3y agoI ran into a SaaS company recently that had a guide for how to setup a white-label domain using route 53 and Cloudfront for one of their services. The SaaS company charges for service bandwidth usage, and they host their infrastructure on AWS, so if you opt to follow their guide they get a fat margin bump in the form of avoiding an egress charge and you get to be double-charged for bandwidth. You've gotta love it.
- cebert 3y agoHow are the avoiding egress costs? I am not completely following.
- dilyevsky 3y agoEgress to cloudfront is free on aws
- grrdotcloud 3y agoImagine a cloud transfer utility that made that easily possible?
- CSSer 3y agoIf I follow what you're saying I suppose my understanding could be wrong, but there's no "cloud transfer" required. It's just a matter of both the distribution and the configured origin being on AWS. If the origin doesn't direct traffic outside of the datacenter, AWS doesn't bill that as egress to whoever owns the origin. The Cloudfront distribution, on the other hand, will take the hit once it exceeds the free tier because it's the AWS service distributing data to end-users. It has to make a request to the AWS internal service then cache it, so The SaaS lambda or s3 bucket or EC2 instance or whatever they're using is none-the-wiser. It's just how the AWS billing mechanism works.
- dilyevsky 3y agoIt's not just egress in case of NAT - they charge you 4.5c per processed GB which means in both directions. This trips a lot of people up.
- tecleandor 3y agoWait what... Ingress too? :o
- dilyevsky 3y agoYes "ingress" too (quotes bc in this case it needs to be initiated from the vpc)