Amazon EFS quotas and limits - Amazon Elastic File System
Amazon EFS quotas that you can increaseAmazon EFS resource quotas that you cannot changeQuotas for NFS clientsQuotas for Amazon EFS file systemsUnsupported NFSv4.0 and 4.1 featuresAdditional considerations

Amazon EFS quotas and limits

Following, you can find out about quotas when working with Amazon EFS.

Amazon EFS quotas that you can increase

Service Quotas is an AWS service that helps you manage your quotas, or limits, from one location. You can view all Amazon EFS limit values in the Service Quotas console. You can also request a quota increase for the number of EFS file systems in an AWS Region using the Service Quotas console.

You can also request an increase in Amazon EFS quotas by contacting AWS Support. To learn more, see Requesting a quota increase. The Amazon EFS service team reviews each request individually.

Resource Default quota
Number of file systems for each customer account in an AWS Region 1,000

The following table lists the default throughput quotas for elastic and provisioned throughput modes. For more information about throughput modes, see Amazon EFS performance.

Resource AWS Region Maximum metered throughput Maximum bursting read throughput
Total elastic throughput for all connected clients

All AWS Regions

 1 GiBps 3 GiBps
Total provisioned throughput for all connected clients

All AWS Regions

 1 GiBps 3 GiBps

Requesting a quota increase

To request an increase for these quotas through AWS Support, take the following steps. The Amazon EFS team reviews each quota increase request.

To request a quota increase through AWS Support

  1. Open the AWS Support Center page, and sign in if necessary. Then choose Create Case.

  2. Under Create case, choose Service Limit Increase.

  3. For Limit Type, choose the type of limit to increase. Fill in the necessary fields in the form, and then choose your preferred method of contact.

Amazon EFS resource quotas that you cannot change

Following are the quotas on Amazon EFS resources for each customer account in an AWS Region. These quotas cannot be changed.

Resource Quota
Number of access points for each file system 1,000
Number of connections for each file system 25,000
Number of mount targets for each file system in an Availability Zone 1
Number of mount targets for each virtual private cloud (VPC) 400
Number of security groups for each mount target 5
Number of tags for each file system 50
Number of VPCs for each file system 1
Note

Clients can also connect to mount targets that are in an account or VPC that is different from that of the file system. For more information, see Mounting EFS file systems from another AWS account or VPC.

Following are the default bursting throughput limits, which cannot be changed. For more information about EFS throughput modes, see Amazon EFS performance. The following table lists the default bursting throughput for all connected clients for each AWS Region.

Total bursting throughput for all connected clients
AWS Region Maximum metered throughput Maximum bursting read throughput

US East (Ohio) Region

3 gibibytes per second (GiBps)

5 GiBps

US East (N. Virginia) Region

3 GiBps

5 GiBps

US West (N. California) Region

1 GiBps

3 GiBps

US West (Oregon) Region

3 GiBps

5 GiBps

Africa (Cape Town) Region

 1 GiBps 3 GiBps
Asia Pacific (Hong Kong) Region 1 GiBps 3 GiBps
Asia Pacific (Hyderabad) Region 1 GiBps 3 GiBps
Asia Pacific (Jakarta) Region 1 GiBps 3 GiBps
Asia Pacific (Mumbai) Region 1 GiBps 3 GiBps
Asia Pacific (Osaka) Region 1 GiBps 3 GiBps
Asia Pacific (Seoul) Region 1 GiBps 3 GiBps
Asia Pacific (Singapore) Region 1 GiBps 3 GiBps
Asia Pacific (Sydney) Region 3 GiBps 5 GiBps
Asia Pacific (Tokyo) Region 1 GiBps 3 GiBps
Canada (Central) Region 1 GiBps 3 GiBps
China (Beijing) Region 1 GiBps 3 GiBps
China (Ningxia) Region 1 GiBps 3 GiBps
Europe (Frankfurt) Region 1 GiBps 3 GiBps
Europe (Ireland) Region 3 GiBps 5 GiBps
Europe (London) Region 1 GiBps 3 GiBps
Europe (Milan) Region 1 GiBps 3 GiBps
Europe (Paris) Region 1 GiBps 3 GiBps
Europe (Spain) Region 1 GiBps 3 GiBps
Europe (Stockholm) Region 1 GiBps 3 GiBps
Europe (Zurich) Region 1 GiBps 3 GiBps
Middle East (Bahrain) Region 1 GiBps 3 GiBps
Middle East (UAE) Region 1 GiBps 3 GiBps
South America (São Paulo) Region 1 GiBps 3 GiBps
AWS GovCloud (US-East) 1 GiBps 3 GiBps
AWS GovCloud (US-West) 1 GiBps 3 GiBps

Quotas for NFS clients

The following quotas for NFS clients apply, assuming a Linux NFSv4.1 client:

  • The maximum throughput that you can drive for each NFS client is 500 mebibytes per second (MiBps). NFS client throughput is calculated as the total number of bytes that are sent and received, with a minimum NFS request size of 4 KB (after applying a 1/3 metering rate for read requests).

  • Up to 128 active users for each client can have files open at the same time. Each user represents one local user logged in to the instance. A user that is logged in multiple times counts as one active user.

  • Up to 32,768 files open at the same time on the instance. Listing directory contents doesn't count as opening a file.

  • Each unique mount on the client can acquire up to a total of 65,536 locks per connection.

  • When connecting to Amazon EFS, NFS clients located on-premises or in another AWS Region can observe lower throughput than when connecting to EFS from the same AWS Region. This effect is because of increased network latency. Network latency of 1 ms or less is required to achieve maximum per-client throughput. Use the DataSync data migration service when migrating large datasets from on-premises NFS servers to EFS.

  • The NFS protocol supports a maximum of 16 group IDs (GIDs) per user and any additional GIDs are truncated from NFS client requests. For more information, see Access denied to allowed files on NFS file system..

  • Using Amazon EFS with Microsoft Windows isn't supported.

Quotas for Amazon EFS file systems

The following quotas are specific to Amazon EFS file systems:

  • Maximum name length: 255 bytes.

  • Maximum symbolic link (symlink) length: 4,080 bytes.

  • Maximum number of hard links to a file: 177.

  • Maximum size of a single file: 52,673,613,135,872 bytes (47.9 TiB).

  • Maximum directory depth: 1,000 levels deep.

  • Any one particular file can have up to 512 locks across all instances connected and users accessing the file.

  • Amazon EFS file system policies have a 20,000 character limit.

  • In General Purpose mode, there is a limit of 35,000 file operations per second. Operations that read data or metadata consume one file operation, operations that write data or update metadata consume five file operations. This means that a file system can support 35,000 read operations per second, or 7,000 write operations, or some combination of the two. For example, your file system can support 20,000 read operations and 3,000 write operations per second:

    20,000 reads x 1 file operation per read + 3,000 writes x 5 file operations per write = 35,000 file operations

    File operations are counted from all connecting clients.

Unsupported NFSv4.0 and 4.1 features

Although Amazon Elastic File System doesn't support NFSv2, or NFSv3, Amazon EFS supports both NFSv4.1 and NFSv4.0, except for the following features:

  • pNFS

  • Client delegation or callbacks of any type

    • Operation OPEN always returns OPEN_DELEGATE_NONE as the delegation type.

    • The operation OPEN returns NFSERR_NOTSUPP for the CLAIM_DELEGATE_CUR and CLAIM_DELEGATE_PREV claim types.

  • Mandatory locking

    All locks in Amazon EFS are advisory, which means that read and write operations don't check for conflicting locks before the operation is executed.

  • Deny share

    NFS supports the concept of a share deny. A share deny is primarily used by Windows clients for users to deny others access to a particular file that has been opened. Amazon EFS doesn't support this, and returns the NFS error NFS4ERR_NOTSUPP for any OPEN commands specifying a share deny value other than OPEN4_SHARE_DENY_NONE. Linux NFS clients don't use anything other than OPEN4_SHARE_DENY_NONE.

  • Access control lists (ACLs)

  • Amazon EFS doesn't update the time_access attribute on file reads. Amazon EFS updates time_access in the following events:

    • When a file is created (an inode is created)

    • When an NFS client makes an explicit setattr call

    • On a write to the inode caused by, for example, file size changes or file metadata changes

    • Any inode attribute is updated

  • Namespaces

  • Persistent reply cache

  • Kerberos based security

  • NFSv4.1 data retention

  • SetUID on directories

  • Unsupported file types when using the CREATE operation: Block devices (NF4BLK), character devices (NF4CHR), attribute directory (NF4ATTRDIR), and named attribute (NF4NAMEDATTR).

  • Unsupported attributes: FATTR4_ARCHIVE, FATTR4_FILES_AVAIL, FATTR4_FILES_FREE, FATTR4_FILES_TOTAL, FATTR4_FS_LOCATIONS, FATTR4_MIMETYPE, FATTR4_QUOTA_AVAIL_HARD, FATTR4_QUOTA_AVAIL_SOFT, FATTR4_QUOTA_USED, FATTR4_TIME_BACKUP, and FATTR4_ACL.

    An attempt to set these attributes results in an NFS4ERR_ATTRNOTSUPP error that is sent back to the client.

Additional considerations

In addition, note the following:

  • For a list of AWS Regions where you can create Amazon EFS file systems, see the AWS General Reference.

  • Amazon EFS does not support the nconnect mount option.

  • You can mount an Amazon EFS file system from on-premises data center servers using AWS Direct Connect and VPN. For more information, see Mounting with on-premises clients.