Secrets Manager

This AWS integration allows you to configure CloudTruth External Parameters from your AWS Secrets Manager.
Adding Integrations
If you already have a CloudTruth AWS integration you can add AWS Secrets Manager by editing the existing account, selecting this integration and adding the Secrets Manager Inline Policy. The Terraform and CloudFormation role setup methods automatically create the Secrets Manager inline policy.
To create a new or additional AWS account click Add AWS Account from the Integrations AWS page to bring up the add account pane. Add a name for the AWS account, your specific AWS account ID and the AWS account role name.‌ CloudTruth allows you to select regions where your resources exist, all US regions are enabled by default.
The Secrets Manager integration supports CloudTruth push actions. To enable Push Actions select Write Access for the integration and apply the write access inline policy for Secrets Manager.
Check the AWS Secret Manager integration and click Save.​‌
The AWS account will enter an Integration Error state until the AWS role is configured. An auto generated External Id will be created to use in the AWS Role Creation.
Configuring the AWS Role
With the provided External ID create your AWS Role.
Setting up an AWS Role
AWS Secret Store Inline Policy
‌Adding an Inline Policy to the AWS Role allows CloudTruth secure access to the selected integration service. The inline policy is automatically created if you used CloudFormation or Terraform to create the role.
From the AWS IAM Console select the role that you created for CloudTruth access.
Click Add Inline Policy.​
Click the JSON Tab.​‌
Paste in the following JSON for the AWS Secret Store integration policy and click Review Policy.
External Parameter Policy
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "ListSecrets",
            "Effect": "Allow",
            "Action": "secretsmanager:ListSecrets",
            "Resource": "*"
        },
        {
            "Sid": "SecretAccess",
            "Effect": "Allow",
            "Action": [
                "secretsmanager:GetSecretValue",
                "secretsmanager:DescribeSecret"
            ],
            "Resource": "*"
        }
    ]
}
Write Access Parameter Policy for Push actions​
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "ListSecrets",
            "Effect": "Allow",
            "Action": "secretsmanager:ListSecrets",
            "Resource": "*"
        },
        {
            "Sid": "SecretAccess",
            "Effect": "Allow",
            "Action": [
                "secretsmanager:CreateSecret",
                "secretsmanager:DeleteSecret",
                "secretsmanager:GetSecretValue",
                "secretsmanager:DescribeSecret",
                "secretsmanager:TagResource",
                "secretsmanager:UpdateSecret"
            ],
            "Resource": "*"
        }
    ]
}
Type in a name for the policy and click Create Policy.​‌​
​👏
Setup is now complete for both the AWS Role and Policy. After refreshing by clicking "Check Integration Status" the CloudTruth integration will now show as "Connected", and you can begin creating External Parameter values that reference your AWS resources.

Azure Key Vault

Last modified 8mo ago

Secrets Manager

Adding Integrations

Configuring the AWS Role

AWS Secret Store Inline Policy

External Parameter Policy

Write Access Parameter Policy for Push actions​

Write Access Parameter Policy for Push actions