Skip to content

The matrices on this page detail the compatible deployment types for application protocols. The matrices also cover Aembit features such as Client Workload Identifiers, Agent Controller Trust Providers, Agent Proxy Trust Providers, and Conditional Access. The matrices list the operating systems for VMs that Aembit supports. The CLI Support section includes the operating systems and Access Policy features that the Aembit CLI supports. The SDK support section covers Trust Providers by language.

Aembit Edge supports multiple types of deployments:

  • Kubernetes

  • AWS Elastic Container Service (ECS) Fargate

  • Virtual Machines (Linux, Windows, Docker-compose)

  • AWS Lambda (function, container)

  • Virtual Appliance (VMware)

IconMeaning
Supported
Not supported
⚪️Not applicable
Application ProtocolsKubernetesAWS EKS FargateAWS ECS FargateVirtual Machine (Linux)Virtual Machine (Windows)Virtual ApplianceDocker-compose on VMsAWS Lambda
HTTP 1.1
Postgres 3.0
MySQL 10
Redis RESP2
Redis RESP3
Snowflake SDK (HTTP-based)
Snowflake REST API (HTTP-based)
Amazon Redshift 3.0
Oracle Database✅*

* Oracle Database on Kubernetes requires transparent steering configured for the Oracle database host.

Client Workload IdentifiersKubernetesAWS EKS FargateAWS ECS FargateVirtual Machine (Linux)Virtual Machine (Windows)Virtual ApplianceDocker-compose on VMsAWS Lambda
Aembit Client ID
AWS Account ID✅*✅*✅*
AWS EC2 Instance ID⚪️⚪️✅*✅*✅*
AWS ECS Task Family⚪️⚪️⚪️⚪️⚪️⚪️⚪️
AWS Region✅*✅*✅*
AWS Subscription ID✅*✅*✅*
AWS VM ID✅*✅*✅*⚪️
Hostname
Kubernetes Pod name⚪️⚪️⚪️⚪️⚪️⚪️
Kubernetes Pod name prefix⚪️⚪️⚪️⚪️⚪️⚪️
Process Command Line **
Process Name **
Process Path **
Process User Name **
Source IP
AWS Lambda ARN⚪️⚪️⚪️⚪️⚪️⚪️⚪️

* These Client Workload identifiers are available for their respective cloud platforms only.
** Before using process-based identifiers, you must enable them in Agent Proxy first. See Process Command Line, Process Name, Process Path, and Process User Name for details

Trust ProvidersKubernetesAWS EKS FargateAWS ECS FargateVirtual MachineVirtual ApplianceDocker-compose on VMsAWS Lambda
AWS Role⚪️⚪️
AWS Metadata Service✅*✅*⚪️⚪️
Azure Instance Metadata Service✅*⚪️⚪️✅*⚪️⚪️
GCP Identity Token✅*⚪️⚪️✅*⚪️⚪️
Kubernetes Service Account⚪️⚪️⚪️⚪️⚪️
Kerberos⚪️⚪️⚪️⚪️⚪️⚪️⚪️

* Aembit tailors the Trust Providers available in Kubernetes and VM environments specifically for their respective cloud platforms.

Trust ProvidersKubernetesAWS EKS FargateAWS ECS FargateVirtual Machine (Linux)Virtual Machine (Windows)Virtual ApplianceDocker-compose on VMsAWS Lambda
AWS Role✅**✅**
AWS Metadata Service✅*✅*✅*✅*
Azure Instance Metadata Service✅*⚪️⚪️✅*✅*✅*⚪️
GCP Identity Token⚪️⚪️⚪️⚪️
Kubernetes Service Account⚪️⚪️⚪️⚪️⚪️⚪️
Kerberos⚪️

* Aembit tailors the Trust Providers available in Kubernetes and VM environments specifically for their respective cloud platforms.
** The AWS Role Trust Provider supports only EC2 instances with an attached IAM role.

Access ConditionsKubernetesAWS EKS FargateAWS ECS FargateVirtual Machine (Linux)Virtual Machine (Windows)Virtual ApplianceDocker-compose on VMsAWS Lambda
CrowdStrike
Wiz
Time
GeoIP

The following sections contain the operating system versions that Aembit Agent Proxy and Agent Controller support on VMs

Linux DistributionVersion
Ubuntu20.04
Ubuntu22.04
Ubuntu24.04
Red Hat8.6
Red Hat8.9
Red Hat9.3
Windows EditionVersion
Windows Server2019
Windows Server2022

You can use the Aembit CLI with the following operating system versions:

Linux DistributionVersion
Ubuntu22.04
Red Hat9.3
Windows EditionVersion
Windows10
Windows Server2019
Windows Server2022

The Aembit CLI is compatible with the following CI/CD runners:

For more information, see GitHub runners documentation.

GitHub Runner
ubuntu-latest
windows-latest

For more information, see GitLab runners documentation.

GitLab Runner
saas-linux-small-amd64
saas-linux-medium-amd64
saas-linux-large-amd64
saas-linux-small-arm64
saas-linux-medium-arm64
saas-linux-large-arm64
saas-windows-medium-amd64

The Aembit CLI supports the following deployment models:

The Aembit CLI supports the following Client Workload Identifiers:

The Aembit CLI supports the following Trust Providers:

The Aembit CLI supports the following Access Conditions:

The Edge SDK is available for TypeScript and Python, and the available Trust Providers differ between the two languages. This table lists every Trust Provider type the Edge API accepts and shows SDK support for each by language.

Trust ProvidersTypeScriptPython
AWS Metadata Service Trust Provider
AWS Role Trust Provider
Azure Instance Metadata Service Trust Provider✅*
GCP Identity Token Trust Provider
GitHub Trust Provider
GitLab Trust Provider
OIDC ID Token Trust Provider
Terraform Cloud Trust Provider
Kubernetes Service Account Trust Provider

* The Azure Instance Metadata Service provider is available in the TypeScript SDK, but Edge API support for that flow is still in progress.