Vercel Sandbox now supports Secure Compute
Mirrored from Vercel — AI for archival readability. Support the source by reading on the original site.
Vercel Sandbox now supports Secure Compute, connecting sandboxes to a team's dedicated network. Public-internet traffic exits through the network's static IPs, and sandboxes can reach private resources in an AWS VPC through VPC peering.
You can attach a sandbox to your network in your code or via the CLI.
In your code, pass an existing Secure Compute network ID when creating a sandbox:
import { Sandbox } from '@vercel/sandbox';
const sandbox = await Sandbox.create({ networkId: '3k9x7m2p5q8w1z4n',In the CLI, append --network-id and your network id value when you run the sandbox create command:
npx sandbox@latest create --network-id your_network_id_hereExisting sandboxes can attach to or change networks with sandbox.update(). The change takes effect on the next session. A running session keeps its current network until it stops.
Available to Enterprise teams with Secure Compute.
Learn more in the Sandbox documentation.
Discussion (0)
Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.
Sign in →No comments yet. Sign in and be the first to say something.