- Newest
- Most votes
- Most comments
That sounds like a problem with the certificate that you imported into ACM from somewhere outside ACM. To obtain a publicly trusted certificate at no cost, you should use ACM to issue a certificate for you, rather than importing an externally issued or self-signed one into ACM: https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-request-public.html
@christian Let's Encrypt is one external certificate issuer for which you need to request and manage the certificates, their renewal, etc. yourself.
ACM is another, Amazon-owned certificate issuer. Certificates issued by ACM are publicly trusted and work with all browsers. They are also free to use. If you use DNS validation, they are also renewed automatically, avoiding the need to manage anything manually after initially establishing the DNS validation and creating the certificate.
I suggest you create a new issued by ACM and use DNS validation for it. You won't need the Let's Encrypt -issued certificate (which has nothing to do with ACM other than that you imported the Let's Encrypt certificate there) after that, and the ACM-issued certificate will work with all browsers.
Relevant content
- Accepted Answerasked 9 days ago
- Accepted Answerasked a year ago
AWS OFFICIALUpdated 2 months ago- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 3 months ago
I imported certificate from another AWS account that handles the domain registration and then "request certificate" using DNS validation on the current AWS account, the issue still exists. when I'm using letsencrypt SSL, it has no issue.
hello @christian, do you mean the certification is from another AWS and it's a AWS-issued public cert? But the AWS-issued public cert cannot be exported. Would you mind clarify what kind of certification is it? Thanks.