In this article
...
Ensure that there is a reliable connection to the 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.
For Cloudplex IP addresses outside the US region, you can use either the Snaplex Monitoring API request for REST clients or the Health tab in the SnapLogic Dashboard (as shown in the following image) to retrieve the External IP address. Learn more about
...
| Info |
|---|
To allow access to S3, update your allowlist to to include all the IP address for your region. For example, for us-east-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 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 |
...