1 Answer
- Newest
- Most votes
- Most comments
0
It looks like the Amplify service team is aware and working on this issue: https://github.com/aws-amplify/amplify-hosting/issues/2846
answered 2 years ago
Relevant content
- Accepted Answerasked 7 months ago
- Accepted Answerasked a month ago
- asked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
Deleting the custom domain and readding it worked, but still wondering how we got in this situation to begin with. Would appreciate any insight!
We're seeing exactly the same issue, and it seems to have started around when this post was made. I'd rather avoid deleting/recreating the custom domain if we can - are there any other suggestions for how to resolve this?