Add L2 constructs for Amazon Redshift Serverless
dontirun opened this issue · 1 comments
Description
The intent of the L2 construct is to simplify the relationship between Namespaces and Workgroups
Redshift Serverless has two distinct components a Namespace(storage) and a Workgroup(compute). The resources are related , i.e a Workgroup can be associated with a namespace.
Interactions between Workgroups and Namespaces could be further simplified. For example if you want to export user activity logs you need to both enable user activity log exports on the namespace and add the parameter to the workgroup
There are some other small improvements that could be made, like making sure the Workgroup base capacity is set to a proper value or adding helper methods for adding config parameters similar to Redshift Clusters, and using VPC subnet selections.
Roles
| Role | User |
|---|---|
| Proposed by | @dontirun |
| Author(s) | @dontirun |
| API Bar Raiser | @alias |
| Stakeholders | @dontirun |
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
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.
Closing this ticket. We believe the functionality is beneficial, but does not intersect with the core framework and should be vended and maintained separately.