- Newest
- Most votes
- Most comments
The issue you're experiencing with Amplify custom domain activation is indeed frustrating and not uncommon. It appears that there's a persistent reference to a deleted IAM role that's preventing the domain activation process from completing successfully.
Here are some additional steps you can try to resolve this issue:
-
IAM Role Cleanup: Although you've already deleted the old role, there might be lingering references in other parts of your AWS account. Double-check your IAM roles and policies to ensure there are no remaining references to the deleted role.
-
Amplify App Rebuild: Try deleting your entire Amplify app and recreating it from scratch. This can sometimes clear out cached or stuck configurations that might be causing the issue.
-
CloudFront Distribution Check: Verify if there are any lingering CloudFront distributions associated with your domain. Amplify creates these automatically, and sometimes they can persist even after deleting an app.
-
AWS CLI Intervention: Use the AWS CLI to list and describe the Amplify app and its associated resources. This might reveal hidden configurations that are not visible in the console.
-
Support Ticket: If none of the above steps work, it's advisable to open a support ticket with AWS. They have access to backend systems and can manually clear stuck configurations that aren't accessible through the console.
-
Temporary Subdomain: As a workaround, you could try using a different subdomain temporarily (e.g., new.24kode.com) to see if the issue is specific to the root domain configuration.
-
ACM Certificate Check: Ensure that there are no old or conflicting SSL certificates in AWS Certificate Manager for your domain.
Remember, each custom domain must be unique across all CloudFront distributions globally, not just within your account. This global uniqueness requirement can sometimes lead to conflicts that are not immediately apparent.
If the problem persists after trying these steps, engaging with AWS Support might be your best option to get the domain fully cleared and ready for use with your Amplify app. They can investigate any hidden associations or configurations that might be causing this persistent reference to the old IAM role.
Sources
Can't Activate AWS Amplify Custom Domain | AWS re:Post
Amplify custom domain setup issue | AWS re:Post
Relevant content
- asked 4 years ago
- asked a year ago
- asked 6 months ago
- asked a year ago