-
Notifications
You must be signed in to change notification settings - Fork 352
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
[FUNK-1550] IP Allowlisting Changes #7244
Conversation
8315f1d
to
0ba13e5
Compare
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
src/connections/functions/index.md
Outdated
#### IP Allowlisting for functions | ||
|
||
With IP Allowlisting, users can ensure that outbound traffic from Functions will originate only from a predefined set of IP addresses. This provides added security for external services by making it easier to recognize and allowlist trusted traffic sources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With IP Allowlisting, users can ensure that outbound traffic from Functions will originate only from a predefined set of IP addresses. This provides added security for external services by making it easier to recognize and allowlist trusted traffic sources. | |
> warning " " | |
> IP Allowlisting is only available for customers on Business Tier plans. | |
IP Allowlisting uses a NAT gateway to route outbound Functions traffic from Segment’s servers to your destinations through a limited range of IP addresses, which can prevent malicious actors from establishing TCP and UDP connections with your integrations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The warning IP Allowlisting is only available for customers on Business Tier plans
has been added as a simple text as it is being displayed as simple text in Destinations IP Allowlisting doc as well.
Ref: https://segment.com/docs/connections/destinations/#ip-allowlisting
src/connections/functions/index.md
Outdated
To learn more, visit the [Functions Copilot documentation](/docs/connections/functions/copilot/). | ||
|
||
#### IP Allowlisting for functions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#### IP Allowlisting for functions | |
#### IP Allowlisting |
src/connections/functions/index.md
Outdated
With IP Allowlisting, users can ensure that outbound traffic from Functions will originate only from a predefined set of IP addresses. This provides added security for external services by making it easier to recognize and allowlist trusted traffic sources. | ||
|
||
To learn more, visit [IP Allowlisting documentation](/docs/connections/destinations/#ip-allowlisting). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we remove the note in the Destination Overview page that mentions Destination Functions are not supported?
To learn more, visit [IP Allowlisting documentation](/docs/connections/destinations/#ip-allowlisting). | |
To learn more, visit [Segment's IP Allowlisting documentation](/docs/connections/destinations/#ip-allowlisting). |
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
https://segment.atlassian.net/browse/FUNK-1550
The changes are to handle the Functions IP Allowlisting changes made.
Merge timing
Related issues (optional)