-
Notifications
You must be signed in to change notification settings - Fork 105
S3 Vector L2 CDK Constructs #867
Copy link
Copy link
Open
Labels
status/proposedNewly proposed RFCNewly proposed RFC
Description
Description
We want to add L2 CDK Constructs for S3 vectors: Index, VectorBucket, VectorBucketPolicy
This is part of the effort to move the Bedrock Knowledge Base construct to the bedrock alpha package
https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/AWS_S3Vectors.html
https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-vectors.html
We have an existing implementation for these here: https://github.com/awslabs/generative-ai-cdk-constructs/tree/main/src/cdk-lib/s3vectors
Roles
| Role | User |
|---|---|
| Proposed by | @krokoko |
| Author(s) | @krokoko |
| API Bar Raiser | @alias |
| Stakeholders | @alias, @alias, @alias |
See RFC Process for details
Workflow
- Tracking issue created (label:
status/proposed) - API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
- Kick off meeting
- RFC pull request submitted (label:
status/review) - Community reach out (via Slack and/or Twitter)
- API signed-off (label
status/api-approvedapplied to pull request) - Final comments period (label:
status/final-comments-period) - Approved and merged (label:
status/approved) - Execution plan submitted (label:
status/planning) - Plan approved and merged (label:
status/implementing) - 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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
status/proposedNewly proposed RFCNewly proposed RFC