This message was deleted.
# getting-started
s
This message was deleted.
s
This isn't really a Pulumi issue as far as I can tell. This is more about how VPCs work: You can't delete (or make a change that requires re-creating) a subnet when it has stuff in it. The "dependency" text here is originating from the AWS API, not Pulumi. I would recommend working within a single stack for now since you're new to Pulumi.
If your network architecture isn't stable, you're gonna have to tear down any resources in the VPC if the VPC structure changes. Unless you're doing something more advanced, you can't go wrong with public and private subnets split across 3 AZs. If you use the AWSX VPC, you get this by default: https://www.pulumi.com/registry/packages/awsx/api-docs/ec2/vpc/
w
Thanks. Ill look into it
s
Also see my reply to your post in #C019YSXN04B