Network Connectors

A network connector decides where a MicroVM's network traffic leaves. Settings → Network lists, under Network Connectors, the connectors of the profile Settings is showing, in one of its regions:

You bring your own VPC, subnets and NAT gateway: MicroVM Studio makes none of them. A MicroVM on a VPC connector gets a private address, never a public IP, so it reaches the internet only if its subnets route out through a NAT gateway. Without that route, GitHub, package installs, Claude Code and Codex won't work in it.

New Connector…

Under the list, choose New Connector… and give it a name (letters, digits and hyphens, up to 40). It uses the Settings profile and the region chosen in the tab. Then choose:

Before Create, the sheet lists what it makes, tagged. The connector takes a few minutes and has no published price. Closing the sheet doesn't stop it, and Resume picks up one that stopped part way.

Creating a connector with an existing role needs your AWS identity to be allowed to read the role and pass it to Lambda. The minimal policy in the permission check lets you read any role, but lists for passing only the roles your workspaces and connectors already use: add a new role's ARN to its pass-role statement before you create the connector.

The list

The list shows every connector in the region: the built-in one, those MicroVM Studio made, marked Made by this app, and any others in the account. MicroVM Studio only shows the others, and never changes or deletes them. View… shows a connector's details: its VPC, health, subnets, security group and role, and the file systems and workspaces that use it. A row's … menu has Change Subnets… and Delete…. Used by counts the file systems and workspaces on it; point at it for their names. Refresh lists the connectors again.

Two profiles of the same AWS account list the same connectors. One made under the other profile says Left over by this app here, though it isn't: manage it from the profile that made it. Delete… refuses it while that profile still has it.

Change Subnets…

Change Subnets… moves a connector onto other subnets of its VPC: it makes a new network connector on them, then deletes the old one, in about 5 minutes. MicroVMs already running on it may lose their connection: relaunch them. File systems on it keep their mount targets, and may need new ones in new zones: their View… offers Add Mount Targets. A change that stops part way says so beside the connector, with Try Again.

Made by an earlier version

Networks made by versions 0.2.0 and 0.2.1, including ones with a NAT gateway MicroVM Studio created, stay and are marked Made by an earlier version. They keep working for storage, and still have View… and Delete…. Change Subnets… is only for those without a NAT gateway: the others use private subnets made for it. Nothing makes a NAT gateway, default VPC or private subnet any more. A NAT gateway costs about $33 a month plus $0.045 per GB of data through it, and its Elastic IP about $3.60 a month (us-east-1 prices; other regions differ). Deleting the network stops both.

Deleting

Delete… is refused while a file system is on the connector, or a workspace leaves through it (move those workspaces to Internet egress first). It deletes the connector and, if MicroVM Studio made it, its security group; a group you chose stays. For a network from an earlier version it also deletes everything MicroVM Studio made: the NAT gateway, Elastic IP, route table and private subnets, with the NAT gateway and Elastic IP first so they stop costing even when AWS is slow to release the rest. The IAM role stays, and so does a default VPC: it's AWS's own. MicroVMs already running on the connector lose their network, and it can't be undone. A connector a file system is on can't be deleted: delete the file system first, in Settings → Storage. One that nothing uses, left over from an earlier delete or change, says Left over by this app and can be deleted.