-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc: add clarification for cross-region PL #31018
base: main
Are you sure you want to change the base?
Doc: add clarification for cross-region PL #31018
Conversation
**Availability Zone Selection**: | ||
|
||
* For in-region connections, the AZs **must match** between the NLB and the consumer VPC. | ||
* For cross-region connections, AZ alignment is not required. You can choose any AZs in your consumer VPC. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this is because cross zone balancing is a pre-req of cross region connections?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I read their docs correctly, this seems to be the case for providers (in our case customers):
Providers must use a minimum of two AZs to anchor the AWS Network Load Balancer (NLB) in the service region. Consumers can choose to create the Interface endpoint in as many AZs as required, although two or more AZs are recommended for high availability. This enables PrivateLink to dynamically weigh away traffic to a healthy AZ, transparent to the provider and consumer, in case of AZ impairment events in either region.
Thank you, @bobbyiliev! Noticed we were missing PrivateLink documentation for MySQL in a bunch of places and had some innaccuracies from copy-pasting in others, so taking the chance to push a patch for all that. 🚀 |
cff0381
to
2069bd5
Compare
* For **cross-region connections**, availability zone alignment is not | ||
required. You can choose any availability zones in your consumer VPC. Due |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* For **cross-region connections**, availability zone alignment is not | |
required. You can choose any availability zones in your consumer VPC. Due | |
* For **cross-region connections**, you can select any availability zones in your current | |
Materialize region. For more details, refer to the [AWS blog on cross-region PrivateLink](https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-cross-region-connectivity-for-aws-privatelink). Due |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me know what you think about the wording here @jubrad!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good
Motivation
Depends on: https://github.com/MaterializeInc/cloud/pull/10617 once it is merged we can update the documentation as well.
The AWS official documentation for releasing cross-region PrivateLink connections: