> For the complete documentation index, see [llms.txt](https://docs.envector.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.envector.io/1.5.x/key-management/client-managed-keys.md).

# Client-Managed Keys

In the client-managed model, the SDK generates the homomorphic-encryption key set and keeps the secret keys on the client side — either on the local filesystem or in AWS-backed storage (S3 + Secrets Manager). The server only ever holds and activates the **public** keys.

This section covers the client-side key workflow:

* [Key Generation](/1.5.x/key-management/client-managed-keys/key-generation.md) — create a key set (`SecKey`, `EncKey`, `EvalKey`, `MetadataKey`), choose storage, and optionally seal with a KEK.
* [Key Registration & Deletion](/1.5.x/key-management/client-managed-keys/key-registration.md) — register/activate public keys on the server and remove them when no longer needed.
* [AWS-Backed Key Storage](/1.5.x/key-management/client-managed-keys/aws-key-storage.md) — delegate key custody to Amazon S3 + AWS Secrets Manager instead of the local filesystem.

To configure these keys at client initialize time (`key_path`, `seal_mode`, `key_store`, …), see [Key Configuration](/1.5.x/sdk-user-guide/initialize/key-config.md) in the Initialize flow.

> For an alternative where the enVector KMS manages the full key lifecycle (generation, sealing, rotation, audit), see [Managed KMS](/1.5.x/key-management/managed-kms.md). For a comparison of the two models, see [Key Management](/1.5.x/key-management/key-management.md).


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.envector.io/1.5.x/key-management/client-managed-keys.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.