Vercel and AWS

Ship on the AWS primitives you already trust and run, with deployment, scaling, and network isolation handled for you.

Talk to an expert Procure on AWS Marketplace

Get the benefits of both AWS and Vercel

Competency-backed delivery, procurement through your existing AWS agreement, and native integration with the accounts you already run.

AWS Competency status. Vercel holds AWS Competency status across four verticals: Retail, CPG, Media + Entertainment, Gen AI, plus a Strategic Collaboration Agreement for AI-enabled developer tooling.
Procure on AWS Marketplace. Vercel is available on the AWS Marketplace, simplifying your software buying experience. Get in touch with us to create your AWS private offer.
Integrate with the accounts you already run. Connect to AWS with Secure Compute, configure your account to trust Vercel’s OIDC, and use Terraform to deploy on Vercel from your CI/CD pipeline.

Teams building on Vercel and AWS

Bring your own cloud

Read the docs

Customer-owned cloud boundary

Placement: Customer-managed AWS account
Managed by: Customer-managed account

Workloads run inside your own AWS account. Compute and data never leave your cloud boundary.

Functions execute in your AWS account
Vercel runtime invoked via AWS Lambda API
Encrypted N1 tunnel callback for responses

The teams this works best for

Teams that need compute and data to never leave their AWS account.

BYOC is for strict security requirements

BYOC generally does not add capabilities for engineering teams. Choose it when compliance or data-residency requirements mean workloads must run in your own AWS account. BYOC moves infrastructure outside Vercel’s managed boundary and requires more upkeep than the fully managed tiers.

AWS databases, provisioned from Vercel

Browse AWS databases Read the announcement

Provisioned from the dashboardPick Aurora PostgreSQL, Aurora DSQL, or DynamoDB, choose a region, and Vercel injects the connection variables into your project.
Keyless connectionsOIDC assumes your AWS role and mints short-lived IAM tokens on each connection, so no database passwords are ever stored.
64ms across 50 round tripsFunctions and databases share a data center. Aurora ran 50 sequential round trips in 64ms; other providers took 109ms and 150ms.