You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BUSINESS PROBLEM
Customer is currently using Digicert for all external certificates, with plans to support public ACM. Amazon Private CA is not being used. Customer needs the ability to have visibility and control across all certificates in AWS.
PROPOSED SOLUTION
Extend the lambda function to support Digicert and ACM, with the flexibility to support additional Certificate Authorities. Support should include enrollment and renewal functionality.
CURRENT ALTERNATIVES
Customer has written their own limited Lambda function to support certificate enrollment from ACM.
VENAFI EXPERIENCE
Customer has been using Venafi for 3 years and are a very active user.
The text was updated successfully, but these errors were encountered:
Support for ACM and IAM is already present in the form of CA template objects. This lambda function is specifically for AWS Private CA.
The figure below may help illustrate ACM and IAM provisioning. Policies defined in Venafi will be enforced for these requests. By the same token, existing certificates in AWS key stores can be 'discovered' as well.
(1) Request for new certificate or a renewal
(5) TPP generates a Private Key, creates a CSR and sends the CSR to Certificate Authority such as DigiCert or another public/private CA. Private Key stored in encrypted database (99)
(6) Signed certificate sent to TPP server and stored in encrypted database (99)
(7) Signed certificate and Private Key provisioned into key store in AWS IAM or ACM by TPP
(8) Certificate unique identifier in AWS (ARN) is sent to TPP
(1) Applicant can optionally read the ‘stage’ provisioning is currently at and/or retrieve values generated by AWS or Azure for this certificate
(4) Certificate details (including ARN) are returned to requesting application when they are available
Venafi's access to key stores in AWS can leverage cross account Asume-Role features in AWS. For e.g. the account doing the provisioning into AWS based key stores temporarily assumes a pre-defined role with minimal required access to perform the provisioning task into the target AWS account.
The possibility of enhancing the Lambda function to alternatively request certificates through Venafi Cloud or TPP would be in alignment with most of our other DevOps solutions but it is not in our near term plans.
BUSINESS PROBLEM
Customer is currently using Digicert for all external certificates, with plans to support public ACM. Amazon Private CA is not being used. Customer needs the ability to have visibility and control across all certificates in AWS.
PROPOSED SOLUTION
Extend the lambda function to support Digicert and ACM, with the flexibility to support additional Certificate Authorities. Support should include enrollment and renewal functionality.
CURRENT ALTERNATIVES
Customer has written their own limited Lambda function to support certificate enrollment from ACM.
VENAFI EXPERIENCE
Customer has been using Venafi for 3 years and are a very active user.
The text was updated successfully, but these errors were encountered: