AWS Amplify domain "already associated with another app" but no associations exist in any region

Hello.

This error can occur not only with Amplify but also when linked to CloudFront.
If you have previously created a CloudFront instance using that domain, you should also check CloudFront.
If it's not found in CloudFront either, all you can do is wait for a response from AWS support.
https://repost.aws/questions/QUFshgZBsORg2MPNBrNG8msg/unable-to-associate-domain-gifted-project-net-with-amplify-cname-already-in-use#ANPz6aot9fTPOASo6jlaXm6w

This is a known issue where domain associations can persist in AWS Amplify's backend even after an app has been deleted, making the domain appear "locked" to a non-existent app. Since you've already verified that no domain associations exist through the CLI and console across all regions, and AWS Support hasn't responded yet, here are some additional steps you can try:

1. Double-check domain associations using the CLI: Run aws amplify list-domain-associations --app-id dwld0pzka7qul --region eu-west-2 to confirm no associations exist for your current app.

2. Check for any pending domain operations: Sometimes domains can be stuck in a transitional state. Look for any pending operations in the Amplify console.

3. Verify domain ownership in Route 53: Ensure the domain is properly configured in Route 53 and there are no conflicting DNS records.

4. Try a different subdomain first: As a temporary workaround, try associating a different subdomain (like app.benjaminkitson.com) to see if the issue is specific to the root and www domains.

Since this appears to be a backend data inconsistency that requires AWS intervention, I recommend:

• Escalating your support case: If you have a support plan, request escalation of your existing case
• Opening a new support case: Reference your app ID, region, domain, and account ID (which you've already provided)
• Using the AWS re:Post community: Post your issue there as AWS support engineers monitor that forum

Unfortunately, this type of backend cleanup typically requires AWS support team intervention to manually remove the stale domain association from their systems. There's no customer-facing API or console action that can resolve this particular issue.