Problem: My network contains security policies that prevent agents from reaching the SeaLights platform
This is normally caused due to security policies related to Firewalls, or other networking related security configurations that prevent access to the SeaLights API. In order to verify this is the case, try running a cURL command to your dashboard URL:
curl -vI https://<YourCustomDNSName>.sealights.co
HTTP/2 200 code should be returned. If this code is received, you can access the SeaLights API and there is no need for this document.
If using a proxy, you should add the relevant parameter
curl -vI https://<YourCustomDNSName>.sealights.co --proxy http://myproxy.mycompany.int
If you need a generic Sealights endpoint, you can use https://connect.sealights.co in your command.
In case this command fails, it is important to understand why. Looking at the detailed output (given by the -vI flags) can point us in the right direction.
The above cURL commands runs on native Linux. If using Windows, you will need to run it from a PowerShell prompt as it allows curl commands as an alias to the native Invoke-WebRequest cmdlet that you can use as well.
For example, Invoke-WebRequest -Uri https://<YourCustomDNSName>.sealights.co | Select-Object -ExpandProperty BaseResponse
Solution
In case a firewall is present, it needs to allow network traffic to reach the SeaLights platform and depending on your organization policy, you can use one of the following solutions.
Allow outbound traffic to Sealights' domain
The Firewall should allow outbound connections on port 443 (TLS v1.2) to our domain https://*.sealights.co.
For a more restrictive rule, you can open the connections to your Sealights dashboard URL only.
Allow outbound traffic to Sealights' range of IP adresses
As SeaLights' networking is managed in AWS, the full list of subnets which can point to our platform, can be found in the ip-ranges.json file supplied by AWS.
Be sure to follow the next steps to understand which IP addresses need to be added to your exceptions list:
Download the provided
ip-ranges.jsonfile from AWS.From the file, filter out the entries related to CloudFront (using jq):
cat ip-ranges.json | jq '.prefixes[] | select(.service=="CLOUDFRONT")'Add the subnets output from the previous stage to your Firewall exception list for outbound connections on port 443 (TLS v1.2)