External services
External services extend Airlock Gateway beyond the local node to provide shared state, centralized analytics, and long-term reporting. In many deployments it is advantageous to offload processing and storage to dedicated components (e.g., reuse an existing SIEM stack, aggregate logs across environments, improve availability, or scale independently). Airlock Gateway can send its logs to a remote Elasticsearch instance rather than relying solely on the built-in local Elasticsearch & Kibana stack.
You can integrate the following external services into your system architecture:
- Redis — external shared session store for clustered Gateways
Use an external Redis session store to share session state across multiple Airlock Gateway instances, enabling horizontal scaling and failover. Because session storage is critical, the Redis service must be low-latency and highly available; outages degrade performance and can block new sessions. Size the store within real capacity and leave headroom for peak load.
For supported topologies and configuration options, refer to the relevant documentation section.
- Elasticsearch and Kibana (EK) — centralized log ingestion, search, and visualization
Airlock Gateway can send its logs to a remote Elasticsearch endpoint over HTTP/HTTPS for centralized reporting in Kibana. If you don’t already operate an EK stack, the reporting bundle provides ready-made templates/pipelines and Kibana saved objects to run EK off‑appliance.
Further information: