2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
This was never resolved. In the end I had to re-create the domain with new names and change configurations elsewhere to match.
beantwortet vor 2 Jahren
0
Best course of action in situations like this is to open a Support ticket from the AWS Account where you're experiencing this.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
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.