Overview
What your firewall must allow depends on where automation runs. With the automation runner, everything is outbound HTTPS from your network. With cloud actions (no runner), the SQIBS platform connects in to the servers it manages.
You need
Access to your firewall rulesWhere
Your network edgeResult
Automation that can reach your systemsWhat to allow
| You use | Direction | To / from | Port |
|---|---|---|---|
| Callgoose automation runner | Outbound from the runner host | The SQIBS platform | 443 (HTTPS) |
| Cloud actions on your servers (no runner) | Inbound to your servers | The SQIBS platform | 22 for SSH (or your SSH port); the tool's port otherwise, for example 443, 5985/5986 for WinRM |
SQIBS platform addresses
Allow these addresses for the rules above:
66.42.56.59172.105.127.89
If you allow by host name instead, contact Callgoose support for the current list.
Recommendations
- Prefer the runner: no inbound ports, and your credentials stay in your network.
- For cloud actions, open the port only to the SQIBS addresses, never to everyone.
- Check the ports your own tools use (for example a custom SSH port).