Skip to content

App Runner not adding custom domain names to ACM certificate

1

We recently deployed a new App Runner service and added two custom domain names and setup the DNS records as required. Both domain names are now showing Status: Active.

When accessing the application using the App Runner provided URL everything works but when accessing via a custom domain we get a ERR_CERT_COMMON_NAME_INVALID error as the served certificate is only valid for *.<region>.awsapprunner.com.

Is there something we might be missing? It seems like a bug and that the AWS managed ELB is not adding the certificates to it's listeners or adding the additional CNs to the certificate.

1 Answer
0
Accepted Answer

The issue was resolved by recreating the certificates a few times. Most likely a bug in the backend services.

answered 3 years ago

EXPERT

reviewed 2 years ago

  • Buggy stuff!! Frustrated here too.

  • Just want to update that I ran into this issue a full two years later. Deployed an app runner service with custom domain and public endpoint and things worked fine. Updated the service to a private endpoint and the cert name was invalid. Switched it back to public domain and the invalid cert remains.

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.