The Aembit Edge Components can be deployed as a virtual appliance. This allows more than one Client Workload to use the same set of Edge Components. Aembit provides an OVA file suitable for deployment on a VMWare ESXi server.
Limitations
Section titled “Limitations”The virtual appliance deployment model is limited in the following ways:
- Only explicit steering is supported.
- Only HTTP(S) and Snowflake traffic is supported.
- Client Workloads may only be identified by the source IP.
- There are no Trust Providers currently compatible.
- Of the current Access Conditions, only the Aembit Time Condition is compatible.
Deployment Instructions
Section titled “Deployment Instructions”For VM-creation details for your specific ESXi version, consult the vSphere Documentation.
- Download the virtual appliance OVA from the Virtual Appliance Releases.
- Upload the OVA to your ESXi server.
- Create a new virtual machine, entering the appropriate configuration values. See the below Configurations section for details.
- Deploy the virtual machine.
- Log into the virtual machine. For login details, please contact your Aembit representative.
Device Code Expiration
Section titled “Device Code Expiration”In the event your device code expires before installation is complete, please contact your Aembit representative for assistance.
Configurations
Section titled “Configurations”There are two fields that must first be populated for a virtual appliance deployment to succeed:
AEMBIT_TENANT_IDAEMBIT_DEVICE_CODE
The virtual appliance deployment uses a subset of the virtual machine deployment options. See the virtual machine deployment page for a detailed discussion of these options.
Configure the proxy configuration of your Client Workloads to send traffic to the virtual appliance. For more information on configuring the proxy settings of your Client Workload, see Explicit Steering.