1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
How about registering credentials in SecretsManager and setting up a resource policy to allow access from other AWS accounts?
https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access_examples_cross.html
If you use AWS Organizations to manage your AWS accounts, you can also configure a SecretsManager resource-based policy to allow Organizations IDs.
The SecretsManager policy is configured to allow OU IDs as follows:
{
"Version" : "2012-10-17",
"Statement" : [
{
"Effect" : "Allow",
"Principal" : "*",
"Action" : "secretsmanager:GetSecretValue",
"Resource" : "arn:aws:secretsmanager:ap-northeast-1:123456789012:secret:test",
"Condition" : {
"StringEquals" : {
"aws:PrincipalOrgID": "o-1234567"
}
}
}
]
}
Also, since this will be cross-account access, be sure to set a customer-managed key for SecretsManager encryption and allow the OU ID in the key policy.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/allow-org-ou-to-use-key.html
Relevant content
- asked 3 years ago
- asked a month ago
- asked 6 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 3 years ago