Commit507bdc5

authored

Update faq.md

Gave clarity to IP ranges and suggested customers use IP addresses

1 parenteaf0a3f commit507bdc5Copy full SHA for 507bdc5

File tree

-2

lines changed

-2

lines changed

Lines changed: 3 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -97,9 +97,10 @@ Segment recommends scripting any sort of additions of data you might have to war`
`97`	`97`
`98`	`98`	`{% include content/warehouse-ip.html %}`
`99`	`99`
`100`		-You must allowlist Segment's custom IPs`52.25.130.38/32` and`34.223.203.0/28` while authorizing Segment to write in to your Redshiftor Postgresport.
	`100`	+You must allowlist Segment's custom IPs`52.25.130.38/32` and`34.223.203.0/28` while authorizing Segment to write in to yourwarehouse port. Currently,Redshiftand Postgresare the only connectors that require configuing an IP upon set-up. However, we recommend enabling IP allowlists for added security if they are not already being used.
`101`	`101`
`102`		-EU workspace regions are currently in beta. If you're in the EU region and participating in the public beta program, use CIDR`3.251.148.96/29`. To learn more about the public beta for EU workspace locations, contact your account manager.
	`102`	`+`
	`103`	+If you're in the EU region, use CIDR`3.251.148.96/29`. To learn more about EU workspace locations, contact your account manager.
`103`	`104`
`104`	`105`
`105`	`106`	`##Will Segment sync my historical data?`

Comments

(0)