Are these certificates seen as self-signed? Is the Root CA signed by AWS or a trusted 3rd party? I am trying to resolve an issue with EC2 servers in my environment that came up in a penetration scan as using self-signed certificates. I’m also using AWS’ Directory Services which I found has direct integration with AWS Private CA but I need to know if this would actually solve my problem or if the penetration/vulnerability scan would still see these certificates as “invalid” self-signed certificates.
Hello, apologies for the delayed response. You can find more specifics about ACM Private CA's on our FAQ's page. The question, "What are self-signed certificates and why should organizations use certificates from a private CA instead?" will point you in the right direction for your use case: go.aws/4aZTYIa. For any follow-up insight, I'd recommend reaching out in our community over on re:Post as a great technical resource: go.aws/aws-repost. 📚 ^AD
@@awssupport No worries. Thanks for responding here at all! I have, in fact, read through the documentation and have posted on AWS re:post as well. Thanks again.
![[UNCUT] เก็บ "สจ.โต้ง" เอี่ยวมาเฟีย รู้ตัวคนบงการ ก่อนสั่งลั่นไก I คนดังนั่งเคลียร์ I 13 ธ.ค.67](http://i.ytimg.com/vi/o-J_p62D40w/mqdefault.jpg)
Are these certificates seen as self-signed? Is the Root CA signed by AWS or a trusted 3rd party? I am trying to resolve an issue with EC2 servers in my environment that came up in a penetration scan as using self-signed certificates. I’m also using AWS’ Directory Services which I found has direct integration with AWS Private CA but I need to know if this would actually solve my problem or if the penetration/vulnerability scan would still see these certificates as “invalid” self-signed certificates.
Hello, apologies for the delayed response. You can find more specifics about ACM Private CA's on our FAQ's page. The question, "What are self-signed certificates and why should organizations use certificates from a private CA instead?" will point you in the right direction for your use case: go.aws/4aZTYIa. For any follow-up insight, I'd recommend reaching out in our community over on re:Post as a great technical resource: go.aws/aws-repost. 📚 ^AD
@@awssupport No worries. Thanks for responding here at all! I have, in fact, read through the documentation and have posted on AWS re:post as well. Thanks again.
😃 Glad to hear it, you're very welcome. ^AD