Amazon MSK now supports configuring custom domain names for MSK Provisioned clusters
Amazon MSK now allows configuring custom domain names for Provisioned clusters, including KRaft mode, simplifying endpoint management across migrations, failovers, and scaling without reconfiguration.
Amazon MSK Provisioned clusters now support configuring custom domain names for both ZooKeeper and KRaft metadata modes. Previously, customers had to manually set these domains on each broker, a process that was time-consuming and error-prone. The new feature enables a single domain configuration at the cluster level, automatically applied to all brokers, streamlining setup and maintenance. This change applies to all new and existing clusters in supported AWS Regions at no extra cost.
The update eliminates the need for individual broker configurations, reducing operational overhead during scaling, migrations, or disaster recovery scenarios. Custom domains persist through cluster operations, ensuring consistent endpoints for client applications. This is particularly beneficial for users relying on Network Load Balancers or those enforcing strict naming conventions for security and compliance purposes.
Previously, KRaft-based clusters could not use custom domain names, limiting flexibility in metadata management. The new capability extends support to KRaft mode, aligning ZooKeeper and KRaft configurations. Customers can now standardize their domain naming across all cluster types without additional configuration steps.
To implement custom domains, users can refer to the Amazon MSK Developer Guide for detailed instructions. The feature is available immediately in all AWS Regions where Amazon MSK Provisioned operates, with no additional charges. This enhancement aims to simplify cluster management while maintaining compatibility with existing workflows.