Multi-VPC private connectivity is now supported for Amazon MSK clusters configured with any authentication mechanism

Amazon Managed Streaming for Apache Kafka (MSK) now allows you to set up multi-VPC and cross-account private connectivity on Amazon MSK clusters configured with any of the MSK supported authentication mechanisms.

Multi-VPC private connectivity (powered by AWS PrivateLink) allows you to easily establish cross-VPC and cross-account connectivity between your Apache Kafka clients and your Amazon MSK cluster, while keeping all traffic within the AWS Network. With a few clicks, you can turn on multi-VPC private connectivity for one or more authentication modes on your cluster. This feature was previously supported only on clusters with client authentication enabled. With this launch, we have extended the multi-VPC functionality for Amazon MSK clusters that do not use client authentication. Your clients that do not use authentication can continue to do so while you can configure multi-VPC connectivity for other clients that have configured authentication.

To learn how to get started with multi-VPC private connectivity, visit our blog and the Amazon MSK Developer Guide.