I may be mistaken, but I’m not sure you’re going to be able to completely alleviate the behavior(s) you’re describing. Regardless of the tool in use (Pulumi or something else), the root issue is that the AWS API prevents you from deleting a subnet that has resources attached. If it’s necessary to delete/recreate a subnet in Stack A and resources from Stack B are using that subnet, there’s not much Pulumi can do. If I may ask, why are you using different stacks? What requirements led you to using separate stacks for A and B?