# Ensure Kafka Cluster Encryption at Rest Uses Customer Managed Keys (CMK)

- Source: https://support.icompaas.com/support/solutions/articles/62000233567-ensure-kafka-cluster-encryption-at-rest-uses-customer-managed-keys-cmk-
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [AWS Checks New Version](https://support.icompaas.com/support/solutions/62000112673) › [AWS New Checks](https://support.icompaas.com/support/solutions/folders/62000169206)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability**

-   **Level 2**

#### **Description**

Encryption at rest protects sensitive data stored in Kafka clusters by encrypting it on disk. Using Customer Managed Keys (CMK) provides greater control over the encryption process, including key rotation, access policies, and lifecycle management. This ensures compliance with stringent security and regulatory requirements.

#### **Rationale**

-   Enhanced Security: CMKs provide full control over encryption keys, ensuring that only authorized users can access sensitive data.
    
-   Compliance: Meets regulatory requirements for data protection and privacy by using customer-controlled encryption keys.
    
-   Key Management: Allows for key rotation and revocation, ensuring better security practices.
    

#### **Impact**

**Pros:**

-   Provides full control over encryption keys and policies.
    
-   Enhances data security by ensuring only authorized access.
    
-   Aligns with compliance and regulatory standards.
    

**Cons:**

-   Requires additional configuration and management of CMKs.
    
-   May incur additional costs for using AWS Key Management Service (KMS).
    

#### **Default Value**

By default, Kafka clusters use AWS-managed keys for encryption at rest. Customer Managed Keys must be explicitly configured.

#### **Pre-Requisite**

IAM Permissions:

-   kafka:ListClusters
    
-   kafka:DescribeCluster
    
-   kms:CreateKey
    
-   kms:DescribeKey
    
-   AWS CLI installed and configured.
    

#### **Remediation**

#### **Test Plan:**

 **Using AWS Console:**

1.  Sign in to the AWS Management Console.
    
2.  Navigate to the MSK Dashboard.
    
3.  Select Clusters from the left-hand menu.
    
4.  Check the encryption settings for each cluster and verify if CMKs are being used.
    

**Using AWS CLI:**

1.  List All MSK Clusters:  
    
    aws kafka list-clusters --query "ClusterInfoList\[\*\].{ClusterName:ClusterName,EncryptionAtRest:EncryptionInfo.EncryptionAtRest.KmsKeyArn}"
    
2.  Verify that the KmsKeyArn field is populated with a CMK ARN.
    

#### **Implementation Steps:** 

**Using AWS Console:**

1.  Sign in to the AWS Management Console.
    
2.  Navigate to the MSK Dashboard.![](https://support.icompaas.com/assets/kb/ce6d3e86cc499251.png)
    
3.  Select the cluster to update.  
    ![](https://support.icompaas.com/assets/kb/1446034beb880d12.png)
    
4.  Click Edit Cluster and configure encryption at rest to use a Customer Managed Key (CMK) from AWS KMS.
    
5.  Save the changes.
    

**Using AWS CLI:**

1.  Update the cluster to use a CMK:  
    
    aws kafka update-cluster-configuration --cluster-arn <cluster-arn> --configuration-info file://config.json
    
2.  Verify the Changes:  
    
    aws kafka describe-cluster --cluster-arn <cluster-arn> --query "ClusterInfo.EncryptionInfo.EncryptionAtRest.KmsKeyArn"
    

#### **Backout Plan**

#### **Using AWS Console:**

1.  #### If enabling encryption causes issues with connector communication, sign in to the AWS Management Console.
    
2.  #### Navigate to Amazon MSK Connect, select the connector, and go to Edit. ![](https://support.icompaas.com/assets/kb/bed7c77759c55fc5.png) ![](https://support.icompaas.com/assets/kb/eab96a2d9ed91f8f.png)
    
3.  #### Disable TLS encryption and switch to non-encrypted communication.
    
4.  #### Save the changes and verify that the connector can communicate without encryption.
    

#### **Using AWS CLI:**

1.  #### To disable encryption in transit, run the following command:  
    
    aws kafka update-connector --connector-arn <CONNECTOR\_ARN> --encryption-in-transit '{"enabled": false}' --region <REGION>
    
2.  #### Verify that encryption has been disabled:  
    
    aws kafka describe-connector --connector-arn <CONNECTOR\_ARN> --region <REGION>
    

#### **References**

-   [AWS MSK Encryption at Rest Documentation](https://docs.aws.amazon.com/msk/latest/developerguide/msk-encryption.html)
    
-   [AWS KMS Documentation](https://docs.aws.amazon.com/kms/latest/developerguide/)
    
-   [AWS Config Rule for MSK Encryption](https://docs.aws.amazon.com/config/latest/developerguide/msk-encryption-at-rest.html)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.
