Multiple Subnets

[ajhool]

The AWS Quickstart seems like a perfect fit for nested templates but they use a very verbose approach (eg. NatGateway1, NatGateway2, etc.) to explicitly declare each resource. Why aren't the VPCs using nested templates to reduce boilerplate? Is there a good reason?

Design decision: should we use a pulumi template to define an AZ (public + private subnet) to reduce boilerplate or mimic the verbose approach used in the quickstart?

• [x] Make design decision above
• [x] Subnets 1
  • [x] Convert the "Simple VPC Deployment" into a subnet resource
  • [x] Public Subnet 1
  • [x] Private Subnet 1A
  • [x] Private Subnet 1B
  • [x] Deploy
• [x] Subnet 2
  • [x] Add the resource
  • [x] Public Subnet 2
  • [x] Private Subnet 2A
  • [x] Private Subnet 2B
  • [x] Deploy
• [x] Subnet 3
  • [x] Add the resource
  • [x] Public Subnet 3
  • [x] Private Subnet 3A
  • [x] Private Subnet 3B
  • [x] Deploy
• [x] Subnet 4
  • [x] Add the resource
  • [x] Public Subnet 4
  • [x] Private Subnet 4A
  • [x] Private Subnet 4B
  • [x] Deploy

[ajhool]

Re: "Make Design Decision Above"

As far as I can tell, there is no good reason that Nested Templates weren't used in the AWS Quickstart.