# Admin Portal Configuration for CSPs

Cloudbrink's Personal SASE enables enterprises to deliver best-in-class quality of experience and security for their end users in the new mobile-first and cloud-native world. Cloudbrink achieves this through three simple components:

1. The Brink Agent is installed on end user devices, with all major platforms supported.
2. Enterprise access points are automatically created via machine learning in close proximity to the end user, enabling Cloudbrink's revolutionary overlay protocol to overcome the most challenging last-mile network conditions, delivering best-in-class, hi fidelity quality of experience for the end-user no matter the network they are connected to.
3. To provide end-to-end security, a Cloudbrink Connector is deployed in the customer's data center or cloud environment, creating a dark tunnel connection from the end user to their applications.

This document covers deploying the Cloudbrink Connector in an Cloud (IaaS) environment.

## Introduction

This document will guide the user to configure a Connector entity on the Cloudbrink admin portal and prepare the prerequisites for deploying the Connector VM on an Cloud Service Provider platforms (ex: AWS, Azure, GCP).

## Create a Connector entity on Cloudbrink admin portal

1. Login to Cloudbrink admin portal (<https://admin.cloudbrink.com>) with admin credentials.
2. Navigate to Configure → Resources → Connector section
3. Click on "Add New"

## Cloudbrink Software Defined Mobility

![](https://web-api.textin.com/ocr_image/external/8ce6a9c60c6ba69f.jpg)

4. Provide the values for the configuration parameters as described below

·Name: Name of the Connector

·Hosting Environment: Select "AWS" for AWS

·Deployment Mode: Non-HA (standalone) or Active-Passive or Active-Active

**·** Region: Select the region where Connector will be deployed

·Release: Select latest Ubuntu 22 based Connector release

·Num of Arms: Select 1 for one-arm and 2 for two-arm

·OS: Select Ubuntu

·OS-Version: 22.04 or 20.04

**·** DNS Primary IP: The enterprise private DNS server IP. If not available, use generic DNS services (ex: 8.8.8.8)

·User IP Management: Select "Source NAT" to use Connector interface IP as the source IP for all internal traffic. Select "DHCP" if a DHCP server will assign LAN IP to the remote user sessions or "Static IP Pool" if the LAN IP is managed by the Connector itself.

**·** Enterprise Services: Select the list of private IP subnet(s)/Hosts that would be accessible from this Connector

## Cloudbrink Software Defined Mobility

![](https://web-api.textin.com/ocr_image/external/1d4183bbad83b5ce.jpg)

![](https://web-api.textin.com/ocr_image/external/cf907d18b0803a83.jpg)

5. Click "Save" to create the Connector configuration entity
6. Generate OTP for the Connector and use this OTP in the Connector VM installation steps defined in the corresponding guide.
7. **NOTE**: Separate and new OTP must be used for every new instance of the Connector VM in active-passive or active-active mode

## Cloudbrink Software Defined Mobility

![](https://web-api.textin.com/ocr_image/external/c44927a174a3086c.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/admin-portal-configuration-for-csps.md?ask=<question>
```

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.