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

do you happen to be doing something like enabling hibernation support on an instance type that doesn’t support it?

I don’t think so! I’m using code that I’ve used elsewhere for spinning up instances. Just assigning security groups, subnet, ami, instance type, key, and disk space

Generally this is due to incompatible inputs such as specifying an AMI that is paravirtualized on an instance type that requires HVM or an instance type that requires VPC in EC2-classic.

You might get more information from the error with the `--debug` flag. If not, if you can share your `preview --diff` we can try to figure it out with you.

<@UDEJ1F5SQ> yea looks like something changed with the AMIs. I was dynamically fetching the most recent debian one. I went back to the AMI used by the latest EC2 instance I created and it worked fine. Not sure what I need to adjust here but at least it worked sort of

You might need to provide an additional filter as shown at <https://www.pulumi.com/docs/reference/pkg/aws/getami/#example-usage>.