// Migration Guide · 2026
Migrate from AWS Amplify to Runsite
AWS Amplify pulls you into the wider AWS account, IAM and CloudFormation. Runsite reads your amplify.yml build spec and recreates the app in Frankfurt without an AWS account, IAM roles or US data residency.
- ~20 min
- typical migration
- No AWS account overhead
- keep your workflow
- Keep AWS Amplify running
- until you cut over
// the mental model
Every AWS Amplify concept has a Runsite home
Amplify wraps S3, CloudFront, Lambda and AppSync behind a build spec. Runsite maps the parts you actually use onto a single, account-free project.
version: 1
frontend:
phases:
preBuild:
commands:
- npm ci
build:
commands:
- npm run build
artifacts:
baseDirectory: dist
files:
- '**/*'- →Amplify build specaws amplifyWeb service build & start autopreBuild/build commands become your build command
- →S3 + CloudFront hostingaws amplifyStatic / SSR web service autoArtifacts served directly with a CDN in front
- →Lambda functions / APIaws amplifyAlways-on web service autoRun your API as a persistent service, no IAM wiring
- →DynamoDB / AppSync dataaws amplifyManaged PostgreSQL you doModel relationally; export and import once
- →Amplify env varsaws amplifyEnvironment variables autoNon-secret vars imported; secrets pasted once
// step by step
From AWS Amplify to live in the EU
Six steps. Most of them take seconds. AWS Amplify keeps serving traffic until you flip your DNS.
- 1
Create a Runsite project
~30 secSign in at runsite.app and create an empty project. No credit card, no sales call.
- 2
Connect your Git repo
GitHub · GitLab · BitbucketAuthorize GitHub, GitLab or Bitbucket. Runsite scans the selected branch for your amplify.yml and detects the stack automatically.
- 3
Review the detected setup
Full preview before provisioningRunsite lists every service, database and env var it found and how each maps onto a Runsite resource. Tweak build or start commands inline. Nothing is created yet.
- 4
Provision in Frankfurt
One click · eu-centralCreate the whole stack in one step. Cross-resource env vars are wired up for you, and you get fresh database and Redis credentials in the EU.
- 5
Drop in your secrets
Secrets stay out of GitSecret values are never read from your repo. Paste API keys and tokens once in the dashboard; they're encrypted at rest and never logged.
- 6
Push to go live
Live in < 2 mingit push and your app builds and deploys in the EU in under two minutes. Point your custom domain when ready. AWS Amplify keeps running until you cut over.
// no surprises
What moves on its own — and what you touch
Honest about the boundaries. The supported stack is recreated in one click; a short list needs a human, and Runsite flags every item.
Imported automatically
- ✓ Build spec phases (preBuild, build)
- ✓ Static / SSR artifacts
- ✓ Non-secret environment variables
- ✓ Auto-deploy on git push
You handle once
- → DynamoDB / AppSync data — model relationally and import
- → Lambda functions with stateful needs — recreate as services
- → Cognito auth — migrate users to your chosen provider
- → Secret environment variables — paste once after import
// aws amplify problems → runsite solutions
Common AWS Amplify frustrations — sound familiar?
Every AWS Amplify frustration, solved.
AWS Amplify problem
"AWS is too complex"
IAM roles, VPCs, CloudFormation, Amplify CLI — deploying a simple app requires DevOps knowledge.
Runsite solution
Git push and done
No AWS Console. No IAM. Connect your repo, pick EU, deploy. Two minutes.
AWS Amplify problem
"I can't understand my AWS bill"
Lambda invocations, API Gateway requests, S3 operations, data transfer — 20+ line items.
Runsite solution
Simple, fixed pricing
One plan. One monthly price. With a hard spending cap so you never overpay.
AWS Amplify problem
"Free tier expires after 12 months"
AWS free tier is a 12-month trial. After that, everything is billed.
Runsite solution
Free forever, no expiry
Runsite's free tier doesn't expire. Build side projects without watching a countdown.
// comparison
Runsite vs AWS Amplify
Side-by-side. No marketing fluff — just facts.
| Feature | Runsite | AWS Amplify |
|---|---|---|
| Complexity | ✓ Simple — git push deploy | AWS Console + IAM + CloudFormation |
| EU Data Centers | ✓ Frankfurt (eu-central) | ✓ eu-west, eu-central |
| GDPR Compliance | ✓ EU entity | Complex — requires AWS DPA |
| Backend Hosting | ✓ Full containers | Lambda functions |
| Pricing Clarity | ✓ Fixed plans | ✗ 20+ line items per invoice |
| Free Tier | ✓ Permanent | ✓ 12 months then paid |
// migration questions
Migrating from AWS Amplify, answered
Do I need an AWS account to use Runsite?
No. Amplify lives inside your AWS account with IAM roles and CloudFormation stacks. Runsite has none of that — you connect a git repo and deploy, with no AWS account, IAM policies or VPC setup.
Can Runsite use my amplify.yml build spec?
Yes. Runsite reads the build commands from your amplify.yml and uses them directly, so your build process carries over without a rewrite.
What about DynamoDB or AppSync data?
Runsite uses managed PostgreSQL, so you model your data relationally and import the exported records. This removes AWS-specific data lock-in at the cost of a one-time modeling step.
Is there downtime migrating from Amplify?
No. Your Amplify app keeps serving while you build and verify on Runsite, then you switch DNS to cut over and can roll back at any time.
Why migrate from AWS Amplify to Runsite?
Runsite removes AWS account complexity and US data residency, giving you a Frankfurt region for GDPR, predictable EUR pricing with hard spending caps and a permanent free tier.
Leave AWS Amplify behind
Bring your amplify.yml. We'll handle the rest — in Frankfurt.
Start your migration →