Remote Networks

The “Remote Network” concept in Twingate is a logical container that groups Resources together. All Resources defined within a Remote Network must be accessible from any deployed Connector(s) within the same Remote Network. When planning a Twingate deployment, each Remote Network will approximately correspond to an existing physical network or VPC you’d like to provide remote access to.

At least one Connector must be deployed to allow access to Resources configured in a Remote Network. Connectors are deployed behind the firewall and provide access to a Remote Network’s Resources for authenticated, authorized users. Without a Connector deployed and running, Resources are inaccessible to Twingate end users.

We recommend that you deploy at least two Connectors in every Remote Network that you configure in Twingate. There are two primary reasons to do this:

• Load balancing and failover
  Load balancing is performed automatically as the number of Connectors deployed within a Remote Network is changed. In addition, if any one Connector fails, additional Connectors will be available for redundancy. You can deploy as many Connectors within a Remote Network as required for your needs.
• Scalability
  As your needs grow, it may be necessary to add additional Connectors to forward additional traffic. A single Connector is generally capable of handling traffic for hundreds of users, depending on your usage patterns. See Deploying Connectors for more details.

Best practices

Because Connectors within the same Remote Network are interchangeable, it’s important that they all have the same network routing and access rules on the Remote network. For more Remote Network best practices, please see our best practices documentation.

Last updated 5 months ago