The Akeyless Gateway is a stateless docker container, provided as a standalone or cluster. In order for the Akeyless Gateway to function properly, it requires public network connectivity to the Akeyless SaaS CORE.
A basic deployment would preferably require a Linux Server (VM) with a docker engine installed.
You may download the latest docker engine on Docker website.
- Network access to pull a docker image from DNS: hub.docker.com (https:443)
- Outgoing network access to Akeyless SaaS Core Services via the following URLs:
https://console.akeyless.io https://vault.akeyless.io https://vault-ro.akeyless.io https://auth.akeyless.io https://auth-ro.akeyless.io https://kfm1.akeyless.io https://kfm1-ro.akeyless.io https://kfm2.akeyless.io https://kfm2-ro.akeyless.io https://kfm3.akeyless.io https://kfm3-ro.akeyless.io https://kfm4.akeyless.io https://kfm4-ro.akeyless.io https://audit.akeyless.io https://audit-ro.akeyless.io https://bis.akeyless.io https://bis-ro.akeyless.io https://gator.akeyless.io https://gator-ro.akeyless.io amqps://mq.akeyless.io tcp://log.akeyless.io:9997
Outgoing network access to Akeyless SaaS Core Services via the following IP's:
Akeyless Services Description
The following table describes the main functionality of Akeyless micro-services:
Akeyless SaaS platform.
Vault : https://vault.akeyless.io
User Account Management, managing user account, items and roles.
Auth : https://auth.akeyless.io
Akeyless Authentication service.
Audit : https://audit.akeyless.io
Audit log main service, enables log forwarding from GW & Bastion.
BIS : https://bis.akeyless.io
Billing infrastructure service.
Gator : https://gator.akeyless.io
Main service to sync gateways instances, and connections with Akeyless SaaS.
MQ : amqps://mq.akeyless.io
Message queue between Akeyless micro-services.
Key Fragments Services, enabling full DFC encryption.
Logs : tcp://log.akeyless.io:9997
GW logs, mainly to be reflected during failure scenarios.
Updated about 12 hours ago