Getting a 403 on domain

Question

I used amplify to set up a new React site, amplify created everything, bucket, cloud front, etc, I put the CNAME in GoDaddy a couple of days ago, and I am still getting a 403.  I did something similar to a simple index HTML, I created a S3 bucket myself, put an index file there, and pointed another CNAME in GoDaddy to that bucket and it worked, issue seems to be Cloud Front in the middle.  I checked the set up multiple times, but again, it was done by amplify, so I am not sure what's missing.  OAI is there, bucket policy is there, CNAME points to the right CF name, etc.

Luiz Terra · Answer

To clarify, I used Amplify to create a React app, and also published the app using Amplify.  In turn, Amplify create the S3 bucket and the Cloud Front distribution.  Then I added the CNAME in GoDaddy to point to the Cloud Front distribution and that's it.  If there is a step missing here, I believe AWS needs to update their documentation.  I did the same thing manually and it worked, without a CF distribution, I created an S3 bucket, and added a CNAME pointing to that bucket, and it worked from the domain level.  I am using HTTP so far, non-secure, but again if there needs to be a cert and HTTPS to use this Amplify set up, it needs to be said somewhere.  I also changed the CF policy for both HTTP/HTTPS:
        "TargetOriginId": "hostingS3Bucket",
        "ViewerProtocolPolicy": "allow-all",

Behrens, Isaac · Answer

I would start by reviewing the following to resolve 403 errors using CloudFront.
https://repost.aws/knowledge-center/cloudfront-troubleshoot-403-errors

Hope this helps.

Getting a 403 on domain

Add your answer

Relevant content