Skip to content

Commit 164312a

Browse files
najeebcfkodster28
authored andcommitted
Update splunk-integration-guide.mdx (#21328)
* Update splunk-integration-guide.mdx Updating content with egress IP Address reference. Related to https://jira.cfdata.org/browse/CUSTESC-50151 * Update src/content/docs/email-security/reporting/siem-integration/splunk-integration-guide.mdx --------- Co-authored-by: Kody Jackson <[email protected]>
1 parent 72160d3 commit 164312a

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

src/content/docs/email-security/reporting/siem-integration/splunk-integration-guide.mdx

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -74,12 +74,8 @@ When creating requests to Splunk, the URL and port number change according to th
7474

7575
Refer to the [Splunk documentation](https://docs.splunk.com/Documentation/Splunk/8.2.2/Data/UsetheHTTPEventCollector) for more information.
7676

77-
If your instance is on-premise, specify the appropriate hostname and ensure that your firewall allows the configured port through to your instance. The connections will be coming from the following egress IP addresses, if you need them for your access control lists (ACLs):
77+
If your instance is on-premise, specify the appropriate hostname and ensure that your firewall allows the configured port through to your instance. The connections will be coming from this [Egress IP addresses](/email-security/deployment/inline/reference/egress-ips/), if you need them for your access control lists (ACLs)
7878

79-
* `52.11.209.211`
80-
* `52.89.255.11`
81-
* `52.0.67.109`
82-
* `54.173.50.115`
8379

8480
:::note
8581
Ensure that you have a valid SSL certificate configured on your instance. The certificate cannot be expired and cannot be a self-signed certificate.

0 commit comments

Comments
 (0)