(secretsmanager): Access secret string stored in secret manager from CDK

[simran66]

I am storing the Codestar connection string for Bitbucket in Secret manager. How can I retrieve it in the CDK app:

I am trying with:

// Get Bitbucket Connection String
const bitbucketConnectionString = Secret.fromSecretCompleteArn(this, "bitbucketConnectionString", "arn:aws:secretsmanager:us-west-2:1000000000:secret:BitbucketCloudConnection-abcdef0");


// SourceAction
const sourceAction = new BitBucketSourceAction({
    actionName: 'BitbucketSource',
    owner: 'abc',
    repo: repoName,
    output: sourceOutputArtifact,
    connectionArn: bitbucketConnectionString,
})

bitbucketConnectionString is not a string though.

1. How do I access the secret value which is actually a connectionString stored in Secret Manager.

2. What is the right way to replace region and accountId with Pseudo variables in the connection string;

   arn:aws:secretsmanager:us-west-2:1000000000:secret:BitbucketCloudConnection-abcdef0

[jogold]

You need to use the SecretValue class from core: https://github.com/aws/aws-cdk/blob/master/packages/%40aws-cdk/core/README.md#secrets

[simran66]

@simran66 Did you mean bitbucketConnectionString.secreValue ? It doesn't return me a string. connectionArn is expecting a string value. Can you share in the context of the question, please? I read through the page and didn't understand still

[jogold]

// SourceAction
const sourceAction = new BitBucketSourceAction({
    actionName: 'BitbucketSource',
    owner: 'abc',
    repo: repoName,
    output: sourceOutputArtifact,
     // use it with secret name, no need for the -abcdef0 part
    connectionArn: SecretValue.fromSecretsManager('BitbucketCloudConnection').toString()
})

Just like the example in the README in core.

SecretValue is a class from @aws-cdk/core.

[SomayaB]

Closing since jogold's guidance seems to have solved the issue.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.