Multi-VPC private connectivity is now supported for Amazon MSK clusters configured with any authentication mechanism
News
This announcement from Amazon Web Services (AWS) highlights the support for multi-VPC private connectivity for Amazon Managed Streaming for Apache Kafka (MSK) clusters, regardless of the authentication mechanism used.
Specifically, the article covers:
- Multi-VPC private connectivity allows establishing cross-VPC and cross-account connectivity between Apache Kafka clients and Amazon MSK clusters while keeping traffic within the AWS Network.
- This feature was previously supported only for clusters with client authentication enabled, but now it's available for any authentication mechanism supported by MSK.
- Clients without authentication can continue to operate as-is, while other clients with configured authentication can leverage multi-VPC connectivity.
- The blog and documentation links provided offer guidance on setting up multi-VPC private connectivity for Amazon MSK clusters.
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
Feb 17
2026
2026
Amazon MSK now supports dual-stack (IPv4 and IPv6) connectivity for existing clusters
Oct 1
2024
2024
Amazon MSK APIs now supports AWS PrivateLink
Sep 10
2024
2024
Amazon MSK enhances cross-cluster replication with support for identical topic names
Jun 19
2025
2025
Secure access to a cross-account Amazon MSK cluster from Amazon MSK Connect using IAM authentication
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.