aws-ram: Missing L2 constructs
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
Currently the only way to create the share with Resource Access Management service is to use the `Cfn` resources.
### Use Case
RAM is a useful service in multi-account setups, having a abstractions for the CFN resources provides better dev-ex then using plain CFN resources
### Proposed Solution
_No response_
### Other Information
_No response_
### Acknowledgements
- [X] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.173.2
### Environment details (OS name and version, etc.)
macOS, Node v22
Contributor guide
Research direction
The issue names no files, tests, or concrete construct scope. Start by locating the existing AWS RAM Cfn resources in the CDK repository and reviewing neighboring L2 construct patterns. Before implementation, clarify with maintainers which RAM abstractions are required and what supported use cases define done.
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
- 25/100