VPC construct should allow using custom route table for many subnets

Currently it’s not possible to specify either the number of route tables or inject a custom route table to the VPC construct.

Use Case

When creating VPN or Peering connections together with the VPC it would be great when I can customise the route table. For me there is no drawback having only one for many subnets - it’s less complex when modifying it.

Proposed Solution

Make it possible to set the route table per subnet. Currently it’s readonly. Why?

const privateRouteTable = new CfnRouteTable(this, "privateRouteTable", {
    vpcId: vpc.vpcId
})

const selection = vpc.selectSubnets({
    subnetType: ec2.SubnetType.PRIVATE
});
for (const subnet of selection.subnets) {
    subnet.routeTable = privateRouteTable
}

[kennu]

I just had to use:

subnetA.node.tryRemoveChild('RouteTableAssociation')
subnetA.node.tryRemoveChild('RouteTable')

To get rid of the autogenerated route tables in my project. They caused problems in replicating an existing VPC configuration to a new deployment of a project. More specifically they caused problems with VPC S3 Endpoint routing.

[mikepietruszka]

I second this use case. It would be nice to manage the route tables in VPC construct. Currently it’s hard to get a list of created route tables.