Skip to content
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

Update aws-gslb-proxy-peering-ha-deployment.mdx #48916

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

WilliamLoy
Copy link
Contributor

Several customers have been confused by the restrictive language stating that an NLB is required. This was true when the guide was first written but is no longer the case. I've added language that indicates that using an AWS ALB is an option.

Several customers have been confused by the restrictive language stating that an NLB is required. This was true when the guide was first written but is no longer the case. I've added language that indicates that using an AWS ALB is an option.
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-48916.d3pp5qlev8mo18.amplifyapp.com

Copy link
Contributor

@ptgott ptgott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, assuming Zac's feedback is addressed

Copy link

🤖 Vercel preview here: https://docs-4c5sk5bjd-goteleport.vercel.app/docs/ver/preview

…proxy-peering-ha-deployment.mdx

Co-authored-by: Zac Bergquist <zac.bergquist@goteleport.com>
@WilliamLoy
Copy link
Contributor Author

@zmb3 I believe the use of ALB with multiplexing was enabled as far back as v13 so should this be backported all the way back to that version?

Copy link

🤖 Vercel preview here: https://docs-5h8nu64m0-goteleport.vercel.app/docs/ver/preview

@zmb3
Copy link
Collaborator

zmb3 commented Nov 13, 2024

@zmb3 I believe the use of ALB with multiplexing was enabled as far back as v13 so should this be backported all the way back to that version?

No, the v13 docs aren't published to goteleport.com anymore (and the v14 docs will be removed very soon)

@public-teleport-github-review-bot public-teleport-github-review-bot bot removed the request for review from xinding33 November 13, 2024 18:30
@WilliamLoy WilliamLoy added the no-changelog Indicates that a PR does not require a changelog entry label Nov 13, 2024
Copy link

🤖 Vercel preview here: https://docs-9mduc5a50-goteleport.vercel.app/docs/ver/preview

Copy link

🤖 Vercel preview here: https://docs-cv0ox4bf7-goteleport.vercel.app/docs/ver/preview

Copy link

github-actions bot commented Mar 12, 2025

Amplify deployment status

Branch Commit Job ID Status Preview Updated (UTC)
will/gslb-alb-update HEAD 1 ✅SUCCEED will-gslb-alb-update 2025-03-12 14:31:48

@hugoShaka
Copy link
Contributor

Do we want users to prefer NLBs when possible? Going through ALBs is done via the upgrade-to-mTLS-in-websocket and adds an encapsulation level, causing the handshakes to be slower and more expensive.

This matters in bad connectivity/high latency scenarios (e.g. connecting to a cluster located in a distant region).

@WilliamLoy
Copy link
Contributor Author

@hugoShaka NLB is implicitly the preference by using it for the example. The issue I'm trying to solve is there have been several customers opening support cases or spending time trying to figure out how to satisfy the NLB requirement even though ALB is now an option for this setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants