Cloudfront responded AccessDenied or NoSuchKey

Question

For example,
1.
https://d2u87yfqb01lll.cloudfront.net/test/
Returns AccessDenied error.

But the URL below is done responding successfully.
https://d2u87yfqb01lll.cloudfront.net/test/index.html

2.
https://d12dcz4jiki7qg.cloudfront.net/%e2%80%aabitcoin-straight-up-gave-me-the-middle-finger-today%e2%80%ac-reddit-bitcoin/
Returns NoSuchKey error.

But the URL below is done responding successfully.
https://d12dcz4jiki7qg.cloudfront.net/%e2%80%aabitcoin-straight-up-gave-me-the-middle-finger-today%e2%80%ac-reddit-bitcoin/index.html

Both are setup correctly.
I enbaled S3 hosting for the contents(index.html as the default page is setup).
Made the bucket and all the objects under the bucket public access.
ACL are both enabled.
Cloudfront has default root object.

Please let me know which steps I might have missed.
Many thanks.

Answer

CloudFront allows you to specify a default root object like index.html, but it only works on the root of the website (such as http://www.example.com > http://www.example.com/index.html). It does not work on any subdirectory (such as http://www.example.com/about/). When you make a request like this, CloudFront makes a GetObject request to S3 for an object that doesn't exist.

You can implement default document functionality for subdirectories via Lambda@Edge. Please refer to this blog post: https://aws.amazon.com/blogs/compute/implementing-default-directory-indexes-in-amazon-s3-backed-amazon-cloudfront-origins-using-lambdaedge/ for details.

Answer

Now, I still can't access https://d2u87yfqb01lll.cloudfront.net/test/
But the situation changed.
It popped up a download dialog with 0 byte.
Seems some tech guys are fixing this bug.

https://d12dcz4jiki7qg.cloudfront.net/%e2%80%aabitcoin-straight-up-gave-me-the-middle-finger-today%e2%80%ac-reddit-bitcoin/
Still returns NoSuchKey error.

Cloudfront responded AccessDenied or NoSuchKey

相關內容