Skip to content

Commit 8154930

Browse files
authored
Add alternatives to SSH Tunneling FAQ
1 parent 7b04788 commit 8154930

File tree

1 file changed

+8
-0
lines changed
  • src/connections/storage/catalog/redshift

1 file changed

+8
-0
lines changed

src/connections/storage/catalog/redshift/index.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -150,3 +150,11 @@ Segment does not currently support SSH tunneling to Redshift. You can usually al
150150
### Do you support Redshift Serverless?
151151

152152
Segment does not currently support Serverless Redshift. While you can set up the connection in the Segment app, Segment does not have the functionality to query Redshift's SYS tables.
153+
154+
Despite the fact we need a public IP address to access your remote instance, Segment supports several layers of Redshift's security model:
155+
156+
Security group — This is the firewall that Segment asks customers to open a pinhole in for Segment's IP address. Security groups are a fundamental building block of AWS security;
157+
158+
SSL — This secures data in transit and also allows client apps like Segment to validate that the warehouse at the other end is actually a warehouse owned by AWS. This is especially important if your Redshift warehouse is not within the us-west-2 region;
159+
160+
Username /password — This is the basic method used to authenticate database users and apply varying levels of permissions like who can create tables, who can delete data, who can see which tables, etc.

0 commit comments

Comments
 (0)