Ways to reduce the costs of an HTTP(S) API on AWS

Re:Ways to reduce the costs of an HTTP(S) API on AWS by ajbeach22 on Friday December 13, 2019 @02:46PM (#21784714)

I wonder what the cost is compared to terminating SSL at Clodfront? For my web tier architectures, I use Cloudfront to reverse proxy both dynamic content (from the api) and static content (from s3). SSL is terminated only at CloudFront.

[ Parent | on HN ]

Re:Ways to reduce the costs of an HTTP(S) API on AWS by ball_biscuit on Friday December 13, 2019 @03:13PM (#21784961)

I don't think you can use Cloudfront to serve that kind of traffic. Cloudfront costs are described here: https://aws.amazon.com/cloudfront/pricing/

So for 10k HTTPS requests, the price is 0.01 $. If you serve 5 billion per day, that is 5000$ a day. With such high traffic I believe it is needed to handle it using performant webservers (Go, Erlang?) to keep costs reasonable, and probably terminating SSL at load balancer is the way to go

[ Parent | on HN ]

Re:Ways to reduce the costs of an HTTP(S) API on AWS by ajbeach22 on Friday December 13, 2019 @04:32PM (#21785727)

I am not sure that math is right. Using the aws cost calculator, its only about 1100/mo for 5B https requests. However, I think if you consider data transfer its still probably in the range of a several thousand a day. yikes.

[ Parent | on HN ]

Re:Ways to reduce the costs of an HTTP(S) API on AWS by Dunedan on Saturday December 14, 2019 @02:29AM (#21788309)

Not sure what calculator you're using, but from the pricing page [1] it's pretty clear that 5B HTTPS requests cost at least (depending on the geographic origin) $5000. And that's per day and without data transfer.

[1]: https://aws.amazon.com/cloudfront/pricing/

[ Parent | on HN ]