Your Celigo Private Cloud instance is reachable only the way you decide: over a virtual private network (VPN), from a list of IP addresses you trust, or both. This article explains how to set up each method with Celigo, how to connect the instance to the cloud and on-premises systems your integrations use, and how to keep the connection secure once it's running. It's for the network or security administrator who owns connectivity to the instance.
Set up a VPN
A VPN gives your network an encrypted channel to the instance, limits access to the users and systems on your side of it, and simplifies meeting security and regulatory requirements.
- During onboarding, give Celigo your VPN configuration details.
- Celigo returns the connection credentials and settings — IP ranges and encryption parameters — for your side of the tunnel.
- Test the connection from your network and confirm that users and systems can reach the instance reliably.
Set up IP whitelisting
IP whitelisting restricts access to the instance to a list of trusted addresses. Use static IP addresses for every system that connects, and keep the list as short as you can.
- Send the authorized IP addresses or ranges to Celigo Support.
- Celigo configures the instance to accept traffic only from those addresses.
- Review the list regularly and send changes as systems are added or retired.
Connect to cloud applications
Integrations in your instance connect to cloud applications such as Salesforce, NetSuite, and AWS services the same way they do on shared infrastructure, with API keys or OAuth; see Create a connection to an application. If an application needs to reach your instance — a webhook listener, for example — make sure its endpoints are covered by your VPN or whitelist.
Connect to on-premises systems
For databases, file servers, and ERP systems on your own network:
- Allow traffic from the instance through the VPN or another secure tunnel Celigo supports.
- Build the connections with the Celigo connector for each system; see Connect to anything.
- Run the flows that use them and confirm data moves in both directions.
Monitor and maintain connectivity
Use the platform's monitoring to keep the connection healthy: set alerts for connections that go offline (see Set up email notifications for flow errors or offline connections), and review the audit log for who connected to the instance and when (see View or download your audit logs). Rotate VPN credentials, API tokens, and other secrets on a schedule.
Three practices keep access both secure and available:
- Layer the controls. Combine the VPN, IP whitelisting, and single sign-on; see Set up single sign-on (SSO) for an account.
- Plan for redundancy. Keep a backup connectivity path so an outage on one doesn't cut off the instance.
- Test regularly. Check each connectivity method on a schedule, not only when something fails.
For help with connectivity, contact Celigo Support.