Otherwise, this operation returns a
FileSystemAlreadyExists error with
the ID of the existing file system.
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
CreateFileSystemcall returns while the file system's lifecycle state is still "creating". You can check the file system creation status by calling the DescribeFileSystems API, which among other things returns the file system state.
After the file system is fully created, Amazon EFS sets its lifecycle state to "available", at which point you can create one or more mount targets for the file system (CreateMountTarget) in your VPC. 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 permission for the
Version: (assembly version)
public abstract CreateFileSystemResponse CreateFileSystem( String creationToken )
String of up to 64 ASCII characters. Amazon EFS uses this to ensure idempotent creation.
|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: 4.5, 4.0, 3.5