aws-amplify / aws-amplify/amplify-hosting

SSL certificate expired on web after auto-renewed in ACM

Open
#2,579 10 comments 0 reactions 0 assignees View on GitHub
bug custom-domain
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked the [custom domains troubleshooting guide](https://docs.aws.amazon.com/amplify/latest/userguide/custom-domain-troubleshoot-guide.html).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-console/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

arn:aws:amplify:ap-southeast-2:809899173738:apps/daloz45pagf6l

### Region

ap-southeast-2

### Step

Live site

### Status

SSL certificate invalid, despite ACM already renewing it

### Issue or question

I have an Amplify custom domain set up for [mattryall.net](https://mattryall.net), and the wildcard SSL cert hosted by Amazon Certificate Manager (ACM) is not being correctly served by Amplify, after it was renewed automatically.

According to the ACM config, the certificate was automatically renewed on 16 December 2021 (see screenshot below). The CNAME records for auto-renewal are still in place on Route53 and have not been modified.

I haven't deployed a new version of the site or changed any configuration since mid-2021.

It looks like the ELBs or Amplify itself are still serving the old certificate, even after it was renewed. I tried digging into the ELB config, but I can't actually see the ELBs referenced from the certificate resources in the EC2 console (see screenshot below for the ARNs). They must be some kind of secret squirrel Amplify ELBs that don't show up in the console.

My hunch is that there's a missing or flaky eventing system between ACM renewing the certificate and the ELBs or Amplify updating the certificate files they serve.

I have not tried to redeploy the site, which I think may fix the issue, because I wanted to leave the setup for problem diagnosis first.

acm-certificate-details

acm-certificate-resources

route53-dns-config

### Error message

> "*.mattryall.net" certificate is expired.

mattryall-certificate-expired

### Additional information

A prompt response would be appreciated, as I'm leaving my site down and unchanged until you can investigate and confirm the problem.

Thanks,
Matt

Contributor guide

Open the contributing guide

Research direction

Start with the custom domains troubleshooting guide, then inspect the ACM renewal details, Route53 renewal CNAME records, Amplify custom-domain configuration, and the certificate served by the live site. The issue is resolved when the renewed ACM certificate is served for mattryall.net without requiring a redeploy and the expired-certificate error disappears.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.