1 Answer
- Newest
- Most votes
- Most comments
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.
answered a year ago
Relevant content
- CloudFront - One or more of the CNAMEs you provided are already associated with a different resourceAccepted Answerasked 5 years ago
- Accepted Answerasked 9 months ago
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- How do I update a CloudFormation stack that's failing because of a resource that I manually deleted?AWS OFFICIALUpdated 3 years ago