For the complete documentation index, see llms.txt. This page is also available as Markdown.

Cloud API Gateway

Connect remote applications to the Command Centre REST API without inbound firewall rules.

Cloud API Gateway network architecture: remote and cloud clients reach the gateway over the internet, which tunnels through to the on-premises Command Centre server

The Cloud API Gateway lets integrators reach the Command Centre REST API without any on-premises firewall configuration. The customer's Command Centre connects outbound to the gateway, and integrators connect inbound to the gateway. The gateway tunnels REST API requests through to the on-premises Command Centre server and brokers the calls.

Why it exists

When the REST API client is on the same corporate network as Command Centre, direct calls work well. Increasingly clients are cloud-based or remote, where direct deployment is difficult and costly. A direct integration often needs corporate IT approval, firewall reconfiguration, and similar work. The Cloud API Gateway removes that.

Conceptually the gateway fills the same role as an HTTP reverse proxy, such as Azure Application Gateway, AWS API Gateway, or HAProxy.

Direct REST API compared with the Cloud API Gateway

Direct REST API (on-prem)
Cloud API Gateway

Firewall

Requires inbound firewall rules to the Command Centre server

No customer firewall configuration needed

Best for

Air-gapped or high-security deployments, lowest latency

SaaS-style and remote integrations

Trade-off

Each integration adds firewall rules; network changes can break integrations

Cloud dependency and slight latency overhead

For a customer asking "can I integrate without opening firewall ports?", the answer is yes, via the Cloud API Gateway.

Full setup detail is in the Cloud API Gateway Technical Information Paper on the Gallagher developer documentation site (gallaghersecurity.github.io).

Last updated

Was this helpful?