Requirements and Guidelines for Connectors
- Supported platforms for connectors: AWS, Microsoft Azure, VMware ESXi, Docker Container.
- For information about deploying connectors in AWS, see Deploy a Connector in AWS.
- For information about deploying connectors in Microsoft Azure, see Deploy a Connector in Azure.
- For information about deploying connectors in VMware, see Deploy a Connector in VMware.
- For information about deploying connectors in a Docker container, see Deploy a Connector in Docker.
- Connector IP addresses:
- Connectors support IPv4 addresses. IPv6 is not supported.
- You cannot use any address reserved for use by Secure Access. For information about addresses reserved for Resource Connectors, see Network Requirements for Secure Access.
- For maximum connector throughput capacity, DTLS and TLS connections must originate from the same IP address. If the originating IP addresses are different, TLS connections will be used, with a significant reduction in throughput.
- For maximum connector throughput capacity, DTLS is required. Connections are downgraded to TLS if the originating IP addresses for the connections to Secure Access are different or UDP connections are blocked.
- Deploy connectors in the same data center, branch office, or security zone location as the private resources to which they will send traffic.
- Each connector in a connector group must be able to reach all of the private resources assigned to the connector group.
- All connectors must be able to reach the Secure Access cloud. For more information, see Connectivity Requirements.
- Connectors support only a single network interface.