We are facing an issue with an AWS CloudFront distribution where we have run out of behaviors. Our current configuration creates a separate behavior for each page or group of pages that requires specific caching settings. For example:

We are facing an issue with an AWS CloudFront distribution where we have run out of behaviors. Our current configuration creates a separate behavior for each page or group of pages that requires specific caching settings. For example:

I have an organization with the following structure (simplified for this)

I want to give both, read and write access to my AWS CloudFront distribution but via separate signed urls. Aka a signed url only for reading and a signed url only for writing. Is this possible? Because the NPM package @aws-sdk/cloudfront-signer only has the getSignedUrl function which does not seem to have this feature. Thanks.

I have my main site at WPEngine hosted and a React based webpage hosted on S3.
Domain is setup on Route 53, I have created a cloudfront with 2 origins.

I want to know bytes transferred to the user by CloudFront in the response body. I want this for each individual user viewer response, not just an aggregated metric of overall CloudFront usage. Also, I’d like to get it immediately and programmatically, not in a delayed fashion, say, from a CloudWatch log. My goal is to bill each individual user a data transfer charge that’s based on the data transfer charges that I pay, assuming that I’ve passed the 1TB per month free CloudFront tier, and I want to show these charges to them immediately so they can see them accumulate on a request-by-request basis.

I have a S3 bucket with Cloudfront in front of it (mainly so that I can use a nice custom domain name to access it whilst still having HTTPS support). It all works beautifully when accessing via a browser. But whenever I use any kind of HTTP client in code, the request never returns and times out.

I am currently hosting my website on an S3 bucket, I have GitHub actions and an IAM user updating the bucket whenever theres an update. I am using Cloudfront for content delivery and the generic xxxxxxx.cloudfront.net domain works. However I have a custom domain that I assigned as an alternate domain that does not work. I’ve been trying to fix this for the last two days but had no luck.

I created a couldfront distribution and I get an access denied error.