Configure a custom domain name for your Amazon MSK cluster
Big Data Blog
This article explains how to configure a custom domain name for your Amazon MSK (Managed Streaming for Apache Kafka) cluster when using SASL/SCRAM authentication. It provides a solution to use a Network Load Balancer (NLB), Route 53, and the advertised listener configuration option in Amazon MSK to support custom domain names.
Specifically, the article covers:
- Solution overview and prerequisites
- Launching the CloudFormation template
- Setting up the EC2 instance and creating a certificate
- Importing the certificate to ACM and the Kafka client trust store
- Setting up DNS resolution and creating EC2 target groups
- Setting up NLB listeners and enabling cross-zone load balancing
- Creating DNS A records in a private hosted zone
- Configuring the advertised listener in the MSK cluster
- Testing the setup and cleaning up resources
- Summary of the solution
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Apr 21
2026
2026
Configure a custom domain name for your Amazon MSK cluster enabled with IAM authentication
Oct 10
2025
2025
Set up custom domains in Amazon Connect hosted with M365 Exchange Online or Google Workspace
Aug 29
2025
2025
Set up custom domain names for Amazon Bedrock AgentCore Runtime agents
Nov 7
2025
2025
Amazon VPC Lattice now supports custom domain names for resource configurations
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.