Resource Connectors (Deployed in Connector Groups)
Characteristics of resource connectors:
- Send traffic to private resources only.
- Support only Zero Trust Access connections (client-based and browser-based).
- Supported environments: AWS, Azure, VMware, and Docker.
- For more information, see Deploy a Connector in AWS.
- For more information, see Deploy a Connector in Azure.
- For more information, see Deploy a Connector in VMware.
- For more information, see Deploy a Connector in Docker.
- Require only outbound connections from your network.
- Can connect user traffic to resources in data centers that have overlapping IP address ranges (when a single IP address can be in multiple locations), if the resource is defined and accessed using an FQDN.
- If an application is hosted from multiple locations, resource connectors automatically send traffic to the application location nearest to the end-user's location, for an optimal user experience.
- Easily scalable by deploying more connectors in a group.
- Additional network routing configuration is not required. Existing routing is normally sufficient.
- Expose only specified private resources, not your entire network, to Secure Access.
- Connectors proxy traffic, so Secure Access is segmented from your network.
- Self-maintaining lifecycle; software upgrades are managed for you by Secure Access except platform operating system upgrades currently.
- For more information, see Manage Resource Connectors and Resource Connector Groups.