Skip to content

Conversation

@aroder
Copy link

@aroder aroder commented Jun 18, 2020

Support a jump server for cases when Redshift is behind a firewall and not exposed to the internet

@awm33
Copy link
Member

awm33 commented Jun 19, 2020

Hi @aroder , thanks for interest in contributing.

I think that:

  1. Setting up SSH / VPN / networking seems out of scope for a particular target and more like something that a bash script should be doing. A large number of taps and targets (pretty much and db or API that can be run on-prem) could use SSH tunneling.
  2. If we were to add it, I would be more inclined to add it to target-postgres's target_tools.py which is used by target-redshift and target-snowflake.

@awm33
Copy link
Member

awm33 commented Jun 19, 2020

CC @AlexanderMann

@AlexanderMann
Copy link
Collaborator

@awm33 is there any movement here or anything to be done here?

@chriskl
Copy link

chriskl commented Mar 24, 2021

I suggest adding support for redshift's data api which is vastly superior than tunneling anyway

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants