Route53 custom domain not updating content
I am using a s3 bucket to serve a static site. I update my bucket via a bitbucket pipeline when change are made on the main branch. The s3 bucket domain name is serving the correct content and updating accordingly.
I am using cloudfront to manage my custom domain (via route53) & my SSL cert(via AWS cert manager)
I have set up an invalidation on cloudfront for all content ( i.e '/*') which is working correctly. For example the cloudfront distribution domain name is serving the correct content and updating accordingly.
However, the custom domain name (Alternate domain name (CNAME)) is not updating when S3 and cloudfront are??
Is my custom domain also caching somewhere, and I need to make changes to the configuration?
It sounds like connecting to the "d123444.cloudfront.net" domain shows correct content. However, using custom domain name to connect shows outdated content. In CloudFront distribution -> behaviors, what caching policy or legacy setting configured? Is it containing host header?
Hey. The cloudfront distribution behaviour is showing:
Cache policy and origin request policy (recommended)
Cache policy CachingOpyimized
Old S3 Content Being Served, Help!asked 5 months ago
Trying to serve https but getting: 403 the request could not be satisfiedasked 3 years ago
Access denied when trying to GET objects uploaded to s3 bucket via aws sdk using cloudfrontasked 6 months ago
Route53 custom domain not updating contentasked 2 months ago
Route 53 domain cname record without hosted zoneAccepted Answerasked 8 months ago
Error in bucket naming rules for hosting with domain with special chars?asked 2 years ago
S3 Static Website RoutingRules when using Cloudfront and a domain nameasked 3 years ago
How to use https with S3 (Alternate Domain Names) and Cloudfrontasked 3 years ago
"www" address of websiteasked 3 years ago
Certificate request getting failedasked 2 months ago