Manage customer-managed encryption keys

Last updated on Nov 18, 2026

Manage the lifecycle of a customer-managed key used for encryption at rest.

After configuring customer-managed encryption keys (BYOK), administrators can manage the key lifecycle, including rotation, suspension, and destruction. These actions affect access to encrypted data.

In the user interface, this feature is labeled Customer Managed Encryption.

Before you begin

  • You must be an account-level administrator.
  • BYOK must already be configured for the account.
  • The configured key must be accessible through AWS Key Management Service (KMS).

To access this setting

  • Navigate to Account Settings > Security Settings > Customer Managed Encryption.
Customer Managed Encryption settings showing AWS credentials, the KMS key ARN, TTL, and the option to re-encrypt existing agreements.
Customer Managed Encryption settings for configuring encryption keys and re-encrypting existing agreements.

Controls

  • Rotate key
    • Updates the key version used for encryption operations.
  • Revert key
    • Restores the previously used key version.
  • Suspend key
    • Blocks encryption and decryption operations using the configured key.
  • Destroy key
    • Permanently removes access to encrypted content.

Impact:

  • Changes to key state affect access to BYOK-encrypted content after the configured TTL period.

How to manage the key

  • AWS automatic rotation: AWS KMS supports automatic annual rotation for symmetric CMKs. When enabled, AWS generates new key material each year while retaining previous material for decrypting existing data. No changes are required in Acrobat Sign.
  • Manual CMK replacement: If you create a new CMK with a different ARN, update the KMS key ARN and Save. Acrobat Sign validates the new key immediately.
  • Credential rotation: If you rotate your AWS access key, update the AWS access key ID and AWS secret access key, and then Save the configuration. Acrobat Sign validates the new credentials immediately.
  • Re-encrypt existing agreements: Select Re-encrypt existing agreements and then Save to initiate background re-encryption using the customer-managed key. 
    • Once the process starts, select View details in the Customer Managed Encryption section to monitor progress, review failures, or stop, resume, and retry the process.

If new credentials do not have access to the CMK, the Save operation will fail, and the existing configuration remains unchanged.

  • Disable CMK in AWS KMS: BYOK agreements become inaccessible after the cache TTL expires. All account admins receive an email notification. Reversible by re-enabling the key in AWS KMS.
  • Delete CMK in AWS KMS: Same as disabling, but permanent once the AWS waiting period completes. You can cancel the deletion only during the waiting period.
  • Deactivate IAM credentials in AWS: BYOK agreements become inaccessible after the cache TTL expires. Reversible by reactivating the credentials or entering new ones in Acrobat Sign.
  • Disable customer-managed encryption: Clear Enable encryption with Customer Managed Key (CMK) for your Acrobat Sign account and select Save. 
    • Acrobat Sign initiates background re-encryption of existing BYOK-protected agreements using Adobe-managed keys. 
    • Keep your AWS KMS key and credentials active until re-encryption completes to maintain access to agreements during the transition.
Alert

Keep your customer-managed key and AWS credentials active until re-encryption to Adobe-managed keys completes.

Disabling the key or revoking credentials before completion makes agreements that are still protected by the customer-managed key inaccessible after the cache TTL expires.

Failure notifications

When Acrobat Sign detects a CMK failure (for example, a revoked key, invalid credentials, or disabled key), it sends an email notification to all active Account Administrators for the affected account. The email includes the type of failure and steps to resolve the issue. Notifications are rate-limited to one per 24 hours per account to prevent notification fatigue.

Things to know

  • Agreements created after BYOK is enabled use customer-managed encryption. Existing eligible agreements can also be re-encrypted through a background process.
  • BYOK is only applied at the account level. Keys cannot be configured for individual groups.
  • If the customer-managed key (CMK) becomes unavailable, BYOK-encrypted agreements become inaccessible after the configured TTL period. Agreements not encrypted using BYOK are not affected.
  • The TTL is configurable from 5 to 60 minutes (default 60). 
  • Use a multi-region CMK can improve availability, as Acrobat Sign operates across multiple AWS regions.