Skip to content

Residual Forwarding Rules from Domain Transfer

0

Before transferring my domain to AWS I added a forwarding rule to my GoDaddy Domain toa cloudfront instance hosting a static version of my site. Now, after the transfer I connected an amplify instance with my react app to the domain.

https://<mydomain>.com works and puts the react app to the screen but http://<mydomain>.com didn't work and loaded the cloudfront resources. I've since disconnected the app from the domain and disposed of the cloudfront instance to try to resolve the issue on it's own. Does anyone know how to resolve this?

I just want to deploy my react app with the option to use http or https, any recommendations are welcome.

Process:

  1. Deployed vanilla static site via cloudfront and s3
  2. While domain was in GoDaddy used a forwarding rule to route traffic to the static site
  3. By the time the domain had loaded into AWS I had written a React App
  4. Recommended resource for deployment was amplify, so I deployed there
  5. Attached domain for and started testing
  6. https:// worked but http:// still forwarded to the cloudfront distribution
1 Answer
0

HI - can you please elaborate on what the set up looks like in terms of origin etc. Amazon CloudFront provides the capabilities required to set up a secure static website. Amazon S3 static websites support only HTTP endpoints.

AWS
EXPERT
answered 3 years ago
  • I've updated my post to describe exactly what I did. What would you recommend?

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.