docs: secure private access #285
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jfallows
requested changes
Feb 11, 2025
jfallows
requested changes
Feb 12, 2025
| ::: info | ||
| Aklivity recommend using the format `*.<region>.<custom-domain>` for your custom wildcard DNS domain. This removes the need for additional client configuration, as the MSK Serverless cluster region can be directly inferred from the custom domain itself. | ||
| ::: | ||
| Multiple Kafka clients from 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. |
There was a problem hiding this comment.
Suggested change
| Multiple Kafka clients from 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. |
| Follow the [Secure Private Access with Terraform](https://github.com/aklivity/zilla-plus-aws-templates/tree/main/amazon-msk/cdktf/secure-private-access) guide to generated or deploy a custom Terraform template using [CDKTF](https://developer.hashicorp.com/terraform/cdktf). This Terraform script can be configured to deploy `SASL/SCRAM authentication`, `Mutual TLS (mTLS) authentication` or `Unauthorized access` to setup connectivity to your MSK Serverless cluster with a wildcard DNS pattern. | ||
| ### One-to-Many Private Access | ||
|
|
||
| Enables Kafka client to securely access multiple Amazon MSK Serverless clusters deployed across different VPCs. |
There was a problem hiding this comment.
Suggested change
| Enables Kafka client to securely access multiple Amazon MSK Serverless clusters deployed across different VPCs. | |
| Enables Kafka clients to securely access multiple Amazon MSK Serverless clusters deployed across different VPCs. |
|
|
||
| ## Deploy with CDK | ||
|
|
||
| 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 generated or deploy a custom AWS CDK stack. This CDK-based deployment supports `SASL/SCRAM authentication`, `Mutual TLS (mTLS) authentication` or `Unauthorized access` to setup connectivity to your MSK Serverless cluster with a wildcard DNS pattern. |
There was a problem hiding this comment.
Suggested change
| 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 generated or deploy a custom AWS CDK stack. This CDK-based deployment supports `SASL/SCRAM authentication`, `Mutual TLS (mTLS) authentication` or `Unauthorized access` to setup connectivity to your MSK Serverless cluster with a wildcard DNS pattern. | |
| 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. |
Only IAM authorization is relevant for MSK Serverless clusters, there are no choices like MSK Provisioned clusters.
src/.vuepress/public/one_to_many.png
Outdated
There was a problem hiding this comment.
This many-to-one scenario requires a different VPC Endpoint for each VPC Endpoint Service, so in this case the Kafka client VPC would have 3 VPC Endpoints, each one leading to a different Zilla Plus NLB.
There was a problem hiding this comment.
The label VPC Endpoint Service should be VPC Endpoint (in both diagrams).
jfallows
requested changes
Feb 13, 2025
src/.vuepress/public/one_to_many.png
Outdated
There was a problem hiding this comment.
The label VPC Endpoint Service should be VPC Endpoint (in both diagrams).
jfallows
approved these changes
Feb 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.