-
Notifications
You must be signed in to change notification settings - Fork 18
Add Terraform example for AWS ECS deployment #581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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. | ||
| </Note> | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| Before deploying PowerSync on AWS ECS, ensure you have: | ||
|
|
@@ -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). | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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 |
||
There was a problem hiding this comment.
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, notpowersync-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.
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