This message was deleted.

sparse-intern-71089

01/30/2024, 12:01 PM

This message was deleted.

adorable-house-61348

01/30/2024, 12:05 PM

you can specify the ami in the ec2 resource instead of looking for it using

getAmi

- that should work

adorable-house-61348

01/30/2024, 12:06 PM

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

creamy-sugar-83202

01/30/2024, 12:15 PM

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..

adorable-house-61348

01/30/2024, 12:16 PM

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.

👍 1

creamy-sugar-83202

01/30/2024, 1:02 PM

alright, thank you!

🚀 1

salmon-account-74572

01/30/2024, 8:28 PM

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.

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.