By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Custom domain for Amplify not working

0

Hello,

I used Amplify option from S3 static site bucket to expose online the site content. The deploy was successful and the application appeared in Amplify console, and could be accessible from web browser using Amplify URL.
When I tried to build a custom domain for the Amplify application, I chose an existing domain, a subdomain and an existing certificate for the main domain (). I was able to press Add domain. In the next page, SSL configuration was successful, but the circle with Domain activation is circling around and nothing happened/ended. There is no error returned. Enter image description here
After these, I tried to restart Add domain procedure and I've got the error below, even if the Domain activation was not finished Enter image description here
Could you please specify what happened, and how should I use with this kind of Amplify application an existing domain and certificate ?

Thank you,
Mihai ADAM

Topics
Front-End Web & MobileNetworking & Content Delivery
Tags
AWS AmplifyAmazon Route 53
Language
English
rePost-User-4717319
asked a month ago64 views
1 Answer
0
Accepted Answer

I understand you're having issues setting up a custom domain for your Amplify application that was created from an S3 static site bucket. Let me provide some insights and suggestions to help resolve this issue.

  1. Domain Activation Process: The domain activation process can sometimes take a while, especially if there are DNS propagation delays. It's normal for the circle to keep spinning for some time. However, if it persists for an extended period (more than an hour), there might be an underlying issue.

  2. Existing Certificate: When using an existing certificate, ensure that it covers both the main domain and the subdomain you're trying to add. If the certificate doesn't include the subdomain, you may encounter issues.

  3. DNS Configuration: Make sure you've properly configured your DNS settings to point to the Amplify app. Amplify will provide you with CNAME records that need to be added to your DNS configuration.

  4. Error on Retry: The error you're seeing when trying to restart the Add domain procedure suggests that the domain is already associated with the app. This is likely because the initial attempt is still in progress or partially completed.

To resolve this and use your existing domain and certificate with the Amplify application:

  1. Wait for some time (about an hour) to see if the domain activation completes on its own.

  2. If it doesn't complete, try removing the domain from the Amplify app entirely and then re-adding it.

  3. Double-check that your existing certificate covers the subdomain you're trying to use.

  4. Ensure your DNS settings are correctly configured according to Amplify's instructions.

  5. If problems persist, you may need to create a new certificate specifically for this subdomain through AWS Certificate Manager.

  6. As a last resort, you could try creating a new Amplify app and migrating your content to it, then setting up the custom domain on the new app.

If none of these steps resolve the issue, it would be advisable to contact AWS Support for further assistance, as they can look into the specifics of your account and application setup.
Sources
Simplify and enhance Amazon S3 static website hosting with AWS Amplify Hosting | AWS News Blog
Deploying a static website to AWS Amplify Hosting from an S3 general purpose bucket - Amazon Simple Storage Service
Wildcard Subdomains for Multi-tenant Apps on AWS Amplify Hosting | Front-End Web & Mobile

profile picture
re:Post Agent
answered a month ago
profile picture
EXPERT
Adeleke Adebowale J
reviewed a month ago
  • rePost-User-4717319
    a month ago

    Thank you for your answer,
    I had some of the issues described above:

    • the existing certificate did not include the domain and subdomain
    • Amplify did not provide with CNAME records until this stage in configuration (Maybe not needed, my DNS is inside AWS: Route53)
    • regarding the Error On Retry, the Domain activation did not finished after one hour
    • the same CNAME was associated with other CloudFront distribution

    I deleted the domain. I created a new one with Amplify managed certificate that works.

  • Adeleke Adebowale J EXPERT
    a month ago

    Ensure that the certificate used covers all domain variations needed. For AWS-hosted DNS (Route 53), additional CNAMEs may not be required as Amplify often auto-configures DNS settings. If an error occurs with domain re-association, check for conflicts with existing CloudFront distributions or other AWS services. In some cases, using Amplify’s built-in certificate service can simplify the setup.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content