This message was deleted.

sparse-intern-71089

11/03/2023, 7:13 PM

This message was deleted.

dry-keyboard-94795

11/03/2023, 7:50 PM

Based on the docs, yes. https://www.pulumi.com/registry/packages/aws/api-docs/ec2/instance/#ami_nodejs Note the symbol next to "ami", which signifies recreate on change

cool-scientist-53915

11/03/2023, 7:51 PM

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?

dry-keyboard-94795

11/03/2023, 7:52 PM

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

cool-scientist-53915

11/03/2023, 7:53 PM

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.

salmon-account-74572

11/06/2023, 12:47 PM

You might be able to use

ignoreChanges

on the AMI property of the EC2 instance (just an idea, I haven’t tested it).

Open in Slack

Previous Next

Pulumi Community

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.