This message was deleted.

You can use the dependsOn opt, if it's not already inferred. I thought ENIs are, though...

yeah I've tried various `CustomResourceOptions`:

dependsOn

,

parent

, etc. Instead of handling that flow above, they offer this preview:

Type                         Name                    Plan       Info
     pulumi:pulumi:Stack          infra-dev                          1 warning
     ├─ aws:ec2:NetworkInterface  networkInterface
 +   │  └─ aws:ec2:Instance       instance                create
 -   └─ aws:ec2:Instance          instance.               delete

After re-reading: you can't get Pulumi to detach ENIs. There is no support for this sort of thing. You would need to do this yourself. Pulumi can delete it for you, and create a new one...

ahhhh I see! But if I hand over the mgmt of making the ENI to Amazon, Amazon will take care of it on replacement?

Yes. I've never had an issue with ENIs. They're essentially atomic within the instances.

so instead of trying something like this to give the instance an EIP: pulumi.com/registry/packages/aws/api-docs/ec2/instance/#network-and-credit-specification-example , I could instead just set something like https://www.pulumi.com/registry/packages/aws/api-docs/ec2/instance/#associatepublicipaddress_nodejs and Amazon should understand iirc

I don't see a need for an explicit ENI in that first example. And I don't see a need for a public IP address, either. If you need a specific private IP address, use

privateIp

. If you don't need a specific IP address, don't provide one, let AWS pick one for you. This is much safer.

this has been working great for me!!! thanks @little-cartoon-10569 🙂