-
Notifications
You must be signed in to change notification settings - Fork 989
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
clarify ssh tunnel dbt connection error #4913
Conversation
this pr clarifies the ssh tunnel connection error. previously it was wordy and hard to read. this was per feedback from a user: https://dbt-labs.slack.com/archives/C067EUS2D7S/p1704912493484739
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
<detailsToggle alt_header="Database Error - could not connect to server: Connection timed out"> | ||
When setting up a database connection using an SSH tunnel, you typically need these parts: | ||
|
||
- A Load Balancer (like ELB or NLB) to manage traffic. |
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.
I think this may be better served keeping the initialisms spelled out first.
website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md
Outdated
Show resolved
Hide resolved
website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md
Outdated
Show resolved
Hide resolved
website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md
Outdated
Show resolved
Hide resolved
website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md
Outdated
Show resolved
Hide resolved
website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md
Outdated
Show resolved
Hide resolved
website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md
Outdated
Show resolved
Hide resolved
|
||
Bastion hosts might have additional SSH settings to disconnect inactive clients after several checks without a response. By default, it checks three times. | ||
|
||
To prevent premature disconnections, you can adjust the settings on the bastion host: |
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 these are recommended settings, we should state that, otherwise leave it a little more open ended for customers to configure what's right for them
website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md
Outdated
Show resolved
Hide resolved
website/docs/docs/cloud/connect-data-platform/connect-redshift-postgresql-alloydb.md
Outdated
Show resolved
Hide resolved
…-postgresql-alloydb.md Co-authored-by: Matt Shaver <[email protected]>
…-postgresql-alloydb.md Co-authored-by: Matt Shaver <[email protected]>
…-postgresql-alloydb.md Co-authored-by: Matt Shaver <[email protected]>
…-postgresql-alloydb.md Co-authored-by: Matt Shaver <[email protected]>
…-postgresql-alloydb.md Co-authored-by: Matt Shaver <[email protected]>
…-postgresql-alloydb.md Co-authored-by: Matt Shaver <[email protected]>
…-postgresql-alloydb.md Co-authored-by: Matt Shaver <[email protected]>
…-postgresql-alloydb.md Co-authored-by: Matt Shaver <[email protected]>
this pr clarifies the ssh tunnel connection error. previously it was wordy and hard to read. this was per feedback from a user: https://dbt-labs.slack.com/archives/C067EUS2D7S/p1704912493484739