Overview

Snaplex nodes can cache Pipelines for up to two hours when communication with the control plane is unavailable. Although Snaplex nodes communicate within a Snaplex, Snaplexes do not directly communicate with each other, regardless of whether the Snaplex is managed by SnapLogic (Cloudplexes) or self-managed (Groundplexes). Because Snaplexes only communicate through the control plane, understanding the dependencies between the control plane and a Groundplex is helpful for implementation planning, pipeline design considerations, and troubleshooting. Pipelines can process documents for a while even if the node cannot communicate with the control plane.

Recommendations

To build pipelines that reduce dependency on the control plane:

...

1. Processing documents through an Ultra pipeline task, which is already running, using the Low-latency Feed (Request and Response) design.

2. Pipelines, which are already started, either a standard mode pipeline or an Ultra pipeline task using the Always-On (Continuous Data Flow) design.

Secure Connectivity

All account credentials are stored in an AWS S3 bucket and encrypted with RSA encryption using key sizes of 4096 bits. Pipeline details are confidential and stored in Mongo DB. Sensitive mappings should be put in an expression library which will be stored encrypted on S3. MongoDB respects firewall rules, and only authorized users can connect to it.

Snaplogic does not store or persist customer data. Metadata is secured at the network, Org level, and DB authorization and access controls. Data is isolated to the customer instance, and metadata is logically separated in the database. The Control Plane does not initiate contact with the Groundplex. MongoDB access is further restricted to service accounts within the application.

...

1. .

Dependencies between Groundplex and Control Plane

...