Add Terraform example for AWS ECS deployment - #581
Conversation
Included a note about a Terraform example for provisioning ECS Fargate deployments, highlighting its use of Amazon RDS for Postgres and additional observability tools. Updated the resources section to include the Terraform self-host example link.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| [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. |
There was a problem hiding this comment.
This is a community-maintained repo (under powersync-community, not powersync-ja), but the note reads as if it's an official, supported deployment path. Worth making that distinction explicit here, e.g. "A community-maintained Terraform example...", so readers don't assume the same support level as the guide itself.
There was a problem hiding this comment.
At this stage, it is officially maintained by PowerSync
|
|
||
| - [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). |
There was a problem hiding this comment.
This restates the same RDS-for-Postgres-vs-MongoDB point already made in the Note near the top of the page, and it's the only entry in this list written as multiple full sentences rather than a short phrase like the other two entries. Consider trimming to something like "Infrastructure-as-code for a full ECS Fargate deployment with an expanded observability stack (Amazon Managed Prometheus, Managed Grafana, OpenSearch)." and letting the Note above carry the database-default detail.
There was a problem hiding this comment.
I thought about this, but I prefer to restate it just in case
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
1 participant
Asked Claude where and how best to add the note, then edited it afterwards.