...
| Code Block |
|---|
curl -vI https://<CustomDNSName><YourCustomDNSName>.sealights.co |
If you need a generic endpoints, you can use the following command
| Code Block |
|---|
curl -vI https://csdemo.sealights.co |
If using a proxy, you should add the relevant parameter
| Code Block |
|---|
curl -vI https://<CustomDNSName><YourCustomDNSName>.sealights.co --proxy http://myproxy.mycompany.int |
...
| Warning |
|---|
In case this command fails, it is important to understand why. Looking at the detailed output (given by the |
| Info |
|---|
The above cURL command runs on native Linux. If using Windows, you will need to run it from a PowerShell prompt as it is an alias to the native |
...
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 custom domain only (https://<YourCustomDNSName>.sealights.co)
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 entires related to CloudFront (using jq):
Code Block 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)
...
| Page Properties | ||
|---|---|---|
| ||
|