- Newest
- Most votes
- Most comments
I understand you're experiencing a CNAMEAlreadyExistsException when trying to associate your custom domain with your Amplify Hosting app, and you've identified that the conflict is with a CloudFront distribution in an AWS service account rather than your own account.
This situation occurs when alternate domain names (CNAMEs) are associated with a CloudFront distribution that Amplify Hosting manages internally. When you see a distribution in an account ending in a different number than yours, this is typically an AWS-managed service account used by Amplify.
For issues where domain associations are blocked by resources in AWS service accounts that you cannot directly access or modify, you'll need to work with AWS Support to resolve the conflict. Since you've already performed thorough troubleshooting (verifying DNS delegation, checking for duplicate zones, attempting the associate-alias API, and recreating your app), the next step is to engage support directly.
Please visit the AWS Support Center at https://console.aws.amazon.com/support/ to create a new support case or add correspondence to your existing case. When you do:
- Select Amplify Hosting as the service
- Provide the Amplify app ID, domain names, and the CloudFront distribution ID you identified
- Include the ListConflictingAliases output showing the conflict
- Explain that the blocking distribution is in an AWS service account you cannot access
The support team will have the tools to investigate the service account resources and help release the domain names so you can complete your association. Depending on your AWS Support plan, you may receive faster response times with higher-tier plans.
I cannot directly disable or delete resources in AWS service accounts, but AWS Support will be able to assist you with resolving this orphaned distribution issue.
Relevant content
asked 5 years ago
- AWS OFFICIALUpdated 9 months ago
