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

Presumably the original key still exists? I think that without it, you won't be able to do anything except destroy the state file.
Assuming you do have the original key, you should be able to change the secrets provider key to refer to the key by ID instead of alias. There's more information here: <https://www.pulumi.com/docs/intro/concepts/secrets/#aws-key-management-service-kms>
You can pass the key reference on the command line (`--secrets-provider`) or override the value in the Pulumi.yaml file (or is it in the Pulumi.&lt;stack&gt;.yaml file? I forget).

Thanks <@U012UJTT55M>, that’s what I suspected. :disappointed: I think I nuked the key (and I didn’t notice until now, so I think the pending deletion was set to 7 days or something).. Not a big deal, this was our dev account.