Think I've run into issues starting with delete before create for vpc related resources created by crosswalk. I manually edited the stack after deleting suggested resources. However, I might have exacerbated the problem by removing too many resources before destroying my stack. Is there a way to sidestep the failure and delete the other resources that it can find? I don't see any suggestion here regarding a stack export.

Resources:
    - 22 to delete

Do you want to perform this destroy? yes
Destroying (dev):
     Type                        Name               Status                  Info
     pulumi:pulumi:Stack         pulumi-vpc-ts-dev  **failed**              1 error
 -   └─ aws:ec2:InternetGateway  clientVpc1         **deleting failed**     1 error
 
Diagnostics:
  aws:ec2:InternetGateway (clientVpc1):
    error: deleting urn:pulumi:dev::pulumi-vpc-ts::awsx:x:ec2:Vpc$awsx:x:ec2:InternetGateway$aws:ec2/internetGateway:InternetGateway::clientVpc1: 1 error occurred:
        * Error waiting for internet gateway (igw-07bf9c311ca705fe8) to detach: couldn't find resource (31 retries)
 
  pulumi:pulumi:Stack (pulumi-vpc-ts-dev):
    error: update failed

Have you tried a

pulumi refresh

? This will sync pulumi state with the resources in AWS. And then try

pulumi destroy

again

You can run pulumi state delete if the resources are gone from the aws console.

Thanks for the references. Refresh seemed to work well.