Describe the feature
All AWS Bedrock AgentCore constructs currently require physical name properties to be specified. These should be made optional, allowing CDK to automatically generate unique physical names when not specified, following AWS CDK best practices.
According to the AWS CDK Best Practices guide:
"Use generated resource names, not physical names"
Use Case
Making physical names optional provides several benefits:
-
Stack reusability: Required physical names make it difficult to deploy the same stack across multiple environments (dev, staging, production) without code changes.
-
Avoid naming conflicts: Auto-generated names guarantee uniqueness across stacks and environments.
Proposed Solution
Make physical name properties optional in all AgentCore resource Props interfaces and auto-generate names using Names.uniqueResourceName() when not specified.
Other Information
No response
Acknowledgements
AWS CDK Library version (aws-cdk-lib)
all
AWS CDK CLI version
all
Environment details (OS name and version, etc.)
all
Describe the feature
All AWS Bedrock AgentCore constructs currently require physical name properties to be specified. These should be made optional, allowing CDK to automatically generate unique physical names when not specified, following AWS CDK best practices.
According to the AWS CDK Best Practices guide:
Use Case
Making physical names optional provides several benefits:
Stack reusability: Required physical names make it difficult to deploy the same stack across multiple environments (dev, staging, production) without code changes.
Avoid naming conflicts: Auto-generated names guarantee uniqueness across stacks and environments.
Proposed Solution
Make physical name properties optional in all AgentCore resource Props interfaces and auto-generate names using
Names.uniqueResourceName()when not specified.Other Information
No response
Acknowledgements
AWS CDK Library version (aws-cdk-lib)
all
AWS CDK CLI version
all
Environment details (OS name and version, etc.)
all