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
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago