No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Based on the docs, yes.

<https://www.pulumi.com/registry/packages/aws/api-docs/ec2/instance/#ami_nodejs|https://www.pulumi.com/registry/packages/aws/api-docs/ec2/instance/#ami_nodejs>

Note the symbol next to "ami", which signifies recreate on change

Is there any way to get that AMI id to be "sticky". Like the first time the code it run, it gets the latest and greatest AMI, but on subsequent runs, if the ec2 instance is already running, it leaves it alone?

I think you want a Launch Template, however it's been many years since I've worked with ec2 instances

If the search criteria for the AMI changed, I'd want the ec2 instance to get updated. But as long as the AMI currently being used by the instance matches the filters that found the AMI, it would be nice if there would be some way to keep it.

You might be able to use `ignoreChanges` on the AMI property of the EC2 instance (just an idea, I haven’t tested it).