- Newest
- Most votes
- Most comments
Based on your detailed description, there are several issues preventing your custom domain setup in AWS Amplify from working properly. Let me address the key problems:
-
Missing IAM Role: The error regarding the missing "AWSAmplifyDomainRole-Z08355081XP7MM1S4KU0J" role is critical. This service-linked role is required for Amplify to properly manage custom domains and create CloudFront distributions. Without this role, Amplify cannot complete the domain setup process.
-
CloudFront Distribution Issues: The fact that you have DNS records pointing to CloudFront distributions that don't exist indicates a failure in the Amplify domain association process. Normally, Amplify should create these CloudFront distributions automatically when setting up a custom domain.
-
DNS Configuration: While your Route 53 records appear to be configured, they're pointing to resources that don't exist, which explains why your domains aren't accessible.
Here are some troubleshooting steps you can try:
-
Delete the current custom domain configuration from your Amplify app completely.
-
Check if there are any verification issues with your domain. Make sure your contact information for the domain is verified. AWS sends verification emails that sometimes go to spam folders.
-
Check for any conflicting records or associations. Your domain might still be associated with another Amplify app or CloudFront distribution, even if you can't see it in your account. This can happen if the domain was previously used with Amplify.
-
When re-adding the domain, try adding both the root domain (talesmio.com) and the www subdomain (www.talesmio.com) to ensure proper configuration.
-
After adding the domain, wait for DNS propagation which can take up to 48 hours, though it's usually much faster.
If these steps don't resolve the issue, you'll likely need to contact AWS Support as you suggested. They can:
- Create the missing IAM role or investigate why it's not being created automatically
- Check for any "ghost" associations with your domain name in the AWS system
- Help clean up any orphaned DNS records
- Assist with properly configuring the CloudFront distribution
The missing IAM role is particularly concerning and likely requires AWS Support intervention, as this is a system-generated role that should be created automatically during the domain setup process.
Sources
Adding amplify custom domain hosted in route53 | AWS re:Post
Issues adding a custom domain to my Amplify application | AWS re:Post
Amplify custom domain setup issue | AWS re:Post
One or more domains requested are already associated with another Amplify | AWS re:Post
answered a year ago
Relevant content
- AWS OFFICIALUpdated a year ago

Tried the solutions mentioned there nothing working