Add Connectors to a Connector Group

Each connector is associated with a connector group, which is in turn associated with specific private resources.

Use the pre-configured connector image to deploy resource connectors in your data centers. During deployment, you will associate each connector with a group using the provisioning key associated with the connector group.

If you need additional throughput capacity to handle the volume of traffic that a connector group must handle, add connectors to the group. You can add resource connectors to a group at any time.

Table of Contents

• Prerequisites
• Procedure
  • Step 1 – Deploy Secure Access Resource Connectors
  • Step 2 – Confirm Connectors
  • Step 3 – Map Private Resources to Connector Group

Prerequisites

• Full Admin role in Secure Access. For more information, see Manage Accounts.

• See requirements and guidelines for connectors in Requirements and Prerequisites for Resource Connectors and Connector Groups.

• Add a connector group for traffic to the data center, branch office, or security zone. For more information, see Add Resource Connector Groups.

• Determine the number of resource connectors to deploy in the group. For details, see:

  • The Capacity Requirements section in Requirements and Prerequisites for Resource Connectors and Connector Groups.
  • Determine the Number of Connectors Needed in a Connector Group.

Procedure

Step 1 – Deploy Secure Access Resource Connectors

1. Obtain the connector image. For more information, see Obtain the Connector Image.

   You can download the image once, then use it for multiple connectors in multiple groups.
   All connectors in a group must use the same environment, for example AWS or VMware.
   However, before deploying, ensure that you have the latest image version.

2. Note the provisioning key for the connector group in which you are deploying connectors.
   You will need this key when deploying connector instances.
   For more information, see Provisioning Keys for Resource Connectors.

3. Deploy connector instances in your environment.

   • For information about VMware, see Deploy a Connector in VMware
   • For information about AWS, see Deploy a Connector in AWS.

Step 2 – Confirm Connectors

After connector instances launch, they will automatically connect to Secure Access. Before you can use connectors, you must accept the connectors in Secure Access to confirm that they are expected and legitimate:

1. In Secure Access, navigate to Connect > Network Connections, and then click Connector Groups.
2. Expand Confirm Connectors .
3. If necessary, wait up to 15 minutes for just-deployed connectors to launch and reach out to Secure Access.

4. Review the list of deployed connectors to ensure that all are expected and legitimate.
   The Origin IP Address of the connector may indicate where the connector is located, which may help you determine if it is legitimate.
   If there are connectors in the list that you are unsure about, you can revoke or disable them before you confirm the others. Disabled connectors will still be confirmed but will be inactive; revoked connectors will not be confirmed. Revoking a connector invalidates the current provisioning key and generates a new key, so you will need to use the new key for subsequent connectors that you deploy. For more information, see Disable, Revoke, or Delete Resource Connectors and Groups.
5. To confirm all connectors in the list, click Confirm Connectors.

Step 3 – Assign Private Resources to Connector Group

Connectors send user traffic to the private resources assigned to the connector group, which the connectors belong to. For more information, see Assign Private Resources to a Connector Group.

If you see issues with a newly deployed connector, see Connector diagnostics (CLI) in Troubleshoot Resource Connectors and Connector Groups.

Add Resource Connector Groups < Add Connectors to a Connector Group > Obtain the Connector Image