---
title: "Grant a VPC access to an SFS"
description: "Let every resource in a VPC reach an SFS with read and write access."
content_type: "how-to"
product: "sfs"
platform: "MyAccount"
url: "/myaccount/sfs/how-to/grant-vpc-access-to-an-sfs/"
topic: ["create-and-connect"]
relationships: {"requires":["/myaccount/sfs/how-to/create-an-sfs/"]}
---

# Grant a VPC access to an SFS

VPC-wide access lets every resource in the SFS's VPC read and write the SFS: nodes, load
balancers, Kubernetes, and databases. It is the quickest way to start using a new SFS. To pick
nodes one at a time instead, and make some of them read-only, see [Configure per-node access to an SFS](/myaccount/sfs/how-to/configure-per-node-access-to-an-sfs/).

An SFS uses one kind of access at a time. If it already gives access to single nodes, granting
VPC-wide access replaces that per-node access.

## Grant it

Once the SFS reads **Available**, and any backup on it has finished its first run:

1. In **Scalable File System**, open the SFS's **Actions** menu and click **Grant all access**.
2. Click **Grant**.

The SFS reads **Configuring** while the access is applied, then **Available** again. The
**ACL** tab now lists the VPC with its CIDR and permission. Every
resource in the VPC can now mount it; see [Mount an SFS](/myaccount/sfs/how-to/mount-an-sfs/).

## Turn it off

To end the VPC's access, for example before you switch to per-node access:

1. Open the SFS's **Actions** menu and click **Disable all access**.
2. Click **Disable**.

This ends access for the nodes, load balancers, Kubernetes, and databases in that VPC. The SFS reads **Configuring**, then **Available** again. To give single nodes access again, add them on the **ACL** tab; see
[Configure per-node access to an SFS](/myaccount/sfs/how-to/configure-per-node-access-to-an-sfs/). If a node in the VPC gets `access denied by server` when it
mounts the SFS, see [Troubleshooting SFS](/myaccount/sfs/troubleshooting/sfs/#mountnfs-access-denied-by-server).