search

stajkowski / terraform-aws-networking

AWS Networking Module for Terraform
Apache License 2.0
0 stars 0 forks source link

Add depth to Subnets #9

Closed stajkowski closed 3 months ago

stajkowski commented 4 months ago

Have the ability to provide a list of names for the depth of private subnets, instead of providing just a number of subnets. At each custom level, can specify number of subnets. These can be referred to as name for placing resources in these subnets. Alternatively, provide an option for this to be non-routeable space that gets added to the VPC as a secondary CIDR with its own pool.

stajkowski commented 4 months ago

This is a bit more involved, but ideally get rid of the public/private concept and just allow for custom subnets that are assigned to custom route tables, and then N number of NACLs assigned to the custom subnets. This also involves stating which named subnets the internet gateway belongs to and what subnets the NAT GW belongs to as well. This is a complete refactor and will also probably require config validation to ensure names are correct and accessible.

stajkowski commented 4 months ago

Route Tables => Subnets => RouteTable Association => NACL to Subnets => IGW/NATGW to Subnets => Gateway Services to Subnets => TGW to Subnets.

Output named subnets map.

stajkowski commented 4 months ago

This would be a major uplift and breaking change. The base public/private is great for straight forward simple configurations. What I can do is add an additional subnets parameter that can have named subnets, additional control over if the route to NATGW is configured, any privatelink or gw services, nacl config, etc.