Fargate
Overview
Deploying the Upwind components on an Amazon ECS cluster using the AWS Fargate launch type simplifies operations by abstracting away the underlying server infrastructure, allowing you to focus solely on managing your applications. In this setup, you can run the Upwind components as containerized services without the need to manage the EC2 instances. Fargate automatically scales and manages the server infrastructure for you, providing an efficient and cost-effective way to deploy and maintain the Upwind components.
Components
Below is a table detailing the Upwind components and their roles in an ECS cluster deployment using the Fargate launch type:
| Upwind Tracer | Runs in each of your tasks, as a sidecar container or embedded in your application image, and monitors the processes and network connections of your application. It reports to the Cluster Manager. |
| Upwind Cluster Manager | Orchestrates the deployment and operation of Upwind components on Fargate. It coordinates tasks, ensuring that the tracer data is efficiently processed and analyzed without the need for direct infrastructure management. |
Installation
The installation choices available for deploying the Upwind components on an ECS cluster using the Fargate launch type are as follows:
- Terraform (Recommended)
- AWS CloudFormation
Upgrade
For instructions on upgrading Upwind components on an ECS cluster using the Fargate 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.