Skip to content

Commit 4ce02f8

Browse files
Merge pull request #6892 from segmentio/DOC-986
IP Allowlisting GA [DOC-986]
2 parents 697cab7 + cf7e548 commit 4ce02f8

File tree

6 files changed

+35
-5
lines changed

6 files changed

+35
-5
lines changed

src/connections/destinations/catalog/actions-liveramp-audiences/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,9 @@ The LiveRamp Audiences destination allows users to connect their Engage Audience
1212

1313
The LiveRamp Audiences destination can be connected to **Twilio Engage sources only**.
1414

15+
> info "LiveRamp Audiences is not compatible with IP Allowlisting"
16+
> For more information, see the [IP Allowlisting](/docs/connections/destinations/#ip-allowlisting) documentation.
17+
1518
## Getting started
1619

1720
### Set up your file drop

src/connections/destinations/catalog/actions-the-trade-desk-crm/index.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,9 @@ This integration lets users link Engage audiences to The Trade Desk and transmit
1414

1515
The Trade Desk destination can only be connected to Twilio Engage sources.
1616

17+
> info "The Trade Desk CRM is not compatible with IP Allowlisting"
18+
> For more information, see the [IP Allowlisting](/docs/connections/destinations/#ip-allowlisting) documentation.
19+
1720
## Getting started
1821

1922
### Obtaining credentials from The Trade Desk

src/connections/destinations/catalog/amazon-kinesis/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@ id: 57da359580412f644ff33fb9
55
---
66
[Amazon Kinesis](https://aws.amazon.com/kinesis/){:target="_blank”} enables you to build custom applications that process or analyze streaming data for specialized needs. Amazon Kinesis Streams can continuously capture and store terabytes of data per hour from hundreds of thousands of sources such as website clickstreams, financial transactions, social media feeds, IT logs, and location-tracking events.
77

8+
> info "Amazon Kinesis is not compatible with IP Allowlisting"
9+
> For more information, see the [IP Allowlisting](/docs/connections/destinations/#ip-allowlisting) documentation.
810
911
## Getting Started
1012

src/connections/destinations/index.md

Lines changed: 24 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -121,9 +121,9 @@ To add a Destination:
121121

122122
[Learn more](/docs/connections/destinations/add-destination/) about what adding a destination entails.
123123
> note "Disabled destinations do not receive data"
124-
> If you haven't enabled your destination for the first time after you created it or if you actively disable a destination, Segment prevents any data from reaching the destination. Business Tier customers can request [a Replay]([url](https://segment.com/docs/guides/what-is-replay/)), which resends data from the time the destination was disabled to the time it was re-enabled. Replays can also send data to currently disabled destinations.
124+
> If you haven't enabled your destination for the first time after you created it or if you actively disable a destination, Segment prevents any data from reaching the destination. Business Tier customers can request [a Replay](/docs/guides/what-is-replay/), which resends data from the time the destination was disabled to the time it was re-enabled. Replays can also send data to currently disabled destinations.
125125
>
126-
> Some destinations are not compatible with Replays after a certain period of time. Check with Segment’s support team [friends@segment.com](friends@segment.com) to confirm that your intended destination allows historical timestamps.
126+
> Some destinations are not compatible with Replays after a certain period of time, for example, 14 days. Check with Segment’s support team [friends@segment.com](mailto:friends@segment.com) to confirm that your intended destination allows historical timestamps.
127127
128128
## Data deliverability
129129

@@ -207,6 +207,26 @@ The following destinations support bulk batching:
207207
> info "You must manually configure bulk batches for Actions destinations"
208208
> To support bulk batching for the Actions Webhook destination, you must set `enable-batching: true` and `batch_size: >= 1000`.
209209
210-
### IP Allowlist
210+
## IP Allowlisting
211211

212-
{% include content/ip-allowlist.md %}
212+
IP Allowlisting uses a NAT gateway to route traffic from Segment's servers to your destination through a limited range of IP addresses, which can prevent malicious actors from establishing TCP and UDP connections with your integrations.
213+
214+
IP Allowlisting is available for customers on Business Tier plans.
215+
216+
### Supported destinations
217+
Segment supports IP Allowlisting in [all destinations](/docs/connections/destinations/catalog/) except for the following:
218+
- [LiveRamp](/docs/connections/destinations/catalog/actions-liveramp-audiences/)
219+
- [TradeDesk](/docs/connections/destinations/catalog/actions-the-trade-desk-crm/)
220+
- [Amazon Kinesis](/docs/connections/destinations/catalog/amazon-kinesis/)
221+
- [Destination Functions](/docs/connections/functions/destination-functions/)
222+
223+
Destinations that are not supported receive traffic from randomly assigned IP addresses.
224+
225+
### Configure IP Allowlisting
226+
To enable IP Allowlisting for your workspace:
227+
1. From your Segment workspace, navigate to **[Settings > Workspace settings > Destination IP settings](https://app.segment.com/goto-my-workspace/settings/destination-ip-settings){:target="_blank”}**.
228+
2. On the Destination IP settings page, click **Enable IP allowlisting**.
229+
3. The page displays the IP address ranges that Segment uses to route data from Segment's internal systems to your destination. Note these ranges, as you'll need this information to enforce IP restriction in your downstream destinations.
230+
4. Open each of your downstream tools and configure IP restriction for each destination. For more information, refer to the documentation for your downstream tool.
231+
232+
*IP restriction might not be supported in all destinations.*

src/connections/functions/destination-functions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ All functions are scoped to your workspace, so members of other workspaces can't
1717

1818

1919
> note ""
20-
> Destination functions doesn't accept data from [Object Cloud sources](/docs/connections/sources/#object-cloud-sources).
20+
> Destination functions doesn't accept data from [Object Cloud sources](/docs/connections/sources/#object-cloud-sources). Destination functions don't support [IP Allowlisting](/docs/connections/destinations/#ip-allowlisting).
2121
2222
## Create a destination function
2323

src/connections/functions/insert-functions.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ Use Destination Insert Functions to enrich, transform, or filter your data befor
1313

1414
**Customize filtration for your destinations**: Create custom logic with nested if-else statements, regex, custom business rules, and more to filter event data.
1515

16+
> info "Destination Insert Functions are not compatible with IP Allowlisting"
17+
> For more information, see the [IP Allowlisting](/docs/connections/destinations/#ip-allowlisting) documentation.
1618
1719
## Create destination insert functions
1820

0 commit comments

Comments
 (0)