Going to paths directly NoSuchKey via cloudfront.

[karldanninger]

When I try to go to www.example.com/about i get the following error.

If I go to the about screen from the root, it seems to work fine.

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>about</Key>
<RequestId>87567F3A5B8</RequestId>
<HostId>
WAwgYKUgEPo7nwoqu3nbKemGq58TEVeo2KazhpN2G03YW/iIAol6lxTGOZ+NAUfRdjcOp0=
</HostId>
</Error>

[karldanninger]

I seem to have solved this by changing the cloudfront origin name to the S3 URL

www.example.com.s3-website-us-east-1.amazonaws.com

I hope I didn't break anything by doing so.

[karldanninger]

This seemed to help my understand https://stackoverflow.com/questions/34060394/cloudfront-s3-website-the-specified-key-does-not-exist-when-an-implicit-ind

[jariz]

Yes, like our cloudfront docs state using the "website" endpoint instead of the "normal" S3 origin is required for many features that the plugin offers to work.