VPN Service
The VPN service is an optional service that is deployed with every environment, providing a way to join outside computers (such as a development machine) into an environment's private network.
The VPN service is an OpenVPN container that supports custom user-access controls.
For security purposes, the VPN is disabled by default, and must be started manually.
Access Controls
The VPN service can be configured to allow any account with access to the environment to use their Cycle credentials to log in, utilize custom VPN logins specifically created for this environment, or both.
Configure VPN Access Controls
Connecting to the VPN
The VPN service will generate OpenVPN connection files upon request. This can be accomplished via the portal or API.
Interacting with Containers Over the VPN
Once an outside computer is connected over the VPN, it can interact with container instances running within the environment just as any other container would.
Cycle TLD
To ensure requests are being routed over the VPN into the environment, the
.cycle TLD can be appended to
force resolution via the discovery service.
# Assuming the container hostname is `api`, these will both work
curl http://api
curl http://api.cycleOr, for example, if a container is hosting a webserver over port 3000, it will be accessible via a browser pointed at
http://<hostname>.cycle:3000