In this article
...
If your network restricts outbound communication, you need to add the SnapLogic IP addresses described on this page to your network allowlist. To restrict inbound requests to the SnapLogic Platform, refer to Task allowlists and the Groundplex allowlist and the information on how to configure them in Admin Manager.
...
Ensure that there is a reliable connection to the Amazon S3 services as JCC:
Downloads the WAR files directly from S3 but falls back to SLDB in case of failure, which may introduce some latency.
Uploads large log files directly to S3, provided JCC can access S3.
Ensure your AWS (Amazon Web Services) S3 instance can access Snaplexes after every JCC start-up. In case of any accessibility issues, all necessary communication occurs through the Control Plane services.
We strongly recommend enabling S3 access on JCC (data processing) and FeedMaster nodes. If Snaplex outbound access to S3 is blocked:
FileReader/FileWriter Snaps that Read/Write to Snaplogic filesystem (
sldb) via the Files asset type will not work.Snaplex WAR files will continue to work, but the download will fall back to the Snaplogic Control Plane and might introduce some latency.
For Cloudplex IP addresses outside the US region, you can use either the Snaplex Monitoring API request for REST clients /wiki/spaces/DRWIP/pages/2892791821 or the Health tab in the SnapLogic Dashboard (as shown in the following image) to retrieve the External IP address. Learn more about
...
.
The Dashboard is being replaced with Monitor. We encourage you to start using Monitor for monitoring and reporting requirements. Contact support@snaplogic.com if you need assistance.
...
| Info |
|---|
To allow access to S3, update your allowlist to to include all the IP address addresses for your region. For example, for us-eastwest-1, select all the CIDR blocks as per the official AWS documentation. Learn more about AWS IP address ranges and steps to filter the JSON files at AWS IP address ranges. |
...
SnapLogic Environment | Domain | IP Addresses to be allowed by your network | |
|---|---|---|---|
Production - Global |
|
| |
Production - EMEA |
|
| |
UAT |
|
| |
UAT - Global |
|
| |
UAT - EMEA |
| ||
UAT - EMEA |
|
|
Request from Cloudplexes to Snap Endpoints
You must add the following IP addresses to your Allowlist on Snap endpoints (like AWS Redshift) to allow requests from SnapLogic Cloudplexes. Here is an example of how to add IP addresses on AWS Redshift.
SnapLogic Environment | Domain | IP Addresses to be allowed by your endpoint for U.S. Cloudplexes | Ireland Cloudplexes | London Cloudplexes | Canada Cloudplexes | India Cloudplexes | Sydney Cloudplexes | Frankfurt Cloudplexes | Singapore Cloudplexes |
|---|---|---|---|---|---|---|---|---|---|
Production - Global | elastic.snaplogic.com |
|
|
|
|
|
|
|
(Inbound) |
Production - EMEA | emea.snaplogic.com | N/A |
| N/A | N/A | N/A | N/A | N/A | N/A |
UAT | uat.elastic.snaplogic.com |
|
| N/A | N/A | N/A | N/A | N/A | N/A |
Requests to Cloudplex API endpoints
...
SnapLogic Environment | Domain | Ireland | London | Canada | India |
|---|---|---|---|---|---|
Production - Global |
|
|
|
|
|
Production - EMEA |
|
| N/A | N/A | N/A |
UAT |
|
| N/A | N/A | N/A |
Cloudflare integration
Since , the The SnapLogic platform uses Cloudflare. The SnapLogic UI now , and the UI automatically redirects to the given Cloudflare CDN addresses. This enhances the SnapLogic platform’s response time, security, and performance. Only customers who restrict outbound IP addresses to a pre-identified list of IP addresses must extend their Allowlist to add all the given IP addresses to ensure continued access to the SnapLogic UI.
...
Domains | IP Addresses to be allowed by your network |
|---|---|
|
|
cdn.emea.snaplogic.com |
|
|
Outbound Requests from SnapLogic Control Plane
...