1 Answer
- Newest
- Most votes
- Most comments
1
Was able to solve this. I removed all of the dns based redirects from amplify, regenerated the hosted zone, and then also regenerated the amplify custom domain. Seems to have been a pure configuration issue
answered 3 months ago
Relevant content
- asked 5 months ago
- asked 5 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago