|
| 1 | +--- |
| 2 | +icon: aky-zilla-plus |
| 3 | +description: Securely access your Kafka cluster via the intranet. |
| 4 | +--- |
| 5 | + |
| 6 | +# Secure Private Access |
| 7 | + |
| 8 | +[Available in <ZillaPlus/>](https://www.aklivity.io/products/zilla-plus) |
| 9 | +{.zilla-plus-badge .hint-container .info} |
| 10 | + |
| 11 | +The [<ZillaPlus/> Secure Private Access for Amazon MSK](https://aws.amazon.com/marketplace/pp/prodview-jshnzslazfm44) enables authorized Kafka clients deployed across **cross-account VPCs** to securely connect, publish messages, and subscribe to topics in your Amazon MSK Serverless cluster. |
| 12 | + |
| 13 | +This setup establishes a fully private, secure, and scalable communication channel between Kafka clients and the Amazon MSK cluster by leveraging **<ZillaPlus/>** proxy. |
| 14 | + |
| 15 | +**<ZillaPlus/>:** An auto-scaling, stateless proxy layer deployed in a private VPC that handles authentication and routing of Kafka requests. |
| 16 | + |
| 17 | + |
| 18 | + |
| 19 | +## Key Features |
| 20 | + |
| 21 | +- Seamless MSK Serverless Connectivity across **Cross-Account VPCs**. |
| 22 | +- **Custom Wildcard DNS** & Route 53 Hosted Zone Integration. |
| 23 | +- **Unified Domain Name** for Kafka clients, streamlining configuration. |
| 24 | +- **Eliminates** the need to **manually whitelist** each bootstrap endpoint to enable access. |
| 25 | +- Seamless end-to-end **TLS** handshake. |
| 26 | +- **Auto-Scaling** <ZillaPlus/> Instances. |
| 27 | +- Deployed behind a **Network Load Balancer** for high availability and efficient request routing. |
| 28 | +- Integrates with **AWS Nitro Enclaves**, enabling automated certificate renewal. |
| 29 | + |
| 30 | +### Many-to-One Private Access |
| 31 | + |
| 32 | +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. |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | +### One-to-Many Private Access |
| 37 | + |
| 38 | +Enables Kafka clients to securely access multiple Amazon MSK Serverless clusters deployed across different VPCs. |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | +You will need to choose a wildcard DNS pattern to use for intranet access to the brokers in your Kafka cluster. These wildcard DNS names must resolve to the IP address of the VPC Endpoint in the client VPC, which then routes traffic via the VPC Endpoint Service to the ZillaPlus Network Load Balancer (NLB). |
| 43 | + |
| 44 | +Additionally, the <ZillaPlus/> proxy must also be configured with a TLS server certificate representing the same wildcard DNS pattern. |
| 45 | + |
| 46 | +## Deploy with CDK |
| 47 | + |
| 48 | +Follow the [Secure Private Access with CDK](https://github.com/aklivity/zilla-plus-aws-templates/tree/main/amazon-msk/cdk/secure-private-access) guide to generate or deploy a custom AWS CDK stack. |
0 commit comments