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

Hello, does anybody have an example of creating an AWS AMI with setup scripts?

We used ImageBuilder for while. I believe that's being decommissioned though, I think I saw an EOL notice go out about it, a few weeks ago.

You might be better off with the AWS SDK, or Hashicorp's tool, or somesuch.

OK, I read Packer, but want to use Pulumi.

I suggest not using Pulumi for packaging things. Treat that as part of the build phase: keep Pulumi for deployment.

Just build the AMI. It's a pacakge, just like an NPM package or a jar. Build it once. Then use Pulumi to deploy it many times.

You shouldn't use Pulumi to build your .net DLL assemblies, and you shouldn't use Pulumi to build your AMI files.

I don't know anything other than Packer, for AMI.
Not doing manually
1. launch a vm,
2. install packages
3. create an AMI from it

You can build AMIs using AWS image builder (which you can set up using Pulumi), or by snapshotting a running machine.

Snapshotting is the classic way, it's very scriptable, but it's definitely not within Pulumi's purvue.

Check to see if an end-of-life announcement has been made about it. I think I read that it's going to be shut down.

I would use Packer alongside Pulumi, so a Packer build creates an AMI, which then triggers a `pulumi up` (details depend on what tools you're using in your toolchain).

Panic over! Image Builder announcement was unrelated to AWS, it was a different provider that was ending an integration. My bad.

<@U02FZC2RE0Y> I only need to build AMI, once in a while. The goal is to avoid any manual steps.