Configure AWS Connection
Table of Contents
Expand all | Collapse all
-
- Activate Next-Generation Trust Security
-
-
- Configure Akamai Connection
- Configure AWS Connection
- Configure Azure Key Vault Connection
-
- Workload Identity Federation Authentication
- Workload Identity Federation - Azure Identity Provider Authentication
- Next-Gen Trust Security Generated Key Authentication
- User Permissions
- Workload Identity Federation Authentication
- Next-Gen Trust Security Generated Key Authentication
- User Permissions
- Supported OIDC Claims
-
-
-
- Working with the Built-in CA
- Add AWS Public CA
- Add AWS Private CA
- Add DigiCert One Certificate Authority
- Add Entrust
- Add GlobalSign Atlas
- Add GlobalSign MSSL
- Add GoDaddy
- Add Google Cloud Private CA
- Add a HID PKIaaS CA
- Add Certificate Manager - Self-Hosted
- Set Up an OpenSSL Certificate Authority Connector
- Create a Sectigo Certificate Manager Certificate Authority
- Add Zero Touch PKI
- Set Up Certificate Expiration Notifications
- Using a Custom DNS Provider
-
-
-
-
- Create an F5 BIG-IP LTM Machine
- Create a Microsoft Azure Private Key Vault Machine
- Create a Microsoft Azure Application Registration Machine
- Create a Microsoft IIS Machine
- Create a Microsoft Windows (PowerShell) Machine
- Create a Microsoft SQL Server Machine
- Create a Common KeyStore Machine
- Create a Citrix ADC Machine
- Create an Imperva WAF Machine
- Create a VMware NSX Advanced Load Balancer (AVI) Machine
- Create an A10 Thunder ADC Machine
- Create a Cloudflare Machine
- Create Kemp Virtual LoadMaster Machine
- Create a Palo Alto Panorama Machine
- Create a Radware Alteon Machine
-
- Provision to an F5 BIG-IP LTM
- Provision to a Microsoft Azure Private Key Vault
- Provision to Microsoft IIS
- Provision to Microsoft Windows (PowerShell)
- Provision to Microsoft SQL Server
- Provision to a Common KeyStore
- Provision to a Citrix ADC
- Provision to an Imperva WAF
- Provision to VMware NSX Advanced Load Balancer (AVI)
- Provision to an A10 Thunder ADC
- Provision to Cloudflare
- Provision to a Kemp Virtual LoadMaster
- Provision to Palo Alto Panorama
- Provision Certificates to Radware Alteon
-
-
- 47-Day Validity Readiness TLS Certificates dashboard
- About the Certificate Inventory
- Managing Certificate Lifecycle Settings
- Reissuing Certificates in Next-Gen Trust Security
- Downloading Certificates, Certificate Chains, and Keystores
- Retiring, Recovering, and Deleting Certificates
- Finding Certificates in the Certificate Inventory
- Importing Certificates from a CA Using EJBCA
- Domain-Based Validation for External Emails
-
- Create a Workload Identity Management or Discovery Agent Built-in Account
- Create an OCI Registry Built-in Account
- Create a Certificate Manager - Self-Hosted Built-in Account
- Create a Scanafi Built-in Account
- Toggling a Built-in Account on or Off
- Editing Built-in Accounts
- Deleting Existing Built-in Accounts
- Renew Existing Built-in Accounts
- Troubleshooting
Configure AWS Connection
The following guide illustrates connecting Next-Gen Trust Security with Amazon Web Services (AWS).
Enable Next-Gen Trust Security to provision new certificates in AWS Certificate Manager (ACM) for use with AWS services. This guide walks you through the integration process.
Before You Begin
You're going to need a few things to complete this procedure.
- You will need an AWS account.
- Your AWS account ID.
- You will need at least one active VSatellite to provision certificates to AWS.
- Venafi permissions for AWS IAM. You must specify these permissions when defining the role's permission policy. This policy defines what actions Venafi takes and what resources they can access. You can find this policy in the JSON file provided below.
Note:
- Review the supported AWS ACM cryptographic algorithms.
- Only Next-Gen Trust Security-generated and user-imported certificates with private keys can be provisioned. To learn more see Importing a private key via API (PKCS #8) and Importing a private key via API (PKCS #12).
- Only one certificate can be provisioned at a time.
- Only regions that are enabled on Amazon will be available for provisioning.
Overview
The following diagram illustrates the high-level steps for integrating Next-Gen Trust Security with AWS. In the subsequent sections, we dive into each of these steps, providing you with a guided walkthrough.
Step 1: Create a Cloud Provider
- Sign in to Next-Gen Trust Security.
- Click Configuration > Certificate Integrations > Cloud Providers.
- Click New.
- Enter a Name for the new cloud provider. This name will help Next-Gen Trust Security users to identify this cloud provider.
- Click Continue.
- Enter your 12 digit AWS Account ID obtained from AWS.
- Enter the IAM Role you want to create in your AWS Account. Provide a role name that carries significance and can be readily linked to this specific cloud provider. For this example we will use TlspcIntegrationRole.
- Click Save. At this point, your new provider details will be displayed in the right pane.
- From the right pane, select Properties, copy, and save the External ID for use later on. To learn more about the use of the External ID, check out the IAM User Guide.
Important: Make sure to copy and save this External ID for use later on. You will need this External ID in Step 3: Create an AWS IAM role for Next-Gen Trust Security.
Step 2: Create an AWS IAM Policy for Next-Gen Trust Security
In this step, we will set up an IAM policy for your AWS Next-Gen Trust Security role, granting it the required permissions for full access to all AWS integrations provided by Next-Gen Trust Security.
- Create a new policy in the AWS IAM Console.
- Select the JSON tab, and then paste the Next-Gen Trust Security permission policies into the provided textbox.
- Click Next: Tags, then Next: Review.
- Assign a name to the policy, such as TlspcIntegrationPolicy, and provide a suitable description.
- Click Create policy.
Step 3: Create an AWS IAM Role for Next-Gen Trust Security
- Create a new role in the AWS IAM Console.
- Select AWS account as the trusted entity type, and then select Another AWS account.
- Enter 569433869543 as the Account ID.
- Select Require external ID and enter the External ID copied in Step 1. Keep Require MFA disabled.
- Click Next.
Tip: For additional information, see How to use an external ID.
- Select the policy you created in the previous step, and then click Next.
- Assign the role a name and provide a suitable description.
Important: Make sure this role name is the SAME role name as the one you assigned in Step 1 when creating a cloud provider in Next-Gen Trust Security.
- Click Create Role.
Step 4: Validate the Connection
- Click Configuration > Certificate Integrations > Cloud Providers.
- Find and select the new cloud provider created in Step 1, then click Validate.
Note: You can also validate the connection by selecting the provider, clicking the more options (ellipsis) button, and selecting Validate.
Note: A yellow warning icon indicates the provider has not yet been validated. This icon disappears after successful validation.
Note: If you configure an AWS Organization account, the Organization ID appears in the Access Details section under Properties.
If the warning icon remains, review the configuration steps above.
Step 5: Add a Cloud Keystore
- Sign in to Next-Gen Trust Security.
- Click Insights > Cloud Keystores.
- Click New and select AWS.
- Enter a Name for the new cloud keystore.
- Select an AWS Cloud Provider.
- (Optional) If you configured an AWS Organization account with the selected cloud provider, select an AWS Organization Account.
- Select an ACM Region.
- (Optional) To discover certificates on your keystore, enable Start discovery immediately and Include expired certificates. Once complete, create a schedule.
- Click Save. The new cloud keystore appears in the Cloud Keystore list.
Step 6: Provision a Certificate
- Click the More actions (ellipsis) icon next to the cloud keystore you created, and then select Provision.Tip: From this menu, you can also delete certificates if needed.
- From the dropdown, search for the certificate you want to provision, select it, and then click Provision. This creates a new certificate installation on the cloud keystore.
- (Optional) You can also re-provision, replace, or delete an existing certificate.
- Select your Cloud Keystore to open the details panel.
- Click the More actions (ellipsis) icon next to the certificate.
- Select Re-provision, Replace, or Delete, and complete the steps in the user interface.
Info:- Re-provision re-installs the current certificate on the cloud keystore.
- Replace substitutes the current certificate with a different one.
- Delete removes the certificate from the cloud keystore.
Set up AWS Discovery Schedule
- In the Next-Gen Trust Security toolbar, click Installations > Cloud Keystores.
- Select the Cloud Keystore.
- In the right pane, select Discovery configuration and enable Scheduled discovery and Include expired certificates.
- Configure the schedule.
- Click Save.
AWS IAM Permissions
Authentication to AWS Resource Via IAM Role
With IAM roles, you can grant access to Next-Gen Trust Security for your AWS resources without sharing your AWS security credentials. Instead, Next-Gen Trust Security can access your AWS resources by assuming a role that you create in your AWS account. You can use an IAM role to establish a trusted connection between your AWS account and Next-Gen Trust Security. Once this connection is established, you will define the role's permission policy, determining what actions Next-Gen Trust Security takes and what resources they can access.
To correctly set up the AWS Integration, you must attach the relevant IAM policies in the following JSON file to the Next-Gen Trust Security AWS Integration IAM Role in your AWS account.
{ "Version":"2012-10-17", "Statement":[ { "Effect":"Allow", "Action":[ "acm:GetCertificate", "acm:DeleteCertificate", "acm:ImportCertificate", "acm:ListCertificates", "acm:AddTagsToCertificate", "ec2:DescribeRegions" ], "Resource":"*" } ] }
Additional IAM Permissions for Organization Management Accounts
Next-Gen Trust Security supports integration with AWS Organization Management accounts. If you plan to use an AWS Organization Management account, additional IAM permissions are required.
To allow Next-Gen Trust Security to discover and manage certificates across multiple accounts in your AWS Organization, attach the following additional policy in the following JSON file to the AWS Organization IAM Role used in the Cloud Provider configuration (Management account):
{ "Version": "2012-10-17", "Statement": [ { "Sid": "AWSOrganizationPermissions", "Effect": "Allow", "Action": [ "organizations:ListRoots", "organizations:ListChildren", "organizations:ListAccountsForParent", "organizations:ListAccounts", "organizations:DescribeOrganization", "organizations:DescribeOrganizationalUnit", "organizations:ListParents", "organizations:ListOrganizationalUnitsForParent" ], "Resource": "*" } ] }
These permissions allow Next-Gen Trust Security to detect AWS Organization Account structure and fetch associated member accounts when configuring Cloud Keystores.
Important: If the Management Account also performs ACM operations, append the standard ACM permissions to this policy.