Seamlessly establish a custom domain to connect Apache Kafka® clients to Amazon MSK Serverless clusters via IAM authentication over AWS PrivateLink.
Amazon MSK serverless brokers are not sequentially numbered, which inhibits setting up a specific DNS record for each serverless broker. As a result, to expose these brokers to clients running in external VPCs or AWS accounts requires manually configuring 1000s of individual broker DNS records.
Organize workloads in separate accounts, and group accounts based on function, compliance requirements, or a common set of controls.
Provide secure cross-account VPC connectivity between Kafka clients and Amazon MSK clusters.
Zilla Plus enables Kafka clients to use a custom domain name to securely connect to your MSK Serverless clusters via IAM authentication over AWS PrivateLink, from as many different AWS accounts or VPCs as needed. It achieves this by overriding the format of the broker bootstrap server names, to make them compatible with wildcard DNS resolution
Existing approaches for cross-VPC connectivity to MSK clusters have limitations.
This setup establishes a fully private, secure, and scalable communication channel between Kafka clients and the Amazon MSK cluster by leveraging Zilla proxy.
Multiple Kafka clients from different cross-account VPCs securely connect to a single Amazon MSK Serverless cluster. This approach simplifies multi-tenant access and ensures a unified, private connectivity model.
Multiple Kafka clients from different cross-account VPCs securely connect to a single Amazon MSK Serverless cluster. This approach simplifies multi-tenant access and ensures a unified, private connectivity model.
