Skip to content

Commit 0bae5ea

Browse files
Update src/connections/storage/catalog/redshift/index.md
Co-authored-by: forstisabella <[email protected]>
1 parent b3cec7c commit 0bae5ea

File tree

1 file changed

+4
-6
lines changed
  • src/connections/storage/catalog/redshift

1 file changed

+4
-6
lines changed

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

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -147,13 +147,11 @@ You can also unload data to a s3 bucket and then load the data into another Reds
147147

148148
Segment does not currently support SSH tunneling to Redshift. You can usually allow Segment's ETL to write to Redshift without leaving the cluster available to other connections by using IP level restrictions.
149149

150-
Despite the fact Segment needs a public IP address to access your remote instance, Segment supports several layers of Redshift's security model:
151-
152-
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.
150+
Segment supports several layers of Redshift's security model:
153151

154-
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.
155-
156-
Username /passwordThis 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.
152+
- **Security groups**: Security groups control the incoming and outgoing traffic to a resource. You can think of this like a pinhole in a firewall that only allows traffic from Segment's IP address. Security groups are a fundamental building block of AWS security.
153+
- **SSL**: This secures data in transit and allows 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 located in the `us-west-2` region.
154+
- **Username and password**: This is the basic method used to authenticate database users and apply varying levels of permissions - for example, who can create tables, who can delete data, who can see which tables.
157155

158156
### Do you support Redshift Serverless?
159157

0 commit comments

Comments
 (0)