2 Answers
- Newest
- Most votes
- Most comments
0
This was never resolved. In the end I had to re-create the domain with new names and change configurations elsewhere to match.
answered 2 years ago
0
Best course of action in situations like this is to open a Support ticket from the AWS Account where you're experiencing this.
answered 2 years ago
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 months ago
I would - but apparently it requires more than a basic plan because it falls under technical support. This is frankly ridiculous since it essentially means that I have to pay AWS to fix their offered service that I already paid for.