AWS Route 53 GSLB Multi-Region Proxy Peering High Availability Deployment Guide#24164
Merged
AWS Route 53 GSLB Multi-Region Proxy Peering High Availability Deployment Guide#24164
Conversation
github-actions
Bot
requested review from
alexfornuto,
ptgott,
r0mant,
xinding33 and
zmb3
Contributor
Author
|
Replaces #24087 |
zmb3
reviewed
Apr 5, 2023
Collaborator
zmb3
left a comment
zmb3
left a comment
There was a problem hiding this comment.
Just a start, only got halfway through.
pschisa
added
c-cc
I applied changes based on @zmb3's feedback. I also made changes to sections that were borrowed from other guides that conflict with this guide.
rosstimothy
reviewed
Apr 6, 2023
Contributor
|
@WilliamLoy I know this is going through engineering review now, so let me know with an @ if you'd like me to give this a look for copy. I'll unsubscribe in the meantime to keep notifications low. Thanks! |
Changes based on @rosstimothy's recommendations.
dboslee
reviewed
Apr 6, 2023
…nt.mdx Co-authored-by: David Boslee <david@goteleport.com>
- corrected agent_connection_count guidance - clarified cross-zone LB guidance - added S3 and Dynamo guidance links - Updated title
Contributor
I think this makes sense, as the guide is specific to using AWS and not a general guide like the HA one |
ptgott
reviewed
May 17, 2023
Contributor
There was a problem hiding this comment.
I think all that's left is:
- Putting this in
docs/pages/deploy-a-cluster/deployments - Updating
docs/config.jsonso we have a new navigation sidebar entry - Updating
docs/pages/deploy-a-cluster/deployments.mdxanddocs/pages/deploy-a-cluster/introduction.mdxto link to this page
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
…nt.mdx to docs/pages/deploy-a-cluster/deployments/aws-gslb-proxy-peering-ha-deployment.mdx
Contributor
|
@ptgott Completed all tasks left, please let me know what you think. I did not move the image location as there was not a sub-directory for Also, do you know if we can make the linter accept |
Contributor
|
@pschisa Thanks for the edits! Going to push some tiny copy-edits and linter fixes, then approve. |
ptgott
approved these changes
May 22, 2023
public-teleport-github-review-bot
Bot
removed request for
alexfornuto,
r0mant and
xinding33
|
@WilliamLoy See the table below for backport results.
|
This was referenced May 22, 2023
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
This guide gives a high-level overview of deploying a single cluster available across multiple regions without using trusted clusters.
This architecture uses AWS Route53 Latency Routing to create Global Server Load Balancing for multi-region single cluster deployments. It also uses Proxy Peering to restrict the number of connections necessary to facilitate this Teleport Cluster architecture.