VPC construct with full control
- Dominant language
- TypeScript
- Stars
- 12.9k
- Forks
- 4.6k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 83
Description
Many people are not satisfied with the out of the box VPC experience we provide.
They have slightly different IP layout needs, or AZ selection or subnet layout or routing table, or don't like the hierarchy/naming used. The current VPC is not flexible enough.
Provide a compatible Vpc construct that can be configured to users' heart's content.
Creating this issue to link all others to.
* [ ] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change
---
This is a :rocket: Feature Request
Related: #6683
Contributor guide
Research direction
Start by reading this umbrella issue and its related issue #6683. The issue calls for a compatible, highly configurable VPC construct covering IP layout, availability-zone selection, subnets, routing tables, and hierarchy or naming, but does not identify files, tests, or a settled design. Done would require an agreed scope and implementation plan that addresses compatibility and possible breaking changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100