Full control over VPC and subnet configuration
otaviomacedo opened this issue · comments
Otavio Macedo commented
Description
New L2 constructs to allow for greater control over subnet configuration. There are a number of use cases that are not supported by the Vpc
construct.
See aws/aws-cdk#5927 for more details.
Roles
Role | User |
---|---|
Proposed by | @otaviomacedo |
Author(s) | @otaviomacedo |
API Bar Raiser | @corymhall |
Stakeholders | @udaypant, @evgenyka |
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-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.