JA EN
shiichan

Amazon MSK now supports cluster-wide custom domain names, and KRaft clusters finally get it too!

AWS What's New ★★★★ View Markdown
#aws#infrastructure#devops

Hi, it's Shii! I've got an update today for everyone running Amazon MSK. That broker-by-broker configuration work you used to do? It just got a lot simpler!

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, Amazon MSK Provisioned clusters now let you easily configure a custom domain name at the cluster level. This works on either ZooKeeper or KRaft mode for metadata management.

With this, client applications can keep using the same connection endpoints, which means you don't have to reconfigure anything during cluster migrations, disaster recovery failovers, or scaling operations.

The story so far

Until now, if you wanted a custom domain name, you had to configure it manually on each broker. And on KRaft-based clusters, configuring a custom domain name wasn't even possible.

For clusters with a lot of brokers, that manual, broker-by-broker setup was a real hassle.

What changes

With this update, you can define a custom domain once at the cluster level, and Amazon MSK automatically applies it to every broker in the cluster. No more configuring each broker individually.

This is especially useful if you:

  • Route traffic through a Network Load Balancer
  • Need persistent connection endpoints across cluster operations
  • Have to follow organizational naming conventions for security and compliance

Dive Deep

Here are the technical details worth knowing:

  • It works identically on both ZooKeeper and KRaft-based clusters
  • The configuration persists through scaling operations
  • You can use it on both new and existing MSK Provisioned clusters
  • It's available in every AWS Region where Amazon MSK Provisioned is available
  • There's no additional cost to use it

If you want the full configuration details, check out the Amazon MSK Developer Guide.

Wrap-up

  • Amazon MSK Provisioned clusters can now have a custom domain name configured once at the cluster level and applied to all brokers automatically
  • Previously this required per-broker manual setup, and KRaft clusters weren't supported at all
  • The setting persists through scaling operations
  • Works on both ZooKeeper and KRaft, on new or existing clusters, at no additional cost

If you're routing traffic through an NLB or you're an infrastructure engineer who wants a stable connection endpoint across migrations and DR failovers, this update is worth a look!

Related posts