Billing question about CloudFront requests
An account is planing to configure CloudFront to house a large number of custom domains and terminate traffic to the CloudFront origin with a single CLB. To be a little more specific, the configuration will be as follows;
Before: client -> CLB
After: client -> CF* -> CLB
*CloudFront content caching is disabled in this scenario.
In this case, is it correct that the number of requests to be charged for After scenario is roughly twice the total number of GET/HEAD requests recorded in the Before Scenario? ("request for client -> CF" + "request for CF -> CLB")
CloudFront acts as a cache, so it really depends on the distribution of your unique requests. If you get a lot of requests to the same URL with the same parameters then you can set it up so that results in very few origin requests to your CLB. That could translate to some big savings on autoscaled instances behind your CLB for example.
Sorry for the insufficient explanation, but CloudFront content caching is disabled in this scenario.
CloudFront with EIP as originAccepted Answerasked 2 years ago
How to set Cloudfront custom headersAccepted Answerasked 2 years ago
How to connect a Lightsail instance to AWS CloudFront?asked 5 years ago
Amazon CloudFront serving compressed files with Origin server running NGINXAccepted Answerasked 2 years ago
How is a CloudFront origin deemed unavailable?asked 3 months ago
Cloudfront Origin SecurityAccepted Answerasked 3 years ago
CLOUDFRONT Failing to add Custom Originasked 2 months ago
CloudFront redirects (301) to custom origin (ELB) instead of cachingAccepted Answerasked a year ago
Can a CloudFront origin be another CloudFront distribution?asked 2 months ago
Billing question about CloudFront requestsasked 2 months ago