I had the same problem.
I believe the default values written in the tab "Rewrites and redirects" are not correct.
If you look at the line for the 302 redirect, you will see:
- source address: https://your_domain.com
- target address: www.your_domain.com
You need to change the target address to: https://www.your_domain.com
Hope it solves your problem!
Not sure how to report it as a bug to the amplify team.
Edited by: boris13 on Apr 28, 2019 9:16 AM
Hi stephen and boris,
You're right, this is an issue on our end that we are working to fix! In the meantime, the above answer is correct. Add "https://" to the front of the custom domain target in the app rewrites and redirects page.
Please let me know if this still doesn't working for you.
That totally worked, thanks so much Boris & Dan!
Amplify redirect www to apexasked a year ago
www redirect in amplify console infinitely redirectsasked 4 years ago
Why can't i use A/AAA records to redirect a www domain to a non-www domain when the latter points to a cloudfront distribution?Accepted Answerasked a month ago
Amplify Next.js Redirectsasked 9 months ago
AWS Amplify Status 301asked 5 months ago
why www. prefix is required(must) with my domain hosted on AWS S3?Accepted Answerasked 3 years ago
WWW and Non-WWW is clashing in Wordpress. Help!asked 4 years ago
How can I serve CloudFront assets to a naked domain I manage with a non-AWS DNS provider?asked a year ago
How can I use Cloudfront with a root domain name?asked 3 days ago
Add a custom domain to AWS Amplify react-appasked 2 years ago