# Ensure MSK Connect Connectors Are Encrypted in Transit

- Source: https://support.icompaas.com/support/solutions/articles/62000233565-ensure-msk-connect-connectors-are-encrypted-in-transit
- 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 in transit ensures that data exchanged between MSK Connect connectors and Kafka clusters is protected from unauthorized access and tampering. By enabling encryption in transit, you safeguard sensitive data and comply with security best practices.

#### **Rationale**

-   Enhanced Security: Protects data from interception and unauthorized access during transmission.
    
-   Compliance: Meets regulatory requirements for securing data in transit.
    
-   Risk Mitigation: Reduces the risk of man-in-the-middle attacks and data breaches.
    

#### **Impact**

**Pros:**

-   Ensures secure communication between MSK Connect connectors and Kafka clusters.
    
-   Reduces the risk of data interception and tampering.
    
-   Aligns with compliance and security standards.
    

**Cons:**

-   May introduce slight latency due to encryption overhead.
    
-   Requires proper configuration of encryption settings.
    

#### **Default Value**

By default, MSK Connect supports encryption in transit using TLS. However, this must be explicitly configured to ensure secure communication.

#### **Pre-Requisite**

IAM Permissions:

-   kafka:DescribeCluster
    
-   kafka:UpdateClusterConfiguration
    
-   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 Connectors from the left-hand menu.
    
4.  Check the encryption settings for each connector and ensure that TLS is enabled.
    

**Using AWS CLI:**

1.  Verify Encryption Settings:  
    
    aws kafka describe-cluster --cluster-arn <cluster-arn> --query "ClusterInfo.EncryptionInfo.EncryptionInTransit"
    
2.  Ensure that the EncryptionInTransit field is set to TLS.
    

**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/97592104f80390df.png)
    
3.  Select the connector to update.  
    ![](https://support.icompaas.com/assets/kb/ea7af8e175a030e3.png)
    
4.  Edit the connector configuration to enable encryption in transit using TLS.
    
5.  Save the changes.
    

**Using AWS CLI:**

1.  Update Encryption Settings:  
    
    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.EncryptionInTransit"
    

#### **Backout Plan**

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

1.  #### If enabling encryption causes issues with connector communication, sign in to the AWS Management Console.  
    Navigate to Amazon MSK Connect, select the connector, and go to Edit.  
      ![](https://support.icompaas.com/assets/kb/192ee7b027ad340e.png) ![](https://support.icompaas.com/assets/kb/59bc7a85712f914f.png)
    
2.  #### Disable TLS encryption and switch to non-encrypted communication.
    
3.  #### 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**

-   [Amazon MSK Encryption Documentation](https://docs.aws.amazon.com/msk/latest/developerguide/msk-encryption.html)
    
-   [AWS Security Hub Controls for MSK](https://docs.aws.amazon.com/securityhub/latest/userguide/msk-controls.html)
    
-   [KafkaClusterEncryptionInTransit API Documentation](https://docs.aws.amazon.com/MSKC/latest/mskc/API_KafkaClusterEncryptionInTransit.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.
