When registering Integrations with publicly available providers, Embedded can communicate with the provider over the public web. Some end users, however, require the ability to register Integrations with providers that are running in on-prem or otherwise unreachable locations. In order to support those providers, Embedded supports a dedicated feature called Synqly Bridge. Synqly Bridge allows end users to run a Bridge agent on their network which can communicate with your Embedded instance and perform API requests to providers on its behalf. For more information on Synqly Bridge, please refer to Synqly Bridge Overview.
In order to enable the Bridge feature with Synqly Embedded, a NATs cluster is required to facilitate communication with Synqly and deployed Bridge Agents. NATs is an open-source, highly available message bus which Embedded uses to send integration API requests to Bridge.
The Synqly Embedded Helm Chart includes the open-source NATs Helm Chart as an optional dependency. The deployment values in Embedded's values.yaml are pre-configured to make running NATs as easy as possible, but there are some manual steps required in order to get NATs configured and operational.
The documentation pages in this section will cover the following topics:
NATs Account Initialization: How to provision the initial NATs Acccounts required to run NATs with Embedded. Embedded will use the generated NATs Account information to authenticate with the deployed NATs instance(s).
NATs Config Guide: Step-by-step guide on how to configure the
natssection ofvalues.yamlonce you have generated NATs Accounts.