- Newest
- Most votes
- Most comments
It is hard to comment on your specific issue, as there are many miss-configurations for a certificate not being trusted, in addition to it being signed by a certificate that is not trusted.
Without knowing, or having access to your endpoint with this certificate installed, I can suggest you look at the following:
When you import the certificate to ACM, ensure that you have all the certificates in the chain as well. In particular pay careful attention to this document https://docs.aws.amazon.com/acm/latest/userguide/import-certificate-format.html
A missing intermediate will result in this type of error.
Lastly, can I suggest that you have a look at potentially using a free ACM certificate with CLoudFront, you can configure validation to a DNS record in your CloudFlare DNS. Refer to https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-request-public.html. This is free for AWS services that are supported by ACM, and has the benefit that it supports automatic renewal and such, removing overhead from the use of the certificate.
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
Thank you for your quick and accurate response! CloudFront accepted the certificate after I reimported the certificate and added the missing intermediate certificate during the import.