amazon-cloudfrontaws-lambda-edge
Lambda@Edge - You cannot update the specified distribution using this API version because it is associated with a cache policy
I am trying to setup Lambda@Edge but getting the following error on clicking Deploy to Lambda@Edge button.
You cannot update the specified distribution using this API version because it is associated with a cache policy.
My CloudFront distribution is already ready and is in Deployed state.
Can someone please help me with this issue?
Solution
I was able to solve this by switching to 'Legacy cache settings'. I got the lead from this link: https://forums.aws.amazon.com/message.jspa?messageID=950582
- CloudFront charges after you invalidate your distribution over 1,000 times, does the count reset each month?
- HTTPS connections to cloudfront / S3 using godaddy domain
- Why is GetMetricData returning an empty set of values?
- Are there any difference between amazon cloudfront and amazon s3 transfer acceleration?
- The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions
- Next js 14 app router always Hard refresh when behind cloudfront
- Access Denied on Cloudfront signed URL for a private S3 bucket
- CloudFront policy to invalidate only specific distribution
- Restrict access to a particular CloudFront distribution using IAM
- CloudFront / S3 ETag: Possible for CloudFront to send updated S3 Object before the CF TTL has expired?
- Aws Php SDk - Create Cloudfront distribution using hard-coded credentials
- Issue with AWS Cloudfront and Woocommerce cart
- react app hosted in s3 doesn't update after deploy
- AWS cloutfront routing issue when including params
- Unable to send GET request with AWS Lambda & DynamoDB Rest API using serverless
- How do I serve index.html in subfolders with S3/Cloudfront?
- Is it possible to set Content-Security-Policy headers in Amazon S3?
- ns_error_net_interrupt in firefox but not in chrome
- When to use Amazon Cloudfront or S3
- Restricting access to CloudFront by IP
- Language specific 404 error page in cloudfront
- Do I need to move all my DNS records to Route 53 when I point Godaddy to their nameservers?
- Issues generating CloudFront signed URLs; always Access Denied
- AWS Amplify: How to delete the environment, when resources are already partially deleted?
- AWS CloudFront - "CORS header ‘Access-Control-Allow-Origin’ missing" for single S3 Resource
- AWS api 403 Forbidden in S3, Cloudfront
- 502 between cloudfront and elb (AWS)
- CORS Access-Control-* headers dropped from AWS Cloudfront Signed URL serving S3 bucket data on a custom domain
- AWS CloudFront Leverage browser caching
- AWS CloudFront err_too_many_redirects