diff --git a/maintenance-ops/self-hosting/aws-ecs.mdx b/maintenance-ops/self-hosting/aws-ecs.mdx
index 6632a7b3..6f873ab1 100644
--- a/maintenance-ops/self-hosting/aws-ecs.mdx
+++ b/maintenance-ops/self-hosting/aws-ecs.mdx
@@ -6,6 +6,10 @@ description: "Deploy the self-hosted PowerSync Service on AWS ECS with Fargate."
 
 [AWS ECS](https://aws.amazon.com/ecs/) with Fargate provides a serverless container orchestration platform for running PowerSync without managing servers.
 
+<Note>
+A [Terraform example](https://github.com/powersync-community/terraform-self-host-aws) is available to provision a comparable ECS Fargate deployment as infrastructure-as-code. Its default architecture uses Amazon RDS for Postgres for both the source and bucket storage databases, rather than the MongoDB bucket storage used in this guide.
+</Note>
+
 ## Prerequisites
 
 Before deploying PowerSync on AWS ECS, ensure you have:
@@ -1299,3 +1303,4 @@ This approach is simpler but less responsive to connection spikes — CPU may no
 
 - [AWS ECS Best Practices](https://docs.aws.amazon.com/AmazonECS/latest/bestpracticesguide/) - AWS's official guide covering security, networking, monitoring, and performance optimization for ECS deployments
 - [Self-Host Demo Repository](https://github.com/powersync-ja/self-host-demo) - Working example implementations of PowerSync self-hosting across different platforms and configurations
+- [Terraform Self-Host Example (AWS)](https://github.com/powersync-community/terraform-self-host-aws) - Infrastructure-as-code for a full ECS Fargate deployment. Note that it defaults to Amazon RDS for Postgres for both the source and bucket storage databases, and adds a richer observability stack (Amazon Managed Prometheus, Managed Grafana, and OpenSearch).