Amazon MSK simplifies configuring custom domain names
Big Data Blog
Amazon MSK now simplifies configuring custom domain names for Kafka clusters using a single cluster-wide property instead of manual per-broker CLI overrides.
- Replace manual advertised listener overrides with a single custom.advertised.listeners configuration property
- Works on both ZooKeeper and KRaft mode clusters, eliminating previous KRaft limitations
- Automatically applies configuration across all brokers during scaling and broker replacement
- Enables static customer-controlled endpoints for NLB routing, cluster migrations, and disaster recovery
- Includes validation to prevent typos and configuration errors that could cause outages
- Requires prerequisite networking layer with NLB, DNS, and TLS certificates already in place
Custom domain names now integrate seamlessly into infrastructure-as-code workflows while maintaining full reversibility and automatic application during cluster operations.
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
Aug 17
2026
2026
Amazon MSK now supports configuring custom domain names for MSK Provisioned clusters
Jun 24
2024
2024
Configure a custom domain name for your Amazon MSK cluster
Apr 21
2026
2026
Configure a custom domain name for your Amazon MSK cluster enabled with IAM authentication
Aug 6
2026
2026
Amazon MSK now delivers Kafka Authorizer Logs to customers
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.