Ways to ignore AMI changes in a stack

[Jessi]

Hey all,

I have a few stacks that require static singular instances that can't be placed in Auto Scaling Groups.

I'm looking to introduce Packer into our infrastructure and utilize a query to grab the latest AMI of the type needed for the stacks.

However for these static instances, a new AMI being found would cause a replacement of the instance overall which I'd like to avoid.

Anyone have any experience with an issue like this and how did you solve it?

With Terraform I could do something like ignore lifecycle changes for the AMI field in question, but with troposphere I'm finding it a little hard to come up with a solution without over engineering it.