Amazon S3 arrives in the Vercel Marketplace with short-lived OIDC credentials

Amazon S3 is now available in the Vercel Marketplace, letting developers provision buckets and hook them into their projects without switching away from the Vercel dashboard. According to the Vercel blog, the integration handles resource creation, connection setup and ongoing management, while linking out to AWS whenever a setting needs configuration that Vercel itself does not expose.

What the integration does

The integration creates S3 resources on a developer's behalf and writes the connection details into the project's environment variables, so there is no manual copying of bucket names or endpoints. Those resources then sit next to the rest of the application's infrastructure in Vercel, letting teams look after storage in the same place they manage deployments. For AWS-specific configuration, the integration hands off to the relevant AWS tooling.

The most consequential design decision is authentication. Rather than generating a long-lived AWS access key and pasting it into an environment variable, a pattern with a poor security track record, the integration uses short-lived OIDC credentials. Vercel says static AWS keys are never stored as part of the flow.

S3 inside v0

Vercel has also brought S3 into v0, its generative coding product. According to the announcement, v0 can set up the storage, wire up the connection and write the code that uses it, all from a single prompt.

The blog post shows two code paths. A createS3 helper from the @vercel/aws package returns an S3 client already authenticated through Vercel's OIDC flow, aimed at quick setups. Teams that prefer the standard SDK can instead construct an S3Client from @aws-sdk/client-s3 and pass it an awsCredentialsProvider imported from @vercel/functions/oidc; the provider reads the role ARN and region from environment variables and handles the credential exchange itself.

Choosing between S3 and Vercel Blob

Vercel already runs its own storage product, Vercel Blob, which covers public and private file uploads and serves them through built-in caching and a CDN near end users. The company positions the new integration as complementary rather than competitive: Blob fits straightforward application uploads, while S3 suits teams already invested in AWS workflows.

Vercel points to two newer S3 capabilities as further reasons to take the AWS route: S3 Tables, which runs analytics on managed Iceberg tables, and S3 Vectors, which adds vector storage and search.

Accounts, credits and one limitation

Developers new to AWS can create an account directly through Vercel and receive $100 in credits, valid for six months, according to the announcement. Anyone with an existing account can link it instead and manage the plan and usage from the Vercel dashboard.

One restriction applies: once an account is linked, only buckets created through Vercel are supported, so pre-existing buckets stay outside the integration's reach. AWS has also published its own announcement covering further examples and setup details, which Vercel points readers towards.

Why it matters

Object storage has long been awkward for frontend teams deploying on Vercel: the application lives in one dashboard, the storage in another, and the bridge between them is usually a static AWS key sitting in an environment variable. By moving provisioning into the Marketplace and replacing static keys with short-lived OIDC credentials, Vercel removes both the split workflow and a common source of credential leaks.

The move also shows how the platform layer keeps consolidating. Vercel is increasingly acting as a control plane in front of AWS resources, while AWS gains a distribution channel into a developer base it has historically reached less directly. And with v0 able to spin up storage and generate the code that uses it from one prompt, the integration points at a broader trend: infrastructure provisioned at the same moment the application that needs it is written.