.png%3Falt%3Dmedia%26token%3Df1ea80d6-51a3-4edb-bfba-3349a6b8cf8f)
.png%3Falt%3Dmedia%26token%3Df1ea80d6-51a3-4edb-bfba-3349a6b8cf8f)
🏢Organization management
🛠️Config Management
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.%20(1).png?alt=media)
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.
.jpg?alt=media)
Configuring the AWS Role
With the provided External ID create your 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.
.jpg?alt=media)
Click
Add Inline Policy.%20(2)%20(1).png?alt=media)
Click the
JSON Tab.
Paste in the following JSON for the AWS Secret Store integration policy and click
Review Policy.External Parameter Policy
1
{
2
"Version": "2012-10-17",
3
"Statement": [
4
{
5
"Sid": "ListSecrets",
6
"Effect": "Allow",
7
"Action": "secretsmanager:ListSecrets",
8
"Resource": "*"
9
},
10
{
11
"Sid": "SecretAccess",
12
"Effect": "Allow",
13
"Action": [
14
"secretsmanager:GetSecretValue",
15
"secretsmanager:DescribeSecret"
16
],
17
"Resource": "*"
18
}
19
]
20
}
Copied!
1
{
2
"Version": "2012-10-17",
3
"Statement": [
4
{
5
"Sid": "ListSecrets",
6
"Effect": "Allow",
7
"Action": "secretsmanager:ListSecrets",
8
"Resource": "*"
9
},
10
{
11
"Sid": "SecretAccess",
12
"Effect": "Allow",
13
"Action": [
14
"secretsmanager:CreateSecret",
15
"secretsmanager:DeleteSecret",
16
"secretsmanager:GetSecretValue",
17
"secretsmanager:DescribeSecret"
18
"secretsmanager:TagResource",
19
"secretsmanager:UpdateSecret"
20
],
21
"Resource": "*"
22
}
23
]
24
}
Copied!
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.
👏
Last modified 1mo ago
Copy link