Once a Resource Set has been created, and roles and responsibilities have been assigned, the Agent Proxy component needs
to be configured and deployed to work with the specific AEMBIT_RESOURCE_SET_ID Agent Proxy environment
variable.
All Aembit deployment mechanisms are supported, including:
- Kubernetes
- Terraform ECS Module
- Agent Proxy VM Installer
- AWS Lambda
Kubernetes deployment
Section titled “Kubernetes deployment”To deploy a Resource Set using Kubernetes, you need to add the aembit.io/resource-set-id annotation to your Client
Workload deployments.
For more information on how to deploy Resource Sets using Kubernetes, please see the Kubernetes Deployment page.
Terraform ECS module deployment
Section titled “Terraform ECS module deployment”To deploy a Resource Set using the Terraform ECS Module, you need to provide the AEMBIT_RESOURCE_SET_ID environment
variable in the Client Workload ECS Task.
For more detailed information on how to deploy a Resource Set using the Terraform ECS Module, please see the Terraform Configuration page.
Agent Proxy VM installer deployment
Section titled “Agent Proxy VM installer deployment”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.
For more information on how to deploy a Resource Set using the Agent Proxy Virtual Machine Installer, please see the Virtual Machine Installation page.
AWS Lambda deployment
Section titled “AWS Lambda deployment”To deploy a Resource Set using an AWS Lambda Container, you need to specify the AEMBIT_RESOURCE_SET_ID environment
variable to your Client Workload.
For more information on AWS Lambda deployment environments, see the AWS Lambda function and AWS Lambda container pages.