Akeyless SaaS Core Services
The Akeyless Gateway is a stateless Docker container, provided as a standalone or as a cluster. To function correctly, it requires public network connectivity to the Akeyless SaaS core services (see the table below).
A basic Gateway deployment requires a server with a Docker engine installed. You may download the latest Docker engine on Docker website. You'll need public network access enabled on port 443 to pull a Docker image from the hub.docker.com.
The following table describes the main functionality of Akeyless micro-services:
| Service Name | IP | Port | Description |
|---|---|---|---|
| Console: https://console.akeyless.io | 52.223.11.194, 35.71.185.167, 52.223.35.208, 35.71.147.131, 15.197.228.204, 3.33.247.128 | 443 | Akeyless SaaS platform |
| Vault : https://vault.akeyless.io https://vault-ro.akeyless.io | 52.223.11.194, 35.71.185.167, 52.223.35.208, 35.71.147.131, 15.197.228.204, 3.33.247.128 | 443 | User Account Management (UAM), managing user accounts, items, and roles |
| Auth : https://auth.akeyless.io https://auth-ro.akeyless.io | 52.223.11.194, 35.71.185.167, 52.223.35.208, 35.71.147.131, 15.197.228.204, 3.33.247.128 | 443 | Akeyless Authentication service |
| Audit : https://audit.akeyless.io https://audit-ro.akeyless.io | 52.223.11.194, 35.71.185.167, 52.223.35.208, 35.71.147.131, 15.197.228.204, 3.33.247.128 | 443 | Audit log main service, enables log forwarding from GW & Bastion |
| BIS : https://bis.akeyless.io https://bis-ro.akeyless.io | 52.223.11.194, 35.71.185.167 | 443 | Billing Infrastructure Service (BIS) |
| Gator : https://gator.akeyless.io https://gator-ro.akeyless.io | 52.223.11.194, 35.71.185.167, 52.223.35.208, 35.71.147.131, 15.197.228.204, 3.33.247.128 | 443 | Main service to sync gateways instances, and connections with Akeyless SaaS |
| MQ : amqps://mq.akeyless.io | 52.223.11.194, 35.71.185.167 | 5671 | Message queue between Akeyless micro-services |
| KFM: 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 | 52.223.11.194, 35.71.185.167, 52.151.230.203, 52.223.35.208, 35.71.147.131, 15.197.228.204, 3.33.247.128 | 443 | Key Fragments Services, enabling full DFC encryption |
| Public Gateway: https://rest.akeyless.io https://api.akeyless.io | 15.197.223.248, 3.33.244.138 | 443 | Optional Public Gateway rest API v1\v2 |
| Public HVP: https://hvp.akeyless.io | 15.197.223.248, 3.33.244.138 | 443 | Optional Public HVP endpoint |
| Logs : tcp://log.akeyless.io:9997 tcp://log.akeyless.io:9443 | 35.192.171.171 | 9997, 9443 | GW logs, mainly to be reflected during failure scenarios |
| https://akeyless-cli.s3.us-east-2.amazonaws.com | N\A | 443 | S3 bucket to download & update Akeyless CLI versions |
| https://akeylessservices.s3.us-east-2.amazonaws.com | N\A | 443 | S3 bucket to download & update Akeyless official binaries. e.g. Gateway |
| https://artifacts.site2.akeyless.io | 34.149.100.205 | 443 | Optional Akeyless official artifacts endpoint. Relevant when working with whitelisted IP range |
Note
When using proxy services, you can use https://sqs.us-east-2.amazonaws.com instead of classic MQ services.
Updated 12 days ago