Aembit provides many different deployment options you can use to deploy Aembit Edge Components in your environment. Each of these options provide similar features and functionality. The steps for each of these options, however, are specific to the deployment option you select.
This page describes the process to deploy Agent Proxy to a Linux virtual machine (VM).
Supported versions
Section titled “Supported versions”Use the following table to make sure that Aembit supports the operating system and platform you’re deploying to your VM:
Operating system | Edge Component versions |
---|---|
Ubuntu 20.04 LTS | Agent Proxy v1.11.1551+ |
Ubuntu 22.04 LTS | Agent Proxy v1.11.1551+ |
Red Hat 8.9 * | Agent Proxy v1.11.1551+ |
* See How to configure Agent Proxy on SELinux or RHEL for more info.
Install Agent Proxy
Section titled “Install Agent Proxy”To install Agent Proxy on Linux, follow these steps:
-
Download the latest Agent Proxy Release.
-
Log on to the VM with your username:
Terminal window ssh -i <path/to/your/ssh/key> <your-username or remote-host>@<hostname> -
Download the latest released version of Agent Proxy. Make sure to include the
<version_number>
in the command:Terminal window wget https://releases.aembit.io/agent_proxy/<version_number>/linux/amd64/aembit_agent_proxy_linux_amd64_<version_number>.tar.gz -
Unpack the archive using the correct version number in the command:
Terminal window tar xf aembit_agent_proxy_linux_amd64_<version_number>.tar.gz -
Navigate to the unpacked directory:
Terminal window cd aembit_agent_proxy_linux_amd64_<version_number> -
Run the Agent Proxy installer, making sure to replace
<agent-controller-host>
address:Terminal window sudo AEMBIT_AGENT_CONTROLLER=http://<agent-controller-host>:5000 ./installOptionally, add any other Agent Proxy environment variables reference in the format
ENV_VAR_NAME=myvalue
. -
(Optional) You may optionally use the additional installation environment variable
AEMBIT_DOCKER_CONTAINER_CIDR
. This variable may be set to the CIDR block of the Docker container bridge network to allow handling workloads running in containers on your VM.Your Client Workloads running on your virtual machine should now be able to access server workloads.
Agent Proxy environment variables
Section titled “Agent Proxy environment variables”For a list of all available environment variables for configuring the Agent Proxy installer, see Agent Proxy environment variables reference.
Uninstall Agent Proxy
Section titled “Uninstall Agent Proxy”Run the following command to uninstall Agent Proxy from Linux VMs:
sudo ./uninstall
Access Agent Proxy logs
Section titled “Access Agent Proxy logs”To access logs on your Agent Proxy, select the following tab for your operating system:
Linux handles Agent Proxy logs with journald
.
To access Agent Proxy logs, run:
journalctl --namespace aembit_agent_proxy
Older versions of journald
do not support namespaces.
If the preceding command does not work, you can use the following command:
journalctl --unit aembit_agent_proxy
For more information about Agent Proxy log levels, see Agent Proxy log level reference
Optional configurations
Section titled “Optional configurations”The following sections describe optional configurations you can use to customize your Agent Proxy installation:
Configuring AWS RDS certificates
Section titled “Configuring AWS RDS certificates”To install all the possible CA Certificates for AWS Relational Database Service (RDS) databases, see AWS RDS Certificates.
Configuring TLS Decrypt
Section titled “Configuring TLS Decrypt”To use TLS decryption on your virtual machine, download the Aembit CA certificate and add it to your trusted CAs. See About TLS Decrypt for detailed instructions on how to use and configure TLS decryption on your virtual machine.
Resource Set deployment
Section titled “Resource Set deployment”If you want to deploy a Resource Set using the Agent Proxy Virtual Machine Installer, you need to specify the
AEMBIT_RESOURCE_SET_ID
environment variable during the Agent Proxy installation.
See Edge Component environment variables
reference for details.
This configuration enables the Agent Proxy to support Client Workloads in this Resource Set. For more info, see Resource Sets overview.