AW3 - Multi-Cloud Hosting Platform
    Migrate · Vercel → AWS

    Migrate from Vercel to AWS
    with Amplify Hosting.

    AWS's closest equivalent to Vercel's git-push workflow is Amplify Hosting, which builds from your repository, deploys previews per pull request and runs Next.js server-side rendering. Here's how the pieces map, and what doesn't carry over.

    Facts checked against each provider's own pages

    The short answer

    Connect the repository to AWS Amplify Hosting, move build settings into amplify.yml[1], recreate environment variables, enable web previews for pull requests[2], then shift traffic gradually before moving DNS. Check your Next.js version and features first: Amplify supports Next.js 12 through 15 and doesn't support streaming, on-demand ISR or Edge API routes[3].

    Mapping

    What maps to what

    On VercelOn AWSNotes
    Git-connected projectAmplify Hosting app connected to the repoAmplify Hosting compute manages SSR for Next.js 12–15[3].
    Preview deploymentsAmplify web previewsEach pull request is deployed to a unique preview URL[2].
    vercel.json build settingsamplify.ymlAmplify build settings live in amplify.yml at the repo root[1].
    Vercel Functions / API routesAmplify SSR compute, or AWS LambdaAPI routes are supported on Amplify; standalone functions can run on Lambda, which scales to zero when idle[4].
    Environment variables per environmentAmplify environment variablesEnvironment variables are listed as supported for Next.js SSR on Amplify[3].
    Vercel Marketplace storage (Neon, Upstash, Supabase…)Keep the same provider, or move to RDS / DynamoDBVercel's storage docs list these as Marketplace partners[5], so the databases aren't tied to Vercel. AWS's own options include RDS and Aurora[6].
    Fast Data TransferInternet egressAWS: 100 GB/month free, then $0.09/GB for the first 10 TB from US East[7].
    Steps

    The migration, step by step

    1. 01

      Check framework support

      Confirm your Next.js version is 12–15 and list any use of streaming, on-demand ISR, Edge API routes, middleware on static assets or images, or unstable_after: Amplify lists those as unsupported[3]. If you depend on them, plan code changes or a different AWS target (containers on ECS or Fargate).

    2. 02

      Export settings from Vercel

      Write down build command, output directory, Node version, redirects, rewrites and headers from vercel.json[8], and export environment variables for each environment (Vercel scopes them to Local, Preview and Production)[9].

    3. 03

      Create the Amplify app

      Connect the repository in Amplify Hosting and commit an amplify.yml with your build settings[1]. Add environment variables, then let Amplify build the main branch.

    4. 04

      Turn on previews

      Enable web previews so each pull request gets its own URL[2], matching the Vercel review workflow.

    5. 05

      Move platform rules into the app

      Platform-specific vercel.json rules don't carry over. Moving redirects and rewrites into next.config keeps them with the application; Cloudflare's Vercel migration guide recommends the same for its platform[10].

    6. 06

      Test on the Amplify domain, then cut over

      Run your test suite against the Amplify URL, then shift production traffic gradually (below) before changing DNS for the custom domain.

    Gotchas

    Things the docs warn about

    • Amplify lists Next.js streaming, on-demand ISR, Edge API routes (edge middleware isn't supported), running middleware on static assets and optimized images, and unstable_after as unsupported, and caps image optimization output at 4.3 MB[3].
    • The Amplify SSR page names Next.js 12 through 15. It doesn't mention Next.js 16, so check before upgrading[3].
    • AWS App Runner, another container option, stopped accepting new customers on 30 April 2026; AWS recommends ECS Express Mode instead[11].
    • Egress pricing changes shape: Vercel Pro includes 1 TB in its Flat Rate CDN tier[12], while AWS gives 100 GB/month free and then charges per GB[13].
    • Vercel applies environment variable changes only to new deployments[9]; if you edit variables on Vercel during the overlap, redeploy there too.
    Where AW3 Host fits

    Run both during cutover, then switch

    AW3 Host connects both your Vercel and AWS accounts, so the old and new deployments run side by side from one dashboard and API instead of a big-bang switch.

    Weighted routing sends a small share of traffic to AWS first (for example 5%, then 25%, 50% and 100%) while Vercel serves the rest. Health checks every 60 seconds watch both; if the AWS side fails, failover moves traffic back automatically, and rollback to the previous release is one step. Daily cost sync shows what each provider costs during the overlap, and budget policies alert you if the double-running period gets expensive. Secrets for both are stored encrypted per environment.

    When AWS has carried all traffic cleanly for long enough that you no longer need the fallback, point DNS at it for good and decommission Vercel.

    Reference

    Vercel vs AWS at a glance

    Vercel vs AWS at a glance
    VercelAWS
    CategoryFrontend platformHyperscaler
    Pricing modelPer-seat plan plus metered usage; Pro's $20/mo fee includes one deploying seat and $20 of usage credit[14]Pay as you go per service; no long-term contract required[19]
    Compute billing granularityActive CPU metered on actual CPU time and billed per CPU-hour; provisioned memory per GB-hour while an instance is alive[15]EC2: per second with a 60-second minimum (Linux, Windows, RHEL, Ubuntu Pro); SLES by the full hour[13]
    Internet egress (first paid tier)$0.15/GB on-demand Fast Data Transfer in US regions (iad1); $0.15–$0.35/GB by region[16]$0.09/GB for the first 10 TB/month from US East (N. Virginia), then $0.085, $0.07, $0.05[7]
    Regions / locations19 compute regions; 126 points of presence[17]39 regions, 124 Availability Zones[20]
    Deploy modelGit push (GitHub, GitLab, Bitbucket) auto-deploys, or the Vercel CLI; OCI containers in beta[18]VMs (EC2), containers (ECS, EKS, Fargate), functions (Lambda), git-connected hosting (Amplify)[21]
    Persistent volumes—Yes: Amazon EBS block volumes for EC2[22]
    Config filevercel.json (or vercel.toml / vercel.ts)[8]amplify.yml for Amplify Hosting; otherwise infrastructure as code (CloudFormation, CDK, SAM)[1]
    FAQ

    Frequently asked questions

    What is the AWS equivalent of Vercel?
    AWS Amplify Hosting: it connects to a git repository, builds and deploys on push, creates preview URLs for pull requests and runs Next.js server-side rendering for versions 12 through 15.
    Does AWS Amplify support all Next.js features?
    No. Amplify's docs list Next.js streaming, on-demand ISR, Edge API routes, middleware on static assets and optimized images, and unstable_after as unsupported, and cap image optimization output at 4.3 MB.
    Is AWS cheaper than Vercel?
    It depends on traffic and compute. Vercel Pro is $20/month per deploying seat with 1 TB of transfer included; AWS is pay as you go with 100 GB of free egress a month, then $0.09/GB from US East.
    Sources

    Sources

    1. AWS Docs: Amplify build settings. https://docs.aws.amazon.com/amplify/latest/userguide/build-settings.html (checked 2026-11-16)
    2. AWS Docs: Amplify web previews. https://docs.aws.amazon.com/amplify/latest/userguide/pr-previews.html (checked 2026-11-16)
    3. AWS Docs: Amplify Next.js SSR support. https://docs.aws.amazon.com/amplify/latest/userguide/ssr-amplify-support.html (checked 2026-11-16)
    4. AWS Docs: What is AWS Lambda?. https://docs.aws.amazon.com/lambda/latest/dg/welcome.html (checked 2026-11-16)
    5. Vercel: Storage. https://vercel.com/docs/storage (checked 2026-11-16)
    6. AWS: Amazon RDS. https://aws.amazon.com/rds/ (checked 2026-11-16)
    7. AWS Price List: AWSDataTransfer offer file, us-east-1. https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AWSDataTransfer/current/us-east-1/index.json (checked 2026-11-16)
    8. Vercel: Project configuration. https://vercel.com/docs/project-configuration (checked 2026-11-16)
    9. Vercel Docs: Environment variables. https://vercel.com/docs/environment-variables (checked 2026-11-16)
    10. Cloudflare Docs: Migrate Next.js from Vercel to Workers. https://developers.cloudflare.com/workers/static-assets/migration-guides/vercel-to-workers/nextjs/ (checked 2026-11-16)
    11. AWS: App Runner. https://aws.amazon.com/apprunner/ (checked 2026-11-16)
    12. Vercel: Flat Rate CDN. https://vercel.com/docs/pricing/flat-rate-cdn (checked 2026-11-16)
    13. AWS: EC2 On-Demand pricing. https://aws.amazon.com/ec2/pricing/on-demand/ (checked 2026-11-16)
    14. Vercel: Pro plan. https://vercel.com/docs/plans/pro-plan (checked 2026-11-16)
    15. Vercel: Functions usage and pricing. https://vercel.com/docs/functions/usage-and-pricing (checked 2026-11-16)
    16. Vercel: Regional pricing, iad1. https://vercel.com/docs/pricing/regional-pricing/iad1 (checked 2026-11-16)
    17. Vercel: Regions. https://vercel.com/docs/regions (checked 2026-11-16)
    18. Vercel: Environments. https://vercel.com/docs/deployments/environments (checked 2026-11-16)
    19. AWS: Pricing. https://aws.amazon.com/pricing/ (checked 2026-11-16)
    20. AWS: Global infrastructure. https://aws.amazon.com/about-aws/global-infrastructure/ (checked 2026-11-16)
    21. AWS Docs: What is Amazon ECS?. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html (checked 2026-11-16)
    22. AWS: Amazon EBS. https://aws.amazon.com/ebs/ (checked 2026-11-16)
    Public beta

    Your next deploy
    goes everywhere.

    Connect a provider, point a service at it, and ship. Add the second provider when you're ready.

    No card needed · Free tier · Pay as you go after that