CDK: Utilize SSM parameters for cross stack references
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
Requesting to change the automated use of CFN exports/imports for cross stack references to utilize SSM parameters and parameter references. This makes updates to the referenced values more dynamic and eliminates the issue of outputs not being able to be updated/deleted due to being in use as it is natively supported to reference SSM parameters in CloudFormation https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/dynamic-references-ssm.html#dynamic-references-ssm-pattern.
### Use Case
When deploying a CDK app with cross stack references, the initial deployment with exports/imports functions well, but when updating that value, CloudFormation produces an error as exports that are in use are not able to be updated.
### Proposed Solution
_No response_
### Other Information
_No response_
### Acknowledgements
- [x] I may be able to implement this feature request
- [x] This feature might incur a breaking change
### CDK version used
2.191
### Environment details (OS name and version, etc.)
Windows 10
Contributor guide
Research direction
Start by tracing how CDK currently creates CloudFormation exports/imports for cross-stack references. Compare that flow with CloudFormation SSM parameter references and review the linked AWS dynamic-reference documentation. Done should include dynamic cross-stack references whose referenced values can be updated or deleted without the current export-in-use failure, with the breaking-change implications and tests addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100