1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Answering my own question in case this is an issue for someone in the future.
When creating the API GW Custom Domain, the "edge" endpoint was used which fronts a CloudFront distribution to API GW. CloudFormation would then later attempt to create another CloudFront distribution for a CNAME that is already in use, find the error, then rollback.
By setting this configuration to "regional" instead of "edge," this error resolves.
con risposta un anno fa
Contenuto pertinente
- Come posso risolvere l'errore "Custom Named Resource already exists in stack" in AWS CloudFormation?AWS UFFICIALEAggiornata 2 anni fa