New S3 Objects give 403 Forbidden in Cloudfront

New S3 Objects give 403 Forbidden in Cloudfront

A common problem with Amazon CloudFront and Amazon S3 hosting deals with negative TTLs. Matthew from Blue Matador outlines the steps needed to correct this problem._x000D_

    _x000D_
  1. Understand eventual consistency in S3. New items may take time to propagate through redundant systems and be available in all locations._x000D_
  2. Understand CloudFront's default policy for handling errors, like 403 forbidden, is to cache that error for 5 minutes._x000D_
  3. The solution is to modify distribution settings in CloudFront._x000D_