EC2
Overview
Deploying the Upwind components on ECS using the EC2 launch type involves several steps that leverage the power and flexibility of AWS services to manage and scale containerized applications. In this setup, you can run the Upwind components as containerized services. Specifically, the Upwind Sensor can be configured as a daemon service in the host network mode, ensuring it has the necessary visibility and access to monitor and manage the network traffic efficiently across your EC2 instances.
Components
Below is a table detailing the Upwind components and their roles in an ECS cluster using the EC2 launch type:
| Upwind Sensor | Collects data on network traffic and system metrics across your EC2 instances. It operates in host network mode to ensure comprehensive visibility and efficient data gathering. |
| Upwind Scanner | Performs in-depth analysis of network traffic and application behavior, identifying potential vulnerabilities and anomalies. It enhances security by continuously assessing the environment for threats. |
| Upwind Cluster Manager | Orchestrates the deployment and operation of Upwind components across the ECS cluster. It coordinates tasks, ensuring that the sensor data is efficiently processed and analyzed without the need for direct infrastructure management. |
Installation
The installation choices available for deploying the Upwind components on EC2 are as follows:
- Terraform (Recommended)
- AWS CloudFormation
Upgrade
For instructions on upgrading Upwind components on an ECS cluster using the EC2 launch type, refer to the Upgrade guide.
Troubleshooting
If you encounter issues during deployment or operation, consult the Troubleshooting guide for solutions and best practices.