Connector pools
This section describes how to create connector pools and assign connectors to the pool.
Overview
Connector pools enable you to:
-
Define a cloud or on-premises network, which can consist of multiple subnets, VPCs/VNets, AWS account IDs and Azure subscription IDs, Azure subscription IDs, and Google Cloud project IDs.
-
Assign a connector to the pool, to provide access to that network.
You can have one connector in the pool to serve all the targets in the defined network. For high availability and scalability, you can add multiple connectors to the connector pool.
Ensure you define a connector pool for each cloud network in your cloud environment, and for each network in your on-premises assets.
Connector pools are supported for on-premises targets and the following cloud platforms:
-
AWS
-
Google Cloud
-
Azure
If you need to connect to Window machines on AWS, at least one of the connectors in the pool must be installed on Windows, in order to do the provisioning. We recommend installing at least two connectors on Windows, to ensure availability. All the connectors in the pool will share the load for connection, including those installed on Linux.
View and manage connector pools
From the Connectors > Connector pools page, you can view, and manage connector pools.
The following tables list the details displayed about each connector pool and the available actions.
Element |
Description |
---|---|
Connector pool name |
Give the pool a meaningful name. If you do not assign a connector to a pool, it is assigned to a default pool. |
Type |
The following are supported:
|
No. of connectors |
The number of connectors deployed in the pool. |
Description |
Meaningful description of the connector pool. |
Action |
Description |
---|---|
Add a pool |
Add a new connector pool |
Add a connector |
Add a new connector |
Switch views |
You can switch between the following views:
|
Edit |
Edit an existing connector pool You can't edit default pools. While editing a pool, if you remove all the connectors that are installed on Windows from the pool, you'll no longer be able to use that pool to connect to AWS targets via RDP. |
Delete |
Delete an existing connector pool You can't delete a pool if it has connectors assigned to it. |
Assign a connector |
Assign a connector to a connector pool |
Create a connector pool
Go to the Connectors > Connector pools page and select Add a pool.
Step 1: Select a platform
You can define multiple connector pools for a platform to provide network coverage.
The following platforms are supported:
-
AWS
-
Azure
-
Google Cloud
-
On-premises
Step 2: Define network coverage
Specify multiple subnets, VNets/VPCs, AWS account IDS, Azure subscription IDs, or Google Cloud project IDs that define your network using the appropriate format as detailed in the following tables.
Element |
Format |
---|---|
List of VPCs |
vpc-<vpc-id> |
List of subnets |
vpc-id/subnet-id |
List of AWS accounts |
Account ID |
Element |
Format |
---|---|
List of VNets |
Type the full VNet ID For example:
|
List of subnets |
VNet-id/subnet-id For example:
|
List of subscriptions |
Subscription ID |
Element |
Format |
---|---|
List of VPC networks |
Type the full VPC network name For example:
|
List of subnets |
VNet-id/subnet-id For example:
|
List of projects |
Project ID |
Element |
Format |
---|---|
FQDN |
To add an FQDN:
An FQDN configured with a domain also includes its subdomains. |
Logical network name |
Use to help with quick identification of the connector pool's coverage. |
Step 3: Assign a connector
-
Select the connector you want to assign to your connector pool.
From the Connector > More menu, select Assign connector.
You can search for connectors from the connectors view.
-
From the connector details pane, select Re-assign.
-
From the Reassign connector dialog, select the connector pool from the drop-down.