> ## Documentation Index
> Fetch the complete documentation index at: https://dev.writer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up BYOK encryption

> Connect your own KMS from AWS, Azure, or GCP to control encryption keys for your Writer organization.

This guide walks you through enrolling your Writer organization in bring-your-own-key (BYOK) encryption. After completing these steps, your data is encrypted with a master key that you control in your own cloud KMS. Writer never sees or stores the key.

For an overview of encryption architecture, scopes, and key actions, see [Encryption Key Management](/home/encryption-key-management).

<Info>
  BYOK encryption is available on Enterprise plans. You must be an organization
  admin to configure encryption settings.
</Info>

<img src="https://mintcdn.com/writer/3p8cus-VbaNQmm3T/images/home/encryption-byok-setup.png?fit=max&auto=format&n=3p8cus-VbaNQmm3T&q=85&s=289e1c042ab8177144d6db6fe46e6a71" alt="Encryption page in AI Studio showing Writer-managed encryption connected and BYOK configuration options for Azure Key Vault, AWS KMS, and GCP Cloud KMS." width="2880" height="1800" data-path="images/home/encryption-byok-setup.png" />

## Prerequisites

Before you begin, make sure you have:

* A Writer Enterprise plan with organization admin access
* An active KMS account with one of the supported providers:
  * [AWS KMS](https://aws.amazon.com/kms/)
  * [Azure Key Vault](https://azure.microsoft.com/en-us/products/key-vault)
  * [GCP Cloud KMS](https://cloud.google.com/kms/docs)
* Permissions to create keys and manage access policies in your KMS

## Enroll in encryption

To enable encryption, navigate to the **Encryption** page under **Admin settings** in AI Studio. You can choose one of two options:

* **Enable Writer-managed encryption**: Writer manages the master key. Select this for zero-maintenance encryption.
* **Bring your own encryption keys**: Connect your own KMS from AWS, Azure, or GCP for direct control over the master key.

You can start with Writer-managed encryption and switch to BYOK at any time.

<Note>
  Enabling encryption applies only to new data created after enrollment.
  Pre-existing data is not retroactively encrypted.
</Note>

## Connect your KMS for BYOK

To set up BYOK, either during initial enrollment or switching from Writer-managed encryption:

1. In AI Studio, navigate to the **Encryption** page under **Admin settings**.
2. On the enrollment screen, select **Bring your own encryption keys**.
   * If encryption is already enabled, select the **Master key** tab and then select **Configure** under **Bring your own keys**.
3. Choose your cloud provider: **AWS KMS**, **Azure Key Vault**, or **GCP Cloud KMS**.
4. Follow the provider-specific instructions in the setup modal to create or select a key in your KMS and grant Writer access.
5. Paste your key identifier (ARN, key URL, or resource name) into the form. Writer validates the connection to your key.
6. After validation succeeds, the setup confirms that your BYOK configuration is complete.

## Control access from your KMS

With BYOK, you can control Writer's access to all encrypted data directly from your cloud provider's KMS console.

### Disable your CMK

Disabling your CMK immediately prevents Writer from unwrapping any DEKs across your entire organization. Use this during an active incident investigation when you need to cut off all access at once.

* In **AWS KMS**: Select the key and choose **Disable key**.
* In **Azure Key Vault**: Set the key's **Enabled** attribute to **false**.
* In **GCP Cloud KMS**: Select the key version and choose **Disable**.

Re-enabling the key restores Writer's ability to decrypt data.

### Delete your CMK

Deleting your CMK permanently prevents Writer from unwrapping any DEKs. All encrypted data across your organization becomes permanently inaccessible.

<Warning>
  Deleting your CMK is irreversible. There is no way for Writer or your cloud
  provider to restore access to your data after the key is deleted.
</Warning>

Most cloud providers enforce a waiting period before permanent deletion (for example, AWS KMS requires a 7-30 day waiting period). Use this window to verify that you intend to destroy access permanently.

## Next steps

* Review [Encryption Key Management](/home/encryption-key-management) for encryption architecture, scopes, and key actions
* [Configure plugins](/home/plugins-overview) to stream security telemetry alongside your KMS audit logs
* [Event logs](/home/event-logs) to monitor request-level activity across your organization
