In this article
...
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 Snaplex 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.
...
| Info |
|---|
To allow access to S3, update your allowlist to include all the IP 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
...
Domains | IP Addresses to be allowed by your network |
|---|---|
|
|
cdn.emea.snaplogic.com |
|
|
Outbound Requests from SnapLogic Control Plane
...