Skip to main content
Not every source is reachable from the internet, and that is never a blocker: any system behind a VPN is accessible to RWS Integration, both for your integrations and for RWS Connect pipelines. It does not matter whose system it is: your own, your customer’s, or any third party’s. Databases, SOAP services and file servers are all reached the same way, through a VPN between RWS and the network where the system lives.
Previews and integrations work perfectly for systems behind a VPN. Once the tunnel is up, the Extract Preview panel and your integrations behave exactly as they do with publicly reachable sources.

​
Supported VPN types

​
Security

Tunnels are outbound only: traffic is always initiated by RWS toward the network where the systems live, never in the other direction. Opening the tunnel gives RWS access to the declared network ranges and nothing else. No system on that network can reach RWS or any other environment through it, guaranteeing security. Combined with the fixed IP addresses, the network team always knows exactly who connects and from where.

​
IPSec (site-to-site): step by step

  1. Request the VPN by emailing connect@rwsintegration.com with:
  1. RWS sets up its side and generates a configuration file tailored to the firewall model you informed
  2. You receive the configuration file with everything the firewall needs: the two tunnel endpoints, one pre-shared key per tunnel, and the phase 1 and phase 2 encryption parameters
  3. The network team applies the configuration to the firewall, setting up both tunnels
  4. We validate together: with the tunnels up, RWS confirms it can reach the network. Everything works from that moment: go to the application and create your integrations
The configuration always contains two tunnels for redundancy. Configure both: if one goes down, traffic fails over to the other automatically and your integrations keep running.

​
OpenVPN

Much simpler: email connect@rwsintegration.com with the OpenVPN configuration file and the credentials it needs (certificates, user and password). RWS installs them on its side, and nothing else is required from your team.

​
IP allowlisting

All RWS traffic originates from three fixed IP addresses:
If the source is protected by a firewall but does not require a VPN, allowlisting these three IPs is enough to grant access.

​
Requesting and SLA

VPN setup is requested by email to connect@rwsintegration.com.
The SLA is two business days after the information for your VPN type is provided. Once the VPN is up, systems on that network are immediately usable: go to the application and create your integrations. If you also requested an RWS Connect connector for a system on that network, its own SLA of two business days counts from that point.

​
Next steps

Network Connectivity

How RWS reaches any system, anywhere

Databases (JDBC)

Extract from databases on private networks

SOAP APIs

Extract from SOAP services behind a firewall