> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/security-and-compliance/access-control-1/at-rest-encryption.md).

# At Rest Encryption

At Rest encryption support in DuploCloud

DuploCloud automatically encrypts resources at rest using cloud provider–specific keys. This ensures that all data stored in cloud resources is protected by default.

When creating resources, encryption is applied using one of the following options:

1. **Default Tenant Key** – A key automatically generated and managed by the cloud provider for the Tenant. This key is applied by default if no custom key is available.
2. **Plan-level custom KMS key** – A custom key added to a Plan. This key can be used for resources across all Tenants in the Plan.
3. **Tenant-level custom KMS key** – A custom key added to a specific Tenant. This key can only be used for resources created within that Tenant.

These options give users flexibility to apply encryption strategies that meet their specific requirements.

{% hint style="info" %}
For detailed instructions on adding Plan-level or Tenant-level keys and selecting them when creating resources, see the [KMS Keys documentation](/docs/automation-platform/security-and-compliance/access-control-1/at-rest-encryption/kms-keys.md).
{% endhint %}


---

# 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://docs.duplocloud.com/docs/automation-platform/security-and-compliance/access-control-1/at-rest-encryption.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.