aws_bedrockagentcore: Support for clientSecretSource: "EXTERNAL" and clientSecretConfig
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 71
Description
Hi Team,
I was wondering when will clientSecretSource: "EXTERNAL" and clientSecretConfig (which is already supported in AWS CLI) be supported in CDK and CloudFormation as shown in below setting using CLI?
{
"name": "test_external_secret_provider",
"credentialProviderVendor": "CustomOauth2",
"oauth2ProviderConfigInput": {
"customOauth2ProviderConfig": {
"clientId": "my-test-client-id",
"clientSecretSource": "EXTERNAL",
"clientSecretConfig": {
"secretId": "SECRET_ID",
"jsonKey": "client_secret"
},
"oauthDiscovery": {
"discoveryUrl": "DISCOVERY_URL"
}
}
### AWS CDK Library version (aws-cdk-lib)
aws-cdk-lib@2.257.0
### AWS CDK CLI version
2.1125.0 (build 71fd29e)
### Environment details (OS name and version, etc.)
macOS 26.5 (Build 25F71), arm64
Contributor guide
Research direction
Start by locating the aws_bedrockagentcore credential-provider definitions exposed by CDK and CloudFormation, then compare their supported properties with the AWS CLI example in the issue. Add support for clientSecretSource="EXTERNAL" and clientSecretConfig, and verify that the resulting CDK and CloudFormation definitions accept the shown configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100