Automation Firewall requirements

This article outlines the firewall requirements for the two deployment options supported by the Callgoose SQIBS Automation Platform. To learn more about the deployment options and capabilities of the platform, refer to the following resources:

• Callgoose SQIBS Automation Platform Overview
• Callgoose SQIBS Automation Documentation
• Callgoose SQIBS Runner Setup

Callgoose SQIBS Runner Program - Firewall Requirements

The Callgoose SQIBS Runner Program is deployed within your on-premise IT infrastructure and requires only outbound access to the Callgoose SQIBS platform servers. The Runner securely connects to the platform to fetch and execute automation jobs.

Required IPs and Ports:

• Outbound access must be allowed to the following IP addresses:
• 66.42.56.59
• 172.105.127.89
• Port: 443 (HTTPS)

If your IT environment restricts outbound access, ensure that these IP addresses and ports are added to your allowed list for the Callgoose SQIBS Runner Program to function correctly.

Callgoose SQIBS Automation SaaS Platform - Out of the Box Integration Firewall Requirements

For users utilizing the Out of the Box Integration provided by the Callgoose SQIBS Automation SaaS Platform, both inbound and outbound access is required to enable communication between the Callgoose SQIBS platform and your internal servers or applications.

Required IPs and Ports:

• Inbound and outbound access must be allowed to the following IP addresses:
• 66.42.56.59
• 172.105.127.89
• Inbound Port: 443 (HTTPS)
• Outbound Ports: The port depends on the type of integration or task being executed:
• SSH Connections: By default, port 22 (SSH) must be allowed. If your server uses a non-standard SSH port, ensure that the respective port is opened.
• API Connections: For tasks involving API communication, allow port 443 (HTTPS).
• Other Applications: If you're using other tools like Ansible, Terraform, Kubectl, Bash, PowerShell, Python, WINRM or others, the port may vary depending on the application and task being executed. Most tasks use the default ports (SSH for remote access or HTTPS for API communication), but some may require custom ports.

For more detailed instructions and platform-specific guidance, refer to the Callgoose SQIBS Documentation.