> For the complete documentation index, see [llms.txt](https://docs.cloudbrink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudbrink.com/configuration/connector-deployment/active-active-aws.md).

# Active - Active: AWS

## Active-Active Connectors on AWS

The Cloudbrink Connector component provides secure zero-trust access to private applications hosted inside customer private networks. Cloudbrink supports access to private networks in a physical on-prem datacenter or a virtual CSP-hosted datacenter such as a VPC/VNET on AWS, Azure, or GCP.

Starting with release **14.2**, Cloudbrink supports Connector deployments in **Active-Active** mode on AWS, in addition to the existing **Standalone** and **Active-Standby** modes.

{% hint style="info" %}
Active-Active mode is available on **AWS only** in the 14.2 release.
{% endhint %}

### Points to note

* Up to **64 Connector instances** can be clustered in one logical Active-Active Connector group.
* All Connector instances must be in the **same AWS VPC**.
* When a new Connector instance is added to an existing Active-Active Connector group, new user sessions are loaded onto the new instance until the load is evenly balanced. Existing sessions on the existing instances are not touched.
* When an existing Connector instance becomes unavailable for any reason, the user sessions on that instance are re-distributed across the remaining available instances.
* When user sessions are re-distributed, users do not need to re-authenticate to Cloudbrink. The user's authentication session remains intact.
* Network-level TCP connections are terminated when a user session is re-distributed to another instance. Applications such as SSH or FTP need to be re-established. Web sessions see a short disruption but continue to work after re-distribution.
* User sessions are distributed across Connector instances based on the session load of each instance.

### Use cases

#### Horizontal scaling

Customers with high-scale requirements can use Active-Active mode to support a large number of users. Customers can start with a limited number of Connector instances and, as the user base grows, add more Connector instances to meet the new scale requirements.

#### Availability

Active-Active mode can be used to increase availability. When one Connector instance becomes unavailable, the load on that instance is distributed across all remaining available instances. In case of an incident, multiple other instances take over the load without burdening a single standby instance.

### Deployment steps

#### Step 1: Create the Active-Active Connector on the Cloudbrink Admin Portal

1. Navigate to **Admin Portal → Configure → Resources → Connectors → Add**.
2. When adding the new Connector, set **Deployment Mode** to **active-active**.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>This option is shown only when <strong>Hosting Environment</strong> is set to <strong>AWS</strong>.</p></div>
3. Select the list of **Device-User-Groups** that will use this Connector to access private applications. As part of the Device-User-Group selection, configure a **Pool Name** and **Lease Time** for each Device-User-Group.
4. Configure the remaining parameters (**DNS Servers**, **Enterprise Resources**) as usual. **User IP Management** is pre-selected as **Static IP Pool**.
5. **Save** the Connector.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FvShLV21u6BNZQ1UFPuep%2Faa-connector-deployment-mode.png?alt=media&amp;token=51ab2d19-560c-41ff-b511-fe1bf430550d" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FmyiSzLNBrZyGIMOzjUdl%2Faa-connector-static-ip-pool.png?alt=media&amp;token=b522303c-2a0d-4281-abe2-bb6a9b5ebf22" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2Fa802tbQZzHDvtH6jT7zc%2Faa-connector-enterprise-resources.png?alt=media&amp;token=b2c53540-41f9-47e0-9d48-ddb705cc71a1" alt=""><figcaption></figcaption></figure>

#### Step 2: Deploy Connector instances from the AWS Management Console

1. Select the latest Connector AMI from the AWS Management Console and deploy a new instance.
2. In the cloud-init script, provide the correct input parameters such as **IP address**, **Gateway**, and the **OTP** generated from the Cloudbrink Admin Portal for this Connector.
3. Once the Connector instance deployment completes successfully on AWS, the Cloudbrink Admin Portal shows the instance in **Online** status.

**Connector list**

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2F8lWOlp6bHne273rJFbIl%2Faa-connector-list.png?alt=media&amp;token=02ddb3af-662e-40c2-9c49-b5845cf6c497" alt=""><figcaption></figcaption></figure>

**Instance-level list for each Connector**

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FsiemZTQdeKzErT2q22Rr%2Faa-connector-instance-list.png?alt=media&amp;token=98789896-284b-41ea-b56b-fcfe21544d3b" alt=""><figcaption></figcaption></figure>

#### Step 3: Configure IP prefixes for Connector instances on AWS

1. From the AWS Management Console, navigate to the **Network Interface** of each Connector instance and assign IPv4 and/or IPv6 prefixes. See the AWS documentation: [Assign prefixes to Amazon EC2 network interfaces](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/work-with-prefixes.html).
2. AWS supports **/28** for IPv4 prefixes and **/80** for IPv6 prefixes.
3. Note down the IP prefixes assigned to each Connector instance. The same configuration must be entered on the Cloudbrink Admin Portal in the next step.

#### Step 4: Configure Static IP Pools for Connector instances on the Cloudbrink Admin Portal

1. Navigate to the Connector instances of the Active-Active Connector by clicking the **Name** of the Active-Active Connector.
2. Under each Connector instance, the Pool Names specified at the Connector level are pre-populated.
3. For each Pool Name, define the IPv4 and IPv6 pools.

   <div data-gb-custom-block data-tag="hint" data-style="danger" class="hint hint-danger"><p>The IP pools must <strong>exactly match</strong> the IP prefixes assigned to the respective AWS instances.</p></div>

**Per-instance IP prefix configuration**

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FHrSpgYxGSm2N92AG3aRk%2Faa-connector-ip-prefix-config.png?alt=media&amp;token=8182f32e-fbf4-4f6c-9e03-df0f8e57a4e8" alt=""><figcaption></figcaption></figure>

#### Step 5: Verify the Connector instance status

All Connector instances must be in **Active** status. Active status indicates that the Connector is ready to handle user traffic to the private applications.

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FtijXAYPztqxSwp1YTUCT%2Faa-connector-instance-active.png?alt=media&amp;token=f3b1e1f5-65ce-4da7-b311-1f59862b6584" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2F6kgX8SRZEwaTGdOyrbkF%2Faa-connector-active-agents.png?alt=media&amp;token=d2158200-4af6-4e4c-9c6d-d63c11c3e9a7" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2520794396-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsONIa4VvrnRrQWBte3ns%2Fuploads%2FbChncQaUOYqlNXrzWdQt%2Faa-connector-private-ip.png?alt=media&amp;token=685b6a69-280c-48df-bc38-ffd88f72c69a" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cloudbrink.com/configuration/connector-deployment/active-active-aws.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
