A developer manages a website that distributes its content by using Amazon CloudFront. The website's static artifacts are stored in an Amazon S3 bucket.
The developer deploys some changes and can see the new artifacts in the S3 bucket. However, the changes do not appear on the webpage that the CloudFront distribution delivers.
How should the developer resolve this issue?
When a developer deploys changes and new artifacts are visible in the S3 bucket but not on the CloudFront-delivered webpage, it typically indicates that the CloudFront distribution is still serving content from its cache. To ensure that users see the latest content, the developer should invalidate the CloudFront cache. This process will force CloudFront to fetch the updated content from the S3 bucket instead of serving stale cached content. Therefore, setting CloudFront to invalidate the cache after the artifacts have been deployed to Amazon S3 is the correct solution.
By invalidating the CloudFront cache, you ensure that the latest artifacts in your S3 bucket are delivered to users, resolving the issue of outdated content being displayed.
C. Set CloudFront to invalidate the cache after the artifacts have been deployed to Amazon S3.