SRA Requirements

Use this page to validate infrastructure requirements before deploying Akeyless Gateway with Secure Remote Access (SRA) and Zero Trust Web Access (ZTWA).

Port values below are default values from the official Helm charts and Docker Compose examples. Exact exposure can vary by deployment model, ingress, and service configuration.

Port Inventory

The following table lists the primary ports by component.

ComponentPort(s)Purpose
Gateway8000External API and SRA portal/web paths
Gateway (Docker Compose default mapping)8080Internal API and health endpoint
Gateway (Docker Compose default mapping)8889Metrics endpoint when metrics are enabled and exposed
SRA web bastion8888Web bastion service
SRA SSH bastion22 (Kubernetes service), 2222 (Docker host mapping), 9900 (control proxy)SSH data plane and control proxy
ZTWA dispatcher9000, 19414Dispatcher listener and web proxy mode
ZTWA web-worker5800Isolated browser worker service (internal service)
Redis6379Cache and session support

Outbound Connectivity

Allow outbound connectivity to the following destinations:

  • Akeyless API endpoint
  • Session forwarding target endpoints, when session forwarding is configured
  • Recording storage endpoints (for example, S3 or Azure Blob), when RDP recording is configured

Redis Dependency

Redis cache support is required for SRA components. For Gateway-only deployments without SRA, cache is optional.

For Redis defaults and operational guidance, see Redis documentation.

Minimum Resources

Use at least 1 vCPU and 2 GiB memory for each SRA component.

Kubernetes-Specific Requirements

  • Expose the SSH bastion service with type: LoadBalancer.
  • Run the SSH bastion container in privileged mode.

For platform guidance, see Kubernetes Service type LoadBalancer and Linux kernel security constraints.

Docker Compose Profiles

Use Docker Compose profiles as follows:

  • gateway
  • sra
  • metrics

For profile behavior and usage, see Docker Compose profiles.


Footer Section