> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloud.red/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Connectivity Requirements

> All requirements for the agent to connect to Cloud.Red

## Agent to Cloud.Red Public Internet Endpoints

* The agent will need OUTBOUND access to Cloud.Red public internet endpoints:
  * `75.2.84.176 (management.cloud.red) TCP port 443`
  * `99.83.227.84 (management.cloud.red) TCP port 443`

<Tip>
  **Note:** SSL INTERCEPTION AND/OR CONTENT INSPECTION OF TRAFFIC TO THESE PUBLIC INTERNET ENDPOINTS IS NOT SUPPORTED AND WILL FAIL
</Tip>

## Agent to DNS and NTP Servers

* The agent will need OUTBOUND access to:
  * DNS servers (capable of internet DNS resolution)
  * NTP servers (preferably 3 or more)

## Agent to Management Port of F5 Hosts

* The agent will need OUTBOUND access to Management port of F5 hosts:
  * `UDP/161, TCP/22, TCP/443`
* F5 access details:
  * [HTTP Access Rule Update](https://support.f5.com/csp/article/K13309)
  * [SSH Access Rule Update](https://support.f5.com/csp/article/K5380)

## Agent to Management of NGINX Hosts

* The agent will need OUTBOUND access to Management of NGINX hosts:
  * TBD (due to the dynamic nature of NGINX hosting environments)

## F5 BIGIPs and NGINX Hosts to Agent

* Your managed F5 and NGINX hosts will require connectivity to the Cloud.Red agent on the following ports:
  * `UDP/162`
  * `TCP+UDP/514`
  * `TCP/22`
  * `TCP+UDP/1514`
  * `TCP+UDP/5000-5099`
  * `TCP+UDP/6000-7000`

## Client Connectivity to Agent

* During on-boarding, the client must be able to reach the agent on port 443.

<Tip>
  **Note:** It is not suggested that the rules allow for public access to the agent.
</Tip>