(aws-ec2): L2 Transit Gateway #17528
Comments
NukaCody
added
feature-request
github-actions
bot
added
the
@aws-cdk/aws-ec2
|
Hi @NukaCody ! Thanks for the idea and link to your construct library! To help us prioritize new L2s, we look for interest and engagement from the community (as well as internal metrics on how much usage the underlying L1s receive). I'm going to initially assign this as a We use 👍 s to help prioritize our work; you can reach out to the cdk.dev community on Slack to solicit support for prioritization. Once we have a good number of people voting to prioritize this, we can dive in. The first step(s) would be to review the API via either an issue in our RFCs repo or as a PR against this issue with just the module's README, showing the API off and how a user would interact with it. |
njlynch
added
effort/medium
### Issue # (if applicable) Closes #17528 ### Description of changes Create new Transit Gateway L2 with the following constructs: * `TransitGateway` * `TransitGatewayRouteTable` * `TransitGatewayRoute` * `TransitGatewayVpcAttachment` * `TransitGatewayRouteTableAssociation` * `TransitGatewayRouteTablePropagation` #### Important Design Decision As described in the README, the CDK disables the creation of the default route table by EC2 and instead the CDK will create a "custom" default route table in its place. This is primarily because there is no way to obtain the route table ID of the EC2 created default route table without a custom resource. The CDK will disable the `defaultRouteTablePropagation` and `defaultRouteTableAssociation` properties on the L1 (when both are disabled, EC2 does not create the default route table), but the properties are still exposed on the CDK TransitGateway interface to allow it to be toggled for the CDK created default route table. The automatic association/propagation is being mimicked by CDK implementation and not relying on the actual EC2 feature. ### Describe any new or updated permissions being added n/a ### Description of how you validated changes Unit + Integration tests to verify that the deployed resources behave as expected. ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license* --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
|
Comments on closed issues and PRs are hard for our team to see. |
Description
L2 Construct for Transit Gateway
Use Case
Transit Gateways are used to build a centralize hub and spoke model, common in complex networking environments with multiple VPCs.
Proposed Solution
The code has been written for a side project, would love to contribute it upstream but wanted to make sure I'm not conflicting with anything: https://github.com/NukaCody/l2-transit-gateway
Other information
No response
Acknowledge
The text was updated successfully, but these errors were encountered: