...
| Table of Contents | ||||
|---|---|---|---|---|
|
Overview
Groundplex deployment The deployment of a Self-managed Snaplex (Groundplex) comprises many factors for consideration. Most of these considerations are because of IT requirements in your computing environment, but some also depend on Pipeline production and the types of Pipelines you plan to run in production.
| Info |
|---|
Although Groundplex and Snaplex refer to the same thing, this article uses Snaplex in general when referring to the type of Asset in SnapLogic Manager, and Groundplex in the context of the computing resources underlying itThe term Groundplex is used throughout this document to refer specifically to your self-managed Snaplex. |
Computing Requirements
The Groundplex must conform to the following minimum specifications:
...
The nodes of a Snaplex need to communicate among themselves, so it is important that each node can resolve each other's host names. This requirement is crucial when you are making local calls into the Snaplex nodes for the execution of Pipelines instead of initiating it through the SnapLogic Platform. The Pipelines are load-balanced by SnapLogic with Tasks passed to the target node.
Communication between the customer-managed Groundplex and the SnapLogic-managed S3 bucket is over HTTPS with TLS enforced by default. The AWS-provided S3 URL also uses an HTTPS connection with TLS enforced by default. If direct access from the Groundplex to the SnapLogic AWS S3 bucket is blocked, then the connection to the AWS S3 bucket communication falls back to a connection through the SnapLogic Control Plane that still uses TLS 1.2.
Learn more about Snaplex network set up.
Network Guidelines for Snap Usage
...