SaaS App Migration from Anything.com to AWS

We run a production SaaS app currently hosted on the Anything platform. We want to migrate it to AWS while keeping: all existing users + logins working (right now it's only me as the super-admin) all existing Stripe subscriptions plans that I have setup all Postgres data intact existing webhooks/integrations working We plan to keep the same domain and just switch hosting behind it. Current scale: ~0 paying users today, growth target 2,000+; possible peak ~400 concurrent users. Much further in the future but want it setup correctly now. Tech Summary (current) React web app + backend API routes (Node-based) Postgres database (production data) Auth: email/password (existing users in Postgres auth tables) Billing: Stripe subscriptions + webhook handling Integrations: Meta (OAuth connect + sync endpoints) HighLevel (webhook receiver using tokenized route like /api/webhooks/highlevel/[token]) Email: Resend What we want built on AWS We’re flexible on exact AWS architecture, but it must be reliable and maintainable. Preferred patterns: ECS Fargate + RDS Postgres (ideal) or EC2 + Docker + Nginx + RDS (also acceptable) (We are not looking for a “Lambda everything” rewrite unless you strongly justify it.) Core deliverables AWS infrastructure + deployment Deploy the app to AWS (ECS/EC2) with a repeatable deploy process Configure environment variables securely (SSM Parameter Store or Secrets Manager) Production-ready SSL (ACM) and HTTP → HTTPS Logging (CloudWatch) and basic alarms for 5xx/errors Database migration Migrate Postgres from Anything to AWS RDS (or your recommended managed Postgres) Minimal downtime plan (maintenance window + final cutover) Verification steps (row counts and spot checks on key tables) Keep Stripe subscriptions + webhooks working Ensure all Stripe billing continues with the same Stripe account Confirm webhooks are delivered and processed correctly after cutover Ensure webhook processing is safe against duplicates (idempotency) Keep integrations working Meta OAuth callback/redirects remain valid (since we keep the same domain) HighLevel webhook receiver continues to work on the same URL paths Confirm background/sync routes function post-migration Domain cutover Keep our domain the same (DNS cutover) Plan for DNS propagation issues (avoid split-traffic problems) Provide rollback plan if something goes wrong Definition of done (acceptance criteria) Users can sign in normally and see their existing data Stripe subscriptions keep billing; no customer forced to re-subscribe Webhooks (Stripe + HighLevel) successfully deliver to AWS and are processed Core pages load in reasonable time (no obvious regressions) We have basic monitoring/logs and a documented deploy process What we will provide Access to the codebase Current environment variables list (keys only; values provided securely) Access to Stripe dashboard (or we can screen share while you guide changes) Domain/DNS access (or we can do DNS changes ourselves with your instructions) A short maintenance window for final DB cutover (if needed) Required experience AWS deployments for Node/React apps (ECS Fargate or EC2 + Docker) RDS Postgres migration experience (pg_dump/restore, downtime planning) Stripe subscriptions + webhook handling in production Strong understanding of DNS cutovers + SSL certs Security best practices (no secrets in Git, least-privilege IAM) Nice to have Terraform / IaC Experience with background jobs/queues (if needed later) Performance tuning for Postgres queries under growth Timeline Looking to complete initial migration within 1–2 weeks, depending on your plan and availability. Ongoing support after launch is a plus. To apply, answer these questions Which approach would you use and why: ECS Fargate vs EC2 vs Elastic Beanstalk? How would you migrate Postgres with minimal downtime? How do you handle webhook idempotency (Stripe event replay / duplicate deliveries)? Have you migrated an app where the domain stayed the same but hosting changed? Any pitfalls?

ID do Projeto: 40145449