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

The key pair already exists in aws, and I'm using a provider to import

`pulumi -C .\pulumi\myproject\ -s mystackname_dev--provider provider-us-west-2=urn:pulumi:mystackname_dev::myproject::pulumi:providers:aws::provider-us-west-2 import aws:ec2/keyPair:KeyPair dev_keypair dev_keypair`

the provider is used in order to support multiple regions on the same stack,
so it only has { region: 'us-west-2' } as config arg

Also, adding verbosity and debug output, doesn't give any insights..

Have you already written some code? Since it's failing on the preview, rather than the import, that implies to me that you've already defined the keypair in code, without the mandatory publicKey parameter.

You could either remove the code and use `pulumi import`, or update the code with the correct publicKey and add the _import_ opt.

I did write some code, but unrelated to keypairs, I commented out index.js completely but it still failed

also I tried raw, without using a provider parameter, just the default project provider and region

Still Errors out, I guess I can create the keypair myself and add the _import_ opt, but that's still a workaround

also there are no keypair resources existing in the stack

ah... even using import is bugged?
I added `import: dev_keypair` to the pulumi options on the resource, but now it says my public-key is mis-matched with the resource that already exists in AWS,
Although I confirmed the saved (MD5) fingerprint in AWS console, matches exactly the same fingerprint I generated locally using the private\public key files

the public hey is in `ssh-rsa` form, do I need to convert it to `-----BEGIN PUBLIC KEY-----`
 form?

You might try switching to a different project and running Pulumi import from there? That will ignore your current code and state, and should correctly generate code. Then you can put that code in the correct project.

You should also export your state and look through it for the keypair, in case Pulumi got confused and it's actually in there. You can use `pulumi state delete &lt;urn&gt;` to delete the "wrong" keypair from the state. You should probably do that before adding the code you get from `pulumi import`.