Guidelines for Connector Groups
- Generally, we recommend that you deploy one resource connector group for each data center, branch office, or security zone that contains private resources that remote users must reach.
- A single location can have multiple connector groups that send traffic to discrete sets of resources.
- A single connector group that sends traffic to resources in multiple locations is not recommended.
- For configuration guidelines for resource connector groups for private resources residing in multiple locations, see Private Resource Configuration Examples.
When adding connectors to a group:
- Deploy all connectors in a group in the same environment, for example AWS, Microsoft Azure, or VMware.
- For accurate load balancing, the instance type for all connectors in a group must be identical.
- Each connector in a connector group must be able to reach all of the private resources assigned to the connector group.