# Active - Active: AWS Cloudbrink Connector component is needed for providinng secure zero-trust access to private applications hosted inside the customers private networks. Cloudbrink supports access to private networks in a physical on-prem datacenter or virtual CSP hosted datacenter such as VPC/VNET on AWS, Azure or GCP. From 14.2 release, Cloudbrink will support Connector deployments in Active-Active mode on AWS, apart from the earlier modes of Standalone or Active-Standby. The Active-Active mode of deployment is available on AWS only for the 14.2 release. ## 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 will be loaded on to the new instance until the load is evenly balanced. Existing sessions on the existing instances will not be touched. ·When an existing Connector instance becomes unavailable for any reason, the user sessions on the particular Connector instance will be re-distributed across the remaining available instances. · When user sessions are re-distributed, user need not re-authenticate to Cloudbrink. The user's authentication session will remain intact. ·The network level TCP connections will be terminated when the user session is re-distributed to other instances. Applications such as SSH or FTP need to be re-established. Web sessions will see short disruption but continue to work after re-distribution. ·User sessions are distributed across Connector instances based on the session load of the Connector instance. ## Use Cases: ### A. Horizontal Scaling Customers having high scale requirements can use the Active-Active mode of deployment to support large number of users. With Active-Active mode, customers can start with a limited number of Connector instances and as the users grow, more Connector instances can be added to support the new scale requirements. ### B. Availability Active-Active mode of Connectors can be used for increasing the availability. When one Connector instance becomes unavailable, the load on that instance will be distributed across all the remaining available instances. This helps in ensuring that in case of an incident, there are multiple other instances to take over the load without burdening one single instance (standby). ### Deployment Steps: #### i) Create Active-Active Connector on Cloudbrink Admin Portal a. Navigate to Admin Portal → Configure → Resources → Connectors → Add b. When adding a new Connector, select "Deployment Mode" as Active-Active. This option will be shown only if "Hosting Environment" is selected as "AWS" c. Select the list of Device-User-Groups that will use this Connector for accessing private applications. As part of the Device-User-Groups selection, "Pool Names" and "Lease-Time" for each Device-User-Group must be configured. d. Configure the other parameters (DNS Servers, Enterprise Resources) as usual. "User IP Management" will be pre-selected as "Static IP Pool" e. Save the Connector ![](https://web-api.textin.com/ocr_image/external/be900c7e6ce7117e.jpg) ![](https://web-api.textin.com/ocr_image/external/c2c81e95fc0b411f.jpg) ![](https://web-api.textin.com/ocr_image/external/6495260dea97305f.jpg) #### ii) Deploy Connector instances from the AWS Management Console a. Select the latest Connector AMI from the AWS management console and deploy new instance b. As part of the cloud-init script, provide correct input parameters such as IP address,Gateway, and the OTP generated from the Cloudbrink Admin Portal for this Connector c. Once Connector instance deployment is successfully completed on the AWS, CloudbrinkAdmin Portal will show the instance in "Online" status **Connector list** ![](https://web-api.textin.com/ocr_image/external/b8cb1080d19f1252.jpg) ### Instance level list for each Connector ![](https://web-api.textin.com/ocr_image/external/028ff4d215b995ea.jpg) ### iii) Configure IP Prefixes for Connector instances on AWS a. From the AWS Management Console, navigate to the Network Interface of each Connector instances and assign IPv4 and/or IPv6 Prefixes. Refer to below documentation b. AWS supports /28 for IPv4 prefixes and /80 for IPv6 prefixes c. Note down the IP Prefixes assigned to the Connector instances because same configuration must be done on the Cloudbrink Admin Portal **iv)** **Configure Static IP Pools for Connector instances on Cloudbrink Admin Portal** a. Navigate to the Connector instances of the Active-Active Connector by clicking on the Name of the Active-Active Connector b. Under each Connector instance, the Pool Names that are specified at the Connector level will be prepopulated c. For each Pool Name, define the IPv4 and IPv6 Pools. The IP Pools must exactly match the IP Prefixes defined on the respective AWS instances ### Per instance IP prefix configuration ![](https://web-api.textin.com/ocr_image/external/ac81959b285816cb.jpg) **v)** **Verify the Connector instance status** a. All Connector instances must be in "Active" status. Active statusindicates that Connector is ready for handling user traffic to the private applications | CLOUDBRINK | CLOUDBRINK | CLOUDBRINK | CLOUDBRINK | CLOUDBRINK | CLOUDBRINK | CLOUDBRINK | | ---------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | | Device User Oroups Admin Users/Groups Resources Policies System Internet Security | Device User Oroups Admin Users/Groups Resources Policies System Internet Security | Device User Oroups Admin Users/Groups Resources Policies System Internet Security | Device User Oroups Admin Users/Groups Resources Policies System Internet Security | Device User Oroups Admin Users/Groups Resources Policies System Internet Security | Device User Oroups Admin Users/Groups Resources Policies System Internet Security | | | Application SServices Enterprise Services Connectors IPSec Gateways Resource Templates | Application SServices Enterprise Services Connectors IPSec Gateways Resource Templates | Application SServices Enterprise Services Connectors IPSec Gateways Resource Templates | Application SServices Enterprise Services Connectors IPSec Gateways Resource Templates | Application SServices Enterprise Services Connectors IPSec Gateways Resource Templates | Application SServices Enterprise Services Connectors IPSec Gateways Resource Templates | | |

ActiveActive-Connector
Instances 3UpdateDelete Name
☐ aws-us-vir-con-00008 ☐ aws-us-vir-con-00009 ☐ aws-us-vi-con-0000a

| | | | | | | |

ActiveActive-Connector
Instances 3UpdateDelete Name
☐ aws-us-vir-con-00008 ☐ aws-us-vir-con-00009 ☐ aws-us-vi-con-0000a

| | | | | | | |

ActiveActive-Connector
Instances 3UpdateDelete Name
☐ aws-us-vir-con-00008 ☐ aws-us-vir-con-00009 ☐ aws-us-vi-con-0000a

| Provider Instance Id Status Management IP | Active Agents | User Group Associations | Version | Up Since | | |

ActiveActive-Connector
Instances 3UpdateDelete Name
☐ aws-us-vir-con-00008 ☐ aws-us-vir-con-00009 ☐ aws-us-vi-con-0000a

| 1-0e306ccdf94 Active 172.18,140.76 | | Pool1 | 13.4.23 | 10/28/2024,10:48:06 AM | | |

ActiveActive-Connector
Instances 3UpdateDelete Name
☐ aws-us-vir-con-00008 ☐ aws-us-vir-con-00009 ☐ aws-us-vi-con-0000a

| 1-0aef45551f04d30bc Active 172.18.139.171 | | Pool1 +1 | 13.4.23 | 10/28/2024,10:48:07 AM | | |

ActiveActive-Connector
Instances 3UpdateDelete Name
☐ aws-us-vir-con-00008 ☐ aws-us-vir-con-00009 ☐ aws-us-vi-con-0000a

| 1-0e83881e2695a75a5 Active 172.18.139.119 | 10 | Pool1 | 13.4.23 | 10/28/2024,12:53:41 PM | ![](https://web-api.textin.com/ocr_image/external/5d2cae3d7e39e592.jpg) ![](https://web-api.textin.com/ocr_image/external/1c4e44f34307cffa.jpg) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cloudbrink.com/configuration/connector-deployment/active-active-aws.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.