AWS S3 directory bucket L2 constructs
- Dominant language
- JavaScript
- Stars
- 572
- Forks
- 108
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
## Description
Add L2 constructs for AWS S3 directory bucket creation that abstracts this resource for better usability and developer experience.
## Roles
| Role | User
|---------------------|------------------------------
| Proposed by | @romsrb
| Author(s) | @romsrb
| 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`)
- [ ] API bar raiser assigned (ping us at [#aws-cdk-rfcs](https://cdk-dev.slack.com/archives/C025ZFGMUCD) 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-approved` applied 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.
Contributor guide
Research direction
Start with the linked RFC Process and the checklist in this issue. This is a proposal for AWS S3 directory bucket L2 constructs, not an implementation task with named files or tests; progress requires API review, community feedback, approval, an execution plan, and eventual implementation completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100