<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/bce1c2a4bda54e3cb85738fe74dd6b8c&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/bce1c2a4bda54e3cb85738fe74dd6b8c-773bb54ae0f66875.gif</thumbnail_url><duration>263.976</duration><title>End to End AWS ECS Analytics Deployment</title><description>This Loom presents an end to end production analytics platform architecture on AWS ECS Fargate that Tahmid deployed and managed entirely with Terraform. It covers the ECS service behind an application load balancer using an HTTPS listener with ACM termination and a health check at /api/heartbeat, with Fargate tasks and an RDS Postgres database running in private subnets and reaching the internet via a NAT gateway. For observability, CloudWatch collects task and database logs, while Terraform state is stored in S3 with state locking and authenticated via GitHub Actions using OIDC to avoid long lived credentials. The Dockerfile uses a multi stage build to produce a lean runtime image, and the Terraform setup is fully modular with a separate bootstrap stack provisioning ECR and the S3 backend.</description></oembed>