> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/solution/keypair-not-recognized-when-deploying-instances.md).

# Keypair Not Recognized When Deploying Instances

## Problem

The following error is encountered when trying to launch an instance.

{% tabs %}
{% tab title="None" %}

```none
ERROR (BadRequest): invalid key_name provided (HTTP 400)
```

{% endtab %}
{% endtabs %}

## Environment

* Platform9 Managed OpenStack - All Versions
* Nova

## Cause

The Keypair doesn't exist for the user, for which the instance was attempted to be spawned under.

## Resolution

Launch the instance under the user for which the Keypair was initially uploaded or created as Keypairs aren't shared between users.

## Additional Information

* For information on how to list or create Keypairs via the OpenStack CLI see [OpenStack Docs - Keypair](https://docs.openstack.org/python-openstackclient/pike/cli/command-objects/keypair.html).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://platform9.com/kb/pmo/solution/keypair-not-recognized-when-deploying-instances.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
