- 最新
- 最多得票
- 最多評論
Hello.
If you contact AWS support, using the following wording should help the process go smoothly.
https://repost.aws/ja/questions/QU3RJ4JmatQM2p8V7uDvAchw/ssl-setup-failed-both-root-and-www-stuck-on-expired-2023-amplify-distribution-cname-already-associated-with-different-resource-confirmed-not-in-my-cloudfront-account
I've experienced the same error before, but it resolved itself automatically after waiting 2-3 hours.
It's possible that AWS is causing delays in the deletion process due to internal reasons.
By the way, I recommend checking not only CloudFront but also Amplify to see if it has been configured.
If the domain in question is being used in Amplify, a duplication error will occur.
When you encounter the error "One or more of the CNAMEs you provided are already associated with a different resource," it means the alternate domain name is currently associated with another CloudFront distribution or distribution tenant, which could be in your account or a different AWS account.
To resolve this situation, you have a couple of options:
If you have access to the source distribution: You can move the alternate domain name from the existing resource to your target distribution. This process involves setting up your target distribution properly, locating the source distribution that currently has the domain name, and then moving it. The move can be done between standard distributions and/or distribution tenants.
If you don't have access to the source distribution: Since you've confirmed the domain isn't in any distribution in your current account and you own the domain through Route 53, this suggests it may be associated with a resource in a different account (possibly an old account you no longer access). In this case, AWS Support is the appropriate path to resolve the issue.
Since you've already opened a support case, that's the correct approach. For your existing case, you can add additional correspondence through the AWS Support Center (https://console.aws.amazon.com/support/) if you need to provide more information or check on the status. If you find response times are longer than needed for your business requirements, you might also consider reviewing your AWS Support plan options, as higher-tier plans typically offer faster response times for these types of requests.
AWS Support has the tools to verify domain ownership and release CNAME associations when appropriate, which is necessary when the domain is stuck on an inaccessible distribution.
Sources
Move an alternate domain name - Amazon CloudFront
已回答 3 個月前
