SSL/TLS certificate verification flow
Issue when dealing with certificate verification in Cloudfront

  Nov 27, 2020 -   read
  software, http, ssl, tls, cloudfront

Recently, I set up a simple RESTful APIs service. To enhance the speed of distribution and provide a better load balance for my micro-service, I put it behind Route53 and Cloudfront. But when I tested using PostMan, I was caught off-guard by a simple error.

Error: Hostname/IP does not match certificate's altnames: Host: is not in the cert's altnames:, DNS:*

Simple & straightforward RESTful APIs service setup


Like every other debugging session, we start with the error message. It’s very descriptive and helpful, mentioned cert alternate names. So how does SSL/TLS cert look like? and how does cert name verification work?

SSL/TLS certificate

HTTPS (via SSL/TLS) uses public key encryption to protect client’s communication with servers (clients can be a web browser or API clients like PostMan). Clients prevent Man-in-the-middle attacks by authenticating HTTPS servers using X.509 certificates, which are digital documents that bind a public key to an individual subject/organization.

In this scenario, I put my app behind AWS infra and by using Cloudfront + Certificate Manager, so I have those certificates for free to protect my service and it will be issued by Amazon Root Certificate 1

Basic SSL/TLS certification chain

The binding is asserted by having a trusted Certification Authority (CA) installed on clients end (e.g. web browser Trusted Root Certification Authorities, Java trust stores for API clients…). And it’s clients’ responsibility to verify those server’s X.509 certificates.

Certification Path Validation

Basically, clients will iterate through all certificates in the path starting with the trust anchor (i.e. the root certificate), validating each certificate’s basic information and critical extensions.

SSL/TLS verification flow

So the certificates are limited to a specific domain or domain tree (i.e. including sub-domains) for a company or an organization, like,, etc. Name constraints are often used for intermediate CA certificates purchased from a publicly trusted CA to prevent the intermediate CA from issuing perfectly valid certificates for third-party domains (e.g.


After examination, it failed step 5 where the existing Alternate Domain Names (CNAMEs) list in Cloudfront doesn’t contain the intended API service sub-domain The solution is simple, just add this sub-domain to the existing list and the error is no longer there.

Error no longer there


Dang Chien
Software engineer, solution architect and Agile practitioner.
Do you find this article helpful ❤️ ? Support me with a coffee via, give me a shout out on Twitter at @dangchien87, or help to share this article instead.