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

Anybody have experience with Pulumi and localstack, specifically in the lookup of ec2 ami image ids?

I'm successfully getting an ami-id, but it turns out to be invalid:

```l2024-05-08T21:30:16.133  INFO --- [et.reactor-1] localstack.request.aws     : AWS ec2.DescribeImages =&gt; 200
2024-05-08T21:30:18.410  INFO --- [et.reactor-2] localstack.request.aws     : AWS ec2.RunInstances =&gt; 400 (InvalidAMIID.NotFound)```
```  aws:ec2:Instance (bastion-instance-subnet-c726a7ea):
    error: 1 error occurred:
        * creating EC2 Instance: InvalidAMIID.NotFound: The image id 'ami-04681a1dbd79675a5' does not exist
        status code: 400, request id: 17875f10-4c5a-438a-adaf-1f3855466a0f```


Got it. The localstack documentation shows which AMIs are supported by localstack here: <https://docs.localstack.cloud/user-guide/aws/ec2/>

So, to make it work with pulumi, I just need to adjust our components to use a supported AMI when deploying to localstack.