Skip to main content

Network connectivity requirements

Reading time: 0 minute(s) (0 words)

This page includes the outbound access requirements for locally hosted Nobl9 agents and Internet Protocol (IP) addresses for Nobl9 alerts that must be allowed for inbound connections to operate in compliance with the existing firewall or IP address restrictions.

Outbound access for locally hosted Nobl9 agents​

Obtaining the agent container image

Nobl9's agent image is published on Docker Hub. Your Kubernetes cluster or other container runtime requires access to the Docker Hub to pull the image. You can also pull the image to a locally hosted artifact image repository and run it from there.
TCP port 443 outbound to the following:

Obtaining the sloctl image

Nobl9's sloctl image is published on Docker Hub. You can leverage it to integrate Nobl9 in the CI/CD pipelines.

Nobl9 needs outbound TCP port 443 to the following:

AuthN/AuthZ concerns

When an agent data source is created (in the Nobl9 web application or the Nobl9 API, via sloctl or the Terraform provider), an OAuth2 credential is created, unique to that agent. These credentials consist of a Client ID and Client Secret, which can be viewed in the web application as part of the agent installation instructionsβ€”they are visible within the Kubernetes YAML or Docker command line examples.

This credential allows the agent instance to connect to Nobl9 over outbound HTTPS, identify itself, and obtain its query configurations from the Nobl9 Application.

Nobl9 agent container network requirements at runtime

Nobl9 agent needs outbound TCP port 443 to the following:

  • Nobl9 Okta instance
    • This is an Amazon ALB. As such, the IP addresses may change over time.
  • Nobl9 SaaS application
    • This is an Amazon ALB. As such, the IP addresses may change over time.
  • the data source API URL that was configured when you created the agent in the Nobl9 UI (varies depending on data source tool or flavor and your configuration).

Nobl9 alerts​

You can opt to set configure alerts in Nobl9 to a variety of systems, including popular incident management SaaS tools (for paging), ticketing systems, chat systems (for chatops), as well as a flexible and secure customizable webhook feature (for webhooks to your CI/CD system, for example).

You may choose to receive alerts from Nobl9 through a firewall you control. These alerts originate from a predictable set of IP addresses (Amazon Elastic IPs) you can list as allowed for inbound access to your network.

IP addresses to add to your allowlist:
⚠ Applies to only. In all other cases, contact Nobl9 support.