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

you can specify the ami in the ec2 resource instead of looking for it using `getAmi` - that should work

<https://www.pulumi.com/registry/packages/aws/api-docs/ec2/instance/#ami_yaml>
hard-code the ami you need here - as long as you use the one you've used previously that shouldn't cause replacements

oh right that seems to work! what’s the best practice here? Now I have to fetch the ami id by myself and replace it to the `get_ami()` , seems a bit manual..

If you want a fixed AMI,  then you should hard-code it. getAMI is useful if you want the AMI to stay up to date - note that that will cause a replacement.

You could also use an `ignoreChanges` on the AMI property for the instance, but in general I agree with Venelin---if you want a fixed AMI, then supply it as a manually-entered configuration value.