MSK cluster must enforce TLS encryption for client-broker communication
High
AWS
General
aws-msk-cluster-encryption
Applies to
AWS::MSK::Cluster
What CGPulse checks
A resource passes this rule when encryptionInTransit.clientBroker must equal TLS. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Set client-broker encryption to TLS to encrypt all Kafka client-broker communication. In AWS Console: MSK > Clusters > select cluster > Edit > set Encryption in transit to TLS. See: https://docs.aws.amazon.com/msk/latest/developerguide/msk-encryption.html
Terraform
resource "aws_msk_cluster" "{name}" {
encryption_info {
encryption_in_transit {
client_broker = "TLS"
}
}
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related AWS rules
- ACM certificate must be eligible for renewal
- ACM certificate must be in issued status
- Amplify app should have basic auth disabled for production
- API Gateway REST API must have an endpoint configuration
- API Gateway V2 API must be properly configured
- App Runner service must have encryption enabled
- AppSync API must have logging configured
- AppSync API must have X-Ray tracing enabled