instead of defining the CIDR then doing all the NACL's, security groups before the subnets are defined. define the CIDR, Subnets, routing, NACL's then security groups.
reorder the subnets to follow the packet flow from the transit gateway through the security VPC(or from the internet back to the TGW.
dont use a /16 for 2 firewalls.
Describe the solution you'd like
1: define the CIDR, Subnets, routing, NACL's then security groups. (see TFVARS below)
2: Make the subnets follow the packet flow from the TGW through the security VPC to the IGW (See TFVARS BELOW)
Packet Flow (Just refer to any of the architecture drawings)
TGW > Security VPC > tgw-attach-subnet > Endpoint-subnets > GWLB > private-dataplane-subnet > MGMT-Subnet > Public-subnet
3: simplify the subnetting even though it doesn't match the reference architecture or deployment guide.
the defined subnetting using a /16 for 2-4 firewalls.... No customer will EVER deploy and infrastructure with a /16. just use a real world example that is easy to follow. assign a /22 or /23 for the CIDR and a /24 for each AZ path from the TGW
4: repeat order for application VPC's also. a /16 is stupid.
Describe alternatives you've considered.
vpcs = {
Do not use - in key for VPC as this character is used in concatation of VPC and subnet for module subnet_set in main.tf
Is your feature request related to a problem?
No- its a simplification
instead of defining the CIDR then doing all the NACL's, security groups before the subnets are defined. define the CIDR, Subnets, routing, NACL's then security groups.
reorder the subnets to follow the packet flow from the transit gateway through the security VPC(or from the internet back to the TGW.
dont use a /16 for 2 firewalls.
Describe the solution you'd like
1: define the CIDR, Subnets, routing, NACL's then security groups. (see TFVARS below) 2: Make the subnets follow the packet flow from the TGW through the security VPC to the IGW (See TFVARS BELOW)
Packet Flow (Just refer to any of the architecture drawings) TGW > Security VPC > tgw-attach-subnet > Endpoint-subnets > GWLB > private-dataplane-subnet > MGMT-Subnet > Public-subnet
3: simplify the subnetting even though it doesn't match the reference architecture or deployment guide.
the defined subnetting using a /16 for 2-4 firewalls.... No customer will EVER deploy and infrastructure with a /16. just use a real world example that is easy to follow. assign a /22 or /23 for the CIDR and a /24 for each AZ path from the TGW
4: repeat order for application VPC's also. a /16 is stupid.
Describe alternatives you've considered.
vpcs = {
Do not use
-
in key for VPC as this character is used in concatation of VPC and subnet for modulesubnet_set
inmain.tf
security_vpc = { name = "security-vpc" cidr = "10.254.0.0/22" subnets = {
Do not modify value of
set=
, it is an internal identifier referenced by main.tf}
Additional context
No response