2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
This was never resolved. In the end I had to re-create the domain with new names and change configurations elsewhere to match.
con risposta 2 anni fa
0
Best course of action in situations like this is to open a Support ticket from the AWS Account where you're experiencing this.
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
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.