--- title: "Attach a node to a VPC" description: "Move a node onto a different VPC, or take it off one, from the node's own tab." content_type: "how-to" product: "node" platform: "MyAccount" url: "/myaccount/node/how-to/attach-a-node-to-a-vpc/" topic: ["network"] relationships: {"requires":["/myaccount/vpc/"]} --- # Attach a node to a VPC A VPC, or virtual private cloud, is a private network your nodes share, reached through their private IPs rather than the internet. A VPC marked **Default** has an E2E provided range of 512 addresses with no subnets. Attaching a node to a **Custom** VPC puts it on a network with your own address range and subnets. Create that VPC first; see [Create a VPC](/myaccount/vpc/how-to/create-a-vpc/). You can also turn a VPC on while you [create a node](/myaccount/node/how-to/create-a-node); the same **Advanced settings** step lets you pick a VPC and, optionally, a subnet. To attach or detach one afterward, use the node's own tab. ## Attach a VPC Attaching a custom VPC deletes any existing backup on the node. If you still need something from that backup, restore it first. CDP Backup backs up nodes on E2E's own network: a private IP with no VPC, or a VPC made with an E2E-provided range. Once the node is back on that network, turn CDP Backup on again; the earlier recovery points are gone. See [Turn on CDP Backup for a node](/myaccount/cdp-backup/how-to/turn-on-cdp-backup/). A VPC can only be attached to a node in the same region, so only a VPC that is active and in that region appears as an option. A node can have up to three private network connections, counting its own default private IP, and up to two from the same VPC or subnet. Open the node's **Network** tab and choose to attach a VPC, then pick one from your account. You can also choose a subnet within it, and a preferred IP address inside that subnet. Confirm to attach it. The VPC then shows in the attached VPCs section of the **Network** tab, and the node has a private IP in that network. To check, connect to that private IP from another node in the same VPC. If the VPC you want is not in the list, see [Troubleshooting node networking and connectivity](/myaccount/node/troubleshooting/networking-and-connectivity/#vpc-does-not-appear-in-the-attach-list). ## Detach a VPC Detaching a VPC removes the node's private IP from that network. If [CDP Backup](/myaccount/cdp-backup/) is using that VPC, detaching deletes the backup too. To detach a VPC, the node must be **Running** or **Powered off**, unlocked, not acting as the VPC's gateway, and disconnected from any SFS. SFS is E2E's Scalable File System, for shared files. Then open the **Network** tab and choose to detach the VPC. To end a node's access to an SFS, see [Configure per-node access to an SFS](/myaccount/sfs/how-to/configure-per-node-access-to-an-sfs/).