AWS Amplify app deployed URL is no longer valid

This issue with your AWS Amplify app's custom domain (neighborly-way.com) not being accessible could be caused by several factors:

1. SSL Certificate Expiration: If you're using a certificate managed by Amplify, it may have expired. Amplify certificates are valid for 13 months and should renew automatically, but this process can fail if the CNAME verification records in your DNS settings have been modified or deleted.

2. DNS Configuration Issues: The CNAME records required for your custom domain may have been changed, removed, or not properly propagated. This is especially common if you're using a third-party DNS provider like Cloudflare.

3. Domain Association Problems: There might be a lingering association between your domain and a previous CloudFront distribution, even though your app is now connected to a new distribution.

To resolve this issue:

1. Check your DNS configuration by going to Hosting > Custom Domains > Actions > View DNS records in the Amplify console. Verify that these CNAME records still exist and are correctly configured in your domain provider's DNS settings.

2. If the records are missing or incorrect, you may need to delete the custom domain in Amplify and re-add it, which will generate new CNAME records to add to your DNS provider.

3. Ensure that if you're using Cloudflare, the proxy status for your CNAME records is set to "DNS only" (not proxied), as Cloudflare's proxy can interfere with AWS's domain validation.

4. Check for any caching issues by trying to invalidate the cache in the Amplify console.

5. Verify that your domain and SSL configurations are correct in the Amplify console.

If these steps don't resolve the issue, you might need to wait 24-48 hours for DNS changes to fully propagate globally.
Sources
CNAME problem deploying a custom domain in Amplify | AWS re:Post
Issue with AWS Amplify Deployment on Custom Domain | AWS re:Post
SSL certificate is expired (Certificate managed by Amplify) | AWS re:Post

1. Check if your app is still working via default Amplify domain Visit: https://d18ar8o5oncuia.amplifyapp.com If that loads , your React app is healthy.

2. Reconnect your custom domain (neighborly-way.com) Go to:

• --> Amplify Console → neighborlyway app → Domain Management
• --> If the domain is missing → click "Add Domain"
• --> Enter neighborly-way.com
• --> Follow the wizard

It will show DNS records you need to configure (CNAME or A-records)

3. Fix DNS Records Go to your domain registrar (e.g., GoDaddy, Google Domains, etc.) Update DNS:

• --> Add a CNAME for www.neighborly-way.com → your Amplify domain (d18ar8o5oncuia.amplifyapp.com)
• --> (Optional) Set up root domain (neighborly-way.com) using a redirect or A/ALIAS record to Amplify

If you’re using Route 53, Amplify can do this automatically

4. Check ACM Certificate (HTTPS) Go to: AWS ACM Console

• --> Look for certificate for neighborly-way.com
• --> If it's expired or pending validation, delete and reissue via Amplify's domain wizard

5. Wait for DNS to propagate

• It can take 5–30 minutes (sometimes up to 1 hour)
• Use: https://dnschecker.org to confirm your records are live.

After the above: Your custom domain will point back to Amplify SSL will be revalidated The React app will be accessible at https://neighborly-way.com again