Redshift Destination implement SSH tunneling #12131
Assignees
Labels
Comments
24 tasks
grishick
changed the title
jcowanpdx
added a commit
that referenced
this issue
Feb 27, 2023
Issue: #12131 User would like to be able to access their Redshift Destination database via an SSH Tunnelling config (SSH Bastion Host), just as in Postgres, etc. destinations. Acceptance tests pass and exercise both Insert and S3 type loading options as well as password and key based authentication with the SSH bastion host. Airbyters: Credentials/configs for acceptance testing against AWS Redshift are updated in Google Cloud Secret Manager. Be sure to get both the config.json and config_staging.json as well as the new PEM file
37 tasks
37 tasks
jcowanpdx
added a commit
that referenced
this issue
Feb 28, 2023
Issue: #12131 User would like to be able to access their Redshift Destination database via an SSH Tunnelling config (SSH Bastion Host), just as in Postgres, etc. destinations. Acceptance tests pass and exercise both Insert and S3 type loading options as well as password and key based authentication with the SSH bastion host. Airbyters: Credentials/configs for acceptance testing against AWS Redshift are updated in Google Cloud Secret Manager. Be sure to get both the config.json and config_staging.json as well as the new PEM file
jcowanpdx
added a commit
that referenced
this issue
Mar 7, 2023
* Redshift Destination: Add SSH Tunnelling Config Option Issue: #12131 User would like to be able to access their Redshift Destination database via an SSH Tunnelling config (SSH Bastion Host), just as in Postgres, etc. destinations. Acceptance tests pass and exercise both Insert and S3 type loading options as well as password and key based authentication with the SSH bastion host. Airbyters: Credentials/configs for acceptance testing against AWS Redshift are updated in Google Cloud Secret Manager. Be sure to get both the config.json and config_staging.json as well as the new PEM file * README.md updates ** Move the pem info into the secrets config files ** Update the version id to 0.4.0 ** Touch up the docs ** adding a note about S3 staging NOT using the SSH Tunnel configuration, if provided. ** make base class abstract to prevent double running the same tests Co-authored-by: Octavia Squidington III <[email protected]>
danielduckworth
pushed a commit
to danielduckworth/airbyte
that referenced
this issue
Mar 13, 2023
* Redshift Destination: Add SSH Tunnelling Config Option Issue: airbytehq#12131 User would like to be able to access their Redshift Destination database via an SSH Tunnelling config (SSH Bastion Host), just as in Postgres, etc. destinations. Acceptance tests pass and exercise both Insert and S3 type loading options as well as password and key based authentication with the SSH bastion host. Airbyters: Credentials/configs for acceptance testing against AWS Redshift are updated in Google Cloud Secret Manager. Be sure to get both the config.json and config_staging.json as well as the new PEM file * README.md updates ** Move the pem info into the secrets config files ** Update the version id to 0.4.0 ** Touch up the docs ** adding a note about S3 staging NOT using the SSH Tunnel configuration, if provided. ** make base class abstract to prevent double running the same tests Co-authored-by: Octavia Squidington III <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add SSH tunneling to Redshift Destination
The text was updated successfully, but these errors were encountered: