Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions maintenance-ops/self-hosting/aws-ecs.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,10 @@

[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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At this stage, it is officially maintained by PowerSync

</Note>

## Prerequisites

Before deploying PowerSync on AWS ECS, ensure you have:
Expand Down Expand Up @@ -1299,3 +1303,4 @@

- [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).

Check warning on line 1306 in maintenance-ops/self-hosting/aws-ecs.mdx

View check run for this annotation

Mintlify / Mintlify Validation (powersync) - vale-spellcheck

maintenance-ops/self-hosting/aws-ecs.mdx#L1306

Did you really mean 'Grafana'?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought about this, but I prefer to restate it just in case

Loading