AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Creates a new, empty file system. The operation requires a creation token in the request that Amazon EFS uses to ensure idempotent creation (calling the operation with same creation token has no effect). If a file system does not currently exist that is owned by the caller's AWS account with the specified creation token, this operation does the following:
Creates a new, empty file system. The file system will have an Amazon EFS assigned
ID, and an initial lifecycle state
Returns with the description of the created file system.
Otherwise, this operation returns a
FileSystemAlreadyExists error with
the ID of the existing file system.
For basic use cases, you can use a randomly generated UUID for the creation token.
The idempotent operation allows you to retry a
without risk of creating an extra file system. This can happen when an initial call
fails in a way that leaves it uncertain whether or not a file system was actually
created. An example might be that a transport level timeout occurred or your connection
was reset. As long as you use the same creation token, if the initial call had succeeded
in creating a file system, the client can learn of its existence from the
CreateFileSystem call returns while the file system's lifecycle state
creating. You can check the file system creation status by calling
the DescribeFileSystems operation, which among other things returns the file
This operation also takes an optional
PerformanceMode parameter that
you choose for your file system. We recommend
mode for most file systems. File systems using the
mode can scale to higher levels of aggregate throughput and operations per second
with a tradeoff of slightly higher latencies for most file operations. The performance
mode can't be changed after the file system has been created. For more information,
EFS: Performance Modes.
After the file system is fully created, Amazon EFS sets its lifecycle state to
at which point you can create one or more mount targets for the file system in your
VPC. For more information, see CreateMountTarget. You mount your Amazon EFS
file system on an EC2 instances in your VPC via the mount target. For more information,
see Amazon EFS:
How it Works.
This operation requires permissions for the
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginCreateFileSystem and EndCreateFileSystem.
public virtual Task<CreateFileSystemResponse> CreateFileSystemAsync( String creationToken, CancellationToken cancellationToken )
String of up to 64 ASCII characters. Amazon EFS uses this to ensure idempotent creation.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
|BadRequestException||Returned if the request is malformed or contains an error such as an invalid parameter value or a missing required parameter.|
|FileSystemAlreadyExistsException||Returned if the file system you are trying to create already exists, with the creation token you provided.|
|FileSystemLimitExceededException||Returned if the AWS account has already created maximum number of file systems allowed per account.|
|InternalServerErrorException||Returned if an error occurred on the server side.|
Supported in: 1.3
Supported in: 4.5
Portable Class Library:
Supported in: Windows Store Apps
Supported in: Windows Phone 8.1
Supported in: Xamarin Android
Supported in: Xamarin iOS (Unified)
Supported in: Xamarin.Forms