L2 Constructs for Bedrock
- Dominant language
- JavaScript
- Stars
- 572
- Forks
- 108
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
## Description
Create L2 constructs for Bedrock. The [awslabs/generative-ai-cdk-constructs](https://github.com/awslabs/generative-ai-cdk-constructs) provide a L2 construct which is actively used by multiple accounts/user. Merging this construct to CDK official repo will help scale the solution.
Short description of the proposed feature.
- Bedrock Agent.
- Knowledge base, data source
- Guardrails
- Inference Profiles
- Prompt Management
## Roles
| Role | User
|---------------------|------------------------------
| Proposed by | @dineshsajwan @krokoko
| Author(s) | @dineshsajwan @krokoko
| API Bar Raiser | @alias
| Stakeholders | @alias, @alias, @alias
> See [RFC Process](https://github.com/aws/aws-cdk-rfcs#rfc-process) for details
## Workflow
- [x] Tracking issue created (label: `status/proposed`)
- [x] API bar raiser assigned (ping us at [#aws-cdk-rfcs](https://cdk-dev.slack.com/archives/C025ZFGMUCD) if needed)
- [x] Kick off meeting
- [x] RFC pull request submitted (label: `status/review`)
- [x] Community reach out (via Slack and/or Twitter)
- [x] API signed-off (label `status/api-approved` applied to pull request)
- [x] Final comments period (label: `status/final-comments-period`)
- [x] Approved and merged (label: `status/approved`)
- [x] Execution plan submitted (label: `status/planning`)
- [x] Plan approved and merged (label: `status/implementing`)
- [x] Implementation complete (label: `status/done`)
---
> Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.
Contributor guide
Assessment
This issue has not been assessed yet.