AWS databases are now available through the Vercel Marketplace and v0. Developers can provision Aurora PostgreSQL, Amazon DynamoDB, and Aurora DSQL from the Vercel dashboard with a guided setup flow and automatic project configuration. v0 can create and connect AWS accounts and databases to a project as it builds.
The integration removes manual IAM setup, credential wiring, and console switching from database provisioning. New AWS teams can start on a free starter plan with $100 in credits.
Same data centers, lower latency
Vercel functions already run on AWS infrastructure, so the database sits in the same data centers as the code that queries it. Vercel measured 50 sequential database round trips across providers:
Provider | 50 round trips (mean) | Per round trip |
AWS RDS (Aurora) | 64ms | ~1ms |
Provider B | 109ms | ~2ms |
Provider C | 150ms | ~3ms |
With an identical workload on identical Vercel functions, AWS RDS came out fastest by a wide margin — the result of having no network hop between code and data.
Building with v0
The simplest path is to tell v0 to use AWS databases while building. It provisions the database, creates or links an AWS account, and configures the connection, taking a project from prompt to working app with a production database.
A sample prompt demonstrates the flow:
Build me an internal employee dashboard for tracking contractor hours with an AWS Database
Prompt v0 to build your app and AWS provisions the database automatically
Because v0 handles the AWS setup, AWS infrastructure is reachable for builders who would otherwise avoid learning IAM policies — designers prototyping full-stack apps, founders validating ideas, and developers who simply want a production database.
Marketplace provisioning for existing projects
Teams that need more control over provisioning, or that are adding a database to an existing project, can install AWS databases from the Vercel Marketplace. Two flows exist, depending on whether an AWS account is already in place.
Create a new AWS account
Teams without an AWS account, or those preferring a simplified setup, can provision in one click from the Vercel dashboard: pick Aurora PostgreSQL, Amazon DynamoDB, or Aurora DSQL, select a region and plan, and Vercel handles the rest.
- Navigate to the Vercel Marketplace → AWS
- Select Create new (Vercel-managed account)
- Choose Aurora PostgreSQL, Aurora DSQL, or Amazon DynamoDB
- Pick your AWS region and plan
- Connect the resource to your project. Vercel automatically injects environment variables and configuration
Link an existing AWS account
Teams already managing AWS infrastructure can connect their own account through AWS IAM temporary delegation permissions, which allow AWS resources to be created on Vercel and attached to projects without disturbing the existing AWS setup.
- Navigate to the Vercel Marketplace → AWS
- Select Link an existing AWS account
- Grant temporary permissions to Vercel and click Allow Access
- You'll be redirected back to Vercel
- Choose Aurora PostgreSQL, Aurora DSQL, or Amazon DynamoDB
- Pick your AWS region and plan, then create a database
- Connect the resource to your project. Vercel automatically injects environment variables and configuration
What the integration covers
- Provision Aurora PostgreSQL, Aurora DSQL, or Amazon DynamoDB in any supported AWS region
- Inject connection credentials into the Vercel project as environment variables
- Manage resource lifecycle from Vercel, including teardown
- Open the resource in the AWS Console for deeper configuration
- Use AWS-native scaling and durability without manual setup
Databases appear in the Storage tab alongside other resources, giving a unified view of the data layer across providers.
Querying a connected database looks like this:
app/api/todos/route.ts
import { pool } from '@/lib/postgres'
export function GET() {
return Response.json(pool.query("select * from todos"));
}
The client relies on Vercel's OIDC integration to assume your AWS role and generate IAM auth tokens per connection — no stored database passwords:
lib/postgres.ts
import { Signer } from "@aws-sdk/rds-signer";
import { awsCredentialsProvider } from "@vercel/functions/oidc";
import { attachDatabasePool } from "@vercel/functions";
import { Pool } from "pg";
const signer = new Signer({
hostname: process.env.PGHOST,
port: Number(process.env.PGPORT),
username: process.env.PGUSER,
region: process.env.AWS_REGION,
credentials: awsCredentialsProvider({
roleArn: process.env.AWS_ROLE_ARN,
clientConfig: { region: process.env.AWS_REGION },
}),
});
export const pool = new Pool({
host: process.env.PGHOST,
user: process.env.PGUSER,
database: process.env.PGDATABASE || "postgres",
password: () => signer.getAuthToken(),
port: Number(process.env.PGPORT),
ssl: { rejectUnauthorized: false },
});
attachDatabasePool(pool);
Credentials are injected, tokens are handled, and the connection pool is configured for serverless, so the remaining work is application code.
Toward self-driving infrastructure
The launch is a step in Vercel's broader vision for self-driving infrastructure, in which developers spend less time configuring systems and more time building products. Pairing AWS reliability and scale with the Vercel developer experience shortens the path from idea to production.
AWS databases can be installed from the Vercel Marketplace, requested from v0 while building an app, or tried through the Movie Fetching Database template.
