diff --git a/config/_default/menus/main.en.yaml b/config/_default/menus/main.en.yaml
index d4e253c1a05ae..86933399a60a1 100644
--- a/config/_default/menus/main.en.yaml
+++ b/config/_default/menus/main.en.yaml
@@ -5443,6 +5443,11 @@ menu:
       identifier: install_the_worker_commands
       parent: observability_pipelines_install_the_worker
       weight: 201
+    - name: ECS Fargate
+      url: observability_pipelines/install_the_worker/set_up_the_worker_in_ecs_fargate/
+      identifier: install_the_worker_ecs_fargate
+      parent: observability_pipelines_install_the_worker
+      weight: 202
     - name: Update Existing Pipelines
       url: observability_pipelines/update_existing_pipelines/
       parent: observability_pipelines
diff --git a/content/en/observability_pipelines/install_the_worker/set_up_the_worker_in_ecs_fargate.md b/content/en/observability_pipelines/install_the_worker/set_up_the_worker_in_ecs_fargate.md
new file mode 100644
index 0000000000000..d054116062139
--- /dev/null
+++ b/content/en/observability_pipelines/install_the_worker/set_up_the_worker_in_ecs_fargate.md
@@ -0,0 +1,107 @@
+---
+title: Set Up the Worker in ECS Fargate
+disable_toc: false
+---
+
+## Overview
+
+This document goes over one of the ways you can set up the Observability Pipelines Worker in ECS Fargate.
+
+## Setup
+
+The setup configuration for this example consists of a Fargate task, Fargate service, and a load balancer.
+
+{{< img src="observability_pipelines/worker_fargate_architecture.png" alt="An architecture diagram with logs going to an application load balancer, a OP Worker task, and the Fargate service" style="width:100%;" >}}
+
+## Configure the task definition
+
+[Create a task definition][1]. The task definition describes which containers to run, the configuration (such as the environment variables and ports), and the CPU and memory resources allocated for the task.
+
+Set the `DD_OP_SOURCE_*` environment variable according to the configuration of the pipeline and port mappings. `DD_OP_API_ENABLED` and `DD_OP_API_ADDRESS` are used to allow the load balancer to do health checks on the routing targets. The CPU and memory resources should be increased for the production usage.
+
+An example task definition:
+
+```json
+{
+  "family": "my-opw",
+  "containerDefinitions": [
+    {
+      "name": "my-opw",
+      "image": "datadog/observability-pipelines-worker",
+      "cpu": 0,
+      "portMappings": [
+        {
+          "name": "my-opw-80-tcp",
+          "containerPort": 80,
+          "hostPort": 80,
+          "protocol": "tcp"
+        }
+      ],
+      "essential": true,
+      "command": [
+        "run"
+      ],
+      "environment": [
+        {
+          "name": "DD_OP_API_ENABLED",
+          "value": "true"
+        },
+        {
+          "name": "DD_API_KEY",
+          "value": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
+        },
+        {
+          "name": "DD_SITE",
+          "value": "datadoghq.com"
+        },
+        {
+          "name": "DD_OP_API_ADDRESS",
+          "value": "0.0.0.0:8181"
+        },
+        {
+          "name": "DD_OP_SOURCE_HTTP_SERVER_ADDRESS",
+          "value": "0.0.0.0:80"
+        },
+        {
+          "name": "DD_OP_PIPELINE_ID",
+          "value": "e4454df2-f3a1-11ef-8654-test"
+        }
+      ],
+      "mountPoints": [],
+      "volumesFrom": [],
+      "systemControls": []
+    }
+  ],
+  "tags": [
+    {
+      "key": "PrincipalId",
+      "value": "AROAYYB64AB3JW3TEST"
+    },
+    {
+      "key": "User",
+      "value": "username@test.com"
+    }
+  ],
+  "executionRoleArn": "arn:aws:iam::60142xxxxxx:role/ecsTaskExecutionRole",
+  "networkMode": "awsvpc",
+  "volumes": [],
+  "placementConstraints": [],
+  "requiresCompatibilities": [
+    "FARGATE"
+  ],
+  "cpu": "256",
+  "memory": "512"
+}
+```
+
+## Configure the ECS service
+
+[Create an ECS service][2]. The service configuration sets the number of Worker replicas to run and the scaling policy. In this example, the scaling policy is set to target an average CPU utilization of 70% with a minimum of two replicas and a maximum of five replicas.
+
+## Set up load balancing
+
+[Configure an application load balancer][3] to target the group of Fargate tasks you defined earlier. Configure the health check against the Observability Pipelines' API port that was set in the task definition.
+
+[1]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-task-definition.html
+[2]: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/create-service-console-v2.html
+[3]: https://docs.aws.amazon.com/elasticloadbalancing/latest/application/create-application-load-balancer.html
\ No newline at end of file
diff --git a/static/images/observability_pipelines/worker_fargate_architecture.png b/static/images/observability_pipelines/worker_fargate_architecture.png
new file mode 100644
index 0000000000000..1855765012e04
Binary files /dev/null and b/static/images/observability_pipelines/worker_fargate_architecture.png differ