bedrock: L2 Constructs
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
### Describe the feature
I would like to use L2 constructs to provision Bedrock related resources with sensible defaults. Now that L1 constructs have been added via https://github.com/aws/aws-cdk/pull/29911 , this should be possible now!
### Use Case
I have been using the awslabs/generative-ai-cdk-constructs library to provision and configure Bedrock related resources, but this library makes use of custom resources to perform all of its actions. I much rather use native constructs rather than custom resources.
https://github.com/awslabs/generative-ai-cdk-constructs
### Proposed Solution
If possible, use the same defaults that the generative-ai-cdk-constructs library is using for each of its L2-like constructs. In my opinion, this would make it a little bit easier to users to migrate without having to change too much. If not, that's fine too.
### Other Information
_No response_
### Acknowledgements
- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change
### CDK version used
2.139.0
### Environment details (OS name and version, etc.)
macOS 14.4.1
Contributor guide
Research direction
Start by reviewing the Bedrock L1 constructs introduced in PR #29911 and comparing the awslabs/generative-ai-cdk-constructs library's L2-like constructs and defaults. Done means defining a decided scope for native L2 Bedrock constructs with sensible defaults and a migration path that avoids custom resources.
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