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

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

Agent to AWS SSM Public Internet Endpoints

  • The agent will need OUTBOUND access to AWS SSM public internet endpoints:
    • ssm.us-east-2.amazonaws.com TCP port 443
    • ssmmessages.us-east-2.amazonaws.com TCP port 443
    • ec2messages.us-east-2.amazonaws.com TCP port 443
    • ssm.us-east-1.amazonaws.com TCP port 443
    • ssmmessages.us-east-1.amazonaws.com TCP port 443
    • ec2messages.us-east-1.amazonaws.com TCP port 443
    • ssm.us-west-1.amazonaws.com TCP port 443
    • ssmmessages.us-west-1.amazonaws.com TCP port 443
    • ec2messages.us-west-1.amazonaws.com TCP port 443
    • ssm.us-west-2.amazonaws.com TCP port 443
    • ssmmessages.us-west-2.amazonaws.com TCP port 443
    • ec2messages.us-west-2.amazonaws.com TCP port 443

Note: SSL INTERCEPTION OF TRAFFIC TO THESE PUBLIC INTERNET ENDPOINTS IS NOT SUPPORTED AND WILL FAIL

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

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.

Note: It is not suggested that the rules allow for public access to the agent.