Connect to Atlas

Atlas Services provide ExtraHop customers with a remote analysis report delivered monthly that contains specific recommendations for critical components across the application delivery chain. For more information and to view a sample of this report, visit Atlas Remote Analysis Reports on the ExtraHop website.

To connect to Atlas, you need the following:

  • The ability to do a DNS lookup of *.a.extrahop.com
  • The ability to connect to the Atlas server through HTTPS (port 443)

Firewall Rules

To connect to the Atlas server through your firewall, you must allow access to the Atlas public IP address through HTTPS (port 443). ExtraHop Networks might change the Atlas IP address at any time. To determine the current IP address, run the following command:

dig +short foo.a.extrahop.com

For protocol, request TCP. For port, request HTTPS / port 443.

Proxy

If you want to connect to Atlas through a proxy, add the following lines to the Running Config file of each ExtraHop system you want to connect to Atlas. The username and password might be optional for your proxy.

"http_proxy": {
    "atlas": {
        "host": "proxyhost",
        "port": "8080",
        "username": "username",
        "password": "password"
    }
},

ExtraHop Administration UI

If you want to connect to Atlas through the ExtraHop Administration UI, refer to the Network Settings section in the ExtraHop Admin UI Guide.

Connect to the ExtraHop License Server

To connect to the ExtraHop license server, you need the ability to do a DNS lookup of *.a.extrahop.com. In most cases, no internal DNS configuration is necessary. You can test your internal DNS infrastructure for this ability by running the following command on an internal computer:

nslookup foo.a.extrahop.com

For more information, refer to the License section.

Published 2017-11-20 17:13