diff --git a/clients/client-efs/src/commands/CreateAccessPointCommand.ts b/clients/client-efs/src/commands/CreateAccessPointCommand.ts index e176bcafdae7..9e6cd698d2b3 100644 --- a/clients/client-efs/src/commands/CreateAccessPointCommand.ts +++ b/clients/client-efs/src/commands/CreateAccessPointCommand.ts @@ -37,13 +37,14 @@ export interface CreateAccessPointCommandOutput extends AccessPointDescription, /** * @public - *

Creates an EFS access point. An access point is an application-specific view into an EFS - * file system that applies an operating system user and group, and a file system path, to any - * file system request made through the access point. The operating system user and group - * override any identity information provided by the NFS client. The file system path is exposed - * as the access point's root directory. Applications using the access point can only access data in - * the application's own directory and any subdirectories. To learn more, see Mounting a file system using EFS access - * points.

+ *

Creates an EFS access point. An access point is an application-specific view + * into an EFS file system that applies an operating system user and group, and a file + * system path, to any file system request made through the access point. The operating system + * user and group override any identity information provided by the NFS client. The file system + * path is exposed as the access point's root directory. Applications using the access point can + * only access data in the application's own directory and any subdirectories. To learn more, see + * Mounting a file + * system using EFS access points.

* *

If multiple requests to create access points on the same file system are sent in quick * succession, and the file system is near the limit of 1,000 access points, you may experience diff --git a/clients/client-efs/src/commands/CreateFileSystemCommand.ts b/clients/client-efs/src/commands/CreateFileSystemCommand.ts index 9aa38016ae2c..0ae400281b56 100644 --- a/clients/client-efs/src/commands/CreateFileSystemCommand.ts +++ b/clients/client-efs/src/commands/CreateFileSystemCommand.ts @@ -57,7 +57,7 @@ export interface CreateFileSystemCommandOutput extends FileSystemDescription, __ *

For basic use cases, you can use a randomly generated UUID for the creation * token.

*
- *

The idempotent operation allows you to retry a CreateFileSystem call without + *

The idempotent operation allows you to retry a CreateFileSystem call 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 @@ -72,11 +72,15 @@ export interface CreateFileSystemCommandOutput extends FileSystemDescription, __ * calling the DescribeFileSystems operation, which among other things returns the file * system state.

* - *

This operation accepts an optional PerformanceMode parameter that you - * choose for your file system. We recommend generalPurpose performance mode for - * most file systems. File systems using the maxIO performance 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 + *

This operation accepts an optional PerformanceMode parameter that you choose + * for your file system. We recommend generalPurpose performance mode for all file + * systems. File systems using the maxIO mode is a previous generation performance type that is designed for highly parallelized workloads that can tolerate higher latencies + * than the General Purpose mode. Max I/O mode is not supported for One Zone file systems or + * file systems that use Elastic throughput.

+ * + *

Due to the higher per-operation latencies with Max I/O, we recommend using General Purpose performance mode for all file systems.

+ *
+ *

The performance mode can't be changed after * the file system has been created. For more information, see Amazon EFS performance * modes.

*

You can set the throughput mode for the file system using the ThroughputMode parameter.

@@ -129,6 +133,7 @@ export interface CreateFileSystemCommandOutput extends FileSystemDescription, __ * // Timestamp: new Date("TIMESTAMP"), * // ValueInIA: Number("long"), * // ValueInStandard: Number("long"), + * // ValueInArchive: Number("long"), * // }, * // PerformanceMode: "generalPurpose" || "maxIO", // required * // Encrypted: true || false, diff --git a/clients/client-efs/src/commands/CreateMountTargetCommand.ts b/clients/client-efs/src/commands/CreateMountTargetCommand.ts index e70a21e87855..d68fdb2da43f 100644 --- a/clients/client-efs/src/commands/CreateMountTargetCommand.ts +++ b/clients/client-efs/src/commands/CreateMountTargetCommand.ts @@ -44,12 +44,12 @@ export interface CreateMountTargetCommandOutput extends MountTargetDescription, * file system. If you have multiple subnets in an Availability Zone, you create a mount target * in one of the subnets. EC2 instances do not need to be in the same subnet as the mount target * in order to access their file system.

- *

You can create only one mount target for an EFS file system using One Zone storage - * classes. You must create that mount target in the same Availability Zone in which the file - * system is located. Use the AvailabilityZoneName and - * AvailabiltyZoneId properties in the DescribeFileSystems - * response object to get this information. Use the subnetId associated with the - * file system's Availability Zone when creating the mount target.

+ *

You can create only one mount target for a One Zone file system. + * You must create that mount target in the same Availability Zone in which the file system is + * located. Use the AvailabilityZoneName and AvailabiltyZoneId + * properties in the DescribeFileSystems response object to get this + * information. Use the subnetId associated with the file system's Availability Zone + * when creating the mount target.

*

For more information, see Amazon EFS: How it Works.

*

To create a mount target for a file system, the file system's lifecycle state must be * available. For more information, see DescribeFileSystems.

diff --git a/clients/client-efs/src/commands/CreateReplicationConfigurationCommand.ts b/clients/client-efs/src/commands/CreateReplicationConfigurationCommand.ts index 4cc3913898ec..fd9cc5077d65 100644 --- a/clients/client-efs/src/commands/CreateReplicationConfigurationCommand.ts +++ b/clients/client-efs/src/commands/CreateReplicationConfigurationCommand.ts @@ -42,8 +42,8 @@ export interface CreateReplicationConfigurationCommandOutput /** * @public - *

Creates a replication configuration that replicates an existing EFS file system to a new, - * read-only file system. For more information, see Amazon EFS replication in the + *

Creates a replication configuration that replicates an existing EFS file system + * to a new, read-only file system. For more information, see Amazon EFS replication in the * Amazon EFS User Guide. The replication configuration * specifies the following:

*