Vercel Sandbox now supports Secure Compute
By Steven Van ·
Enterprise teams with Secure Compute can route sandbox traffic through static IPs and reach an AWS VPC over peering, set from the SDKs or CLI.
Vercel Sandbox can now be attached to a team's Secure Compute network. A sandbox's public-internet traffic then exits through the network's static IPs, and it can reach private resources in an AWS VPC through VPC peering. The feature is for Enterprise teams that already have Secure Compute, and Vercel describes it in its Sandbox documentation.
To attach a network when creating a sandbox, pass an existing Secure Compute network ID as networkId in the SDK, or add --network-id to the sandbox create command in the CLI. The ID is shown on the network's page under Settings, then Networking, in the Vercel dashboard.
Existing sandboxes can attach to, change or detach from a network with sandbox.update(). The change takes effect on the next session, and a running session keeps its current network until it stops. Traffic that leaves the network over the public internet is billed as Private Data Transfer, while traffic over VPC peering to AWS does not incur data transfer charges.