-
Notifications
You must be signed in to change notification settings - Fork 379
IP Allowlisting GA [DOC-986] #6892
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 3 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -121,9 +121,9 @@ To add a Destination: | |
|
||
[Learn more](/docs/connections/destinations/add-destination/) about what adding a destination entails. | ||
> note "Disabled destinations do not receive data" | ||
> 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. | ||
> 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. | ||
> | ||
> 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. | ||
> 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. | ||
|
||
## Data deliverability | ||
|
||
|
@@ -207,6 +207,29 @@ The following destinations support bulk batching: | |
> info "You must manually configure bulk batches for Actions destinations" | ||
> To support bulk batching for the Actions Webhook destination, you must set `enable-batching: true` and `batch_size: >= 1000`. | ||
|
||
### IP Allowlist | ||
## IP Allowlisting | ||
|
||
{% include content/ip-allowlist.md %} | ||
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. | ||
|
||
IP Allowlisting is available for customers on Business Tier plans. | ||
|
||
> info "" | ||
> Segment might add additional IP address ranges. Before adding additional ranges, Segment will send an email to all Workspace Owners notifying them of the update. | ||
|
||
### Supported destinations | ||
Segment supports IP Allowlisting in all Classic and Actions destinations except for the following: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Classic and Actions destinations as these are internal names for categorization, so customers likely may not understand this. Couple of suggestions to resolve (pls feel free to ignore if there are more elegant solutions)
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll go with the first option! Good callout, thanks! |
||
- [LiveRamp](/docs/connections/destinations/catalog/actions-liveramp-audiences/) | ||
- [TradeDesk](/docs/connections/destinations/catalog/actions-the-trade-desk-crm/) | ||
- [Amazon Kinesis](/docs/connections/destinations/catalog/amazon-kinesis/) | ||
- [Destination Functions](/docs/connections/functions/destination-functions/) | ||
|
||
Destinations that are not supported receive traffic from randomly assigned IP addresses. | ||
|
||
### Configure IP Allowlisting | ||
To enable IP Allowlisting for your workspace: | ||
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”}**. | ||
2. On the Destination IP settings page, click **Enable IP allowlisting**. | ||
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. | ||
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. | ||
|
||
*IP restriction might not be supported in all destinations.* |
Uh oh!
There was an error while loading. Please reload this page.