@aws-sdk/client-efs 3.35.0 → 3.38.0

package/dist-types/ts3.4/EFSClient.d.ts

@@ -36,128 +36,59 @@ import { UpdateFileSystemCommandInput, UpdateFileSystemCommandOutput } from "./c
 export declare type ServiceInputTypes = CreateAccessPointCommandInput | CreateFileSystemCommandInput | CreateMountTargetCommandInput | CreateTagsCommandInput | DeleteAccessPointCommandInput | DeleteFileSystemCommandInput | DeleteFileSystemPolicyCommandInput | DeleteMountTargetCommandInput | DeleteTagsCommandInput | DescribeAccessPointsCommandInput | DescribeAccountPreferencesCommandInput | DescribeBackupPolicyCommandInput | DescribeFileSystemPolicyCommandInput | DescribeFileSystemsCommandInput | DescribeLifecycleConfigurationCommandInput | DescribeMountTargetSecurityGroupsCommandInput | DescribeMountTargetsCommandInput | DescribeTagsCommandInput | ListTagsForResourceCommandInput | ModifyMountTargetSecurityGroupsCommandInput | PutAccountPreferencesCommandInput | PutBackupPolicyCommandInput | PutFileSystemPolicyCommandInput | PutLifecycleConfigurationCommandInput | TagResourceCommandInput | UntagResourceCommandInput | UpdateFileSystemCommandInput;
 export declare type ServiceOutputTypes = CreateAccessPointCommandOutput | CreateFileSystemCommandOutput | CreateMountTargetCommandOutput | CreateTagsCommandOutput | DeleteAccessPointCommandOutput | DeleteFileSystemCommandOutput | DeleteFileSystemPolicyCommandOutput | DeleteMountTargetCommandOutput | DeleteTagsCommandOutput | DescribeAccessPointsCommandOutput | DescribeAccountPreferencesCommandOutput | DescribeBackupPolicyCommandOutput | DescribeFileSystemPolicyCommandOutput | DescribeFileSystemsCommandOutput | DescribeLifecycleConfigurationCommandOutput | DescribeMountTargetSecurityGroupsCommandOutput | DescribeMountTargetsCommandOutput | DescribeTagsCommandOutput | ListTagsForResourceCommandOutput | ModifyMountTargetSecurityGroupsCommandOutput | PutAccountPreferencesCommandOutput | PutBackupPolicyCommandOutput | PutFileSystemPolicyCommandOutput | PutLifecycleConfigurationCommandOutput | TagResourceCommandOutput | UntagResourceCommandOutput | UpdateFileSystemCommandOutput;
 export interface ClientDefaults extends Partial<__SmithyResolvedConfiguration<__HttpHandlerOptions>> {
-    /**
-     * The HTTP handler to use. Fetch in browser and Https in Nodejs.
-     */
+    
     requestHandler?: __HttpHandler;
-    /**
-     * A constructor for a class implementing the {@link __Hash} interface
-     * that computes the SHA-256 HMAC or checksum of a string or binary buffer.
-     * @internal
-     */
+    
     sha256?: __HashConstructor;
-    /**
-     * The function that will be used to convert strings into HTTP endpoints.
-     * @internal
-     */
+    
     urlParser?: __UrlParser;
-    /**
-     * A function that can calculate the length of a request body.
-     * @internal
-     */
+    
     bodyLengthChecker?: (body: any) => number | undefined;
-    /**
-     * A function that converts a stream into an array of bytes.
-     * @internal
-     */
+    
     streamCollector?: __StreamCollector;
-    /**
-     * The function that will be used to convert a base64-encoded string to a byte array.
-     * @internal
-     */
+    
     base64Decoder?: __Decoder;
-    /**
-     * The function that will be used to convert binary data to a base64-encoded string.
-     * @internal
-     */
+    
     base64Encoder?: __Encoder;
-    /**
-     * The function that will be used to convert a UTF8-encoded string to a byte array.
-     * @internal
-     */
+    
     utf8Decoder?: __Decoder;
-    /**
-     * The function that will be used to convert binary data to a UTF-8 encoded string.
-     * @internal
-     */
+    
     utf8Encoder?: __Encoder;
-    /**
-     * The runtime environment.
-     * @internal
-     */
+    
     runtime?: string;
-    /**
-     * Disable dyanamically changing the endpoint of the client based on the hostPrefix
-     * trait of an operation.
-     */
+    
     disableHostPrefix?: boolean;
-    /**
-     * Value for how many times a request will be made at most in case of retry.
-     */
+    
     maxAttempts?: number | __Provider<number>;
-    /**
-     * Specifies which retry algorithm to use.
-     */
+    
     retryMode?: string | __Provider<string>;
-    /**
-     * Optional logger for logging debug/info/warn/error.
-     */
+    
     logger?: __Logger;
-    /**
-     * Unique service identifier.
-     * @internal
-     */
+    
     serviceId?: string;
-    /**
-     * The AWS region to which this client will send requests
-     */
+    
     region?: string | __Provider<string>;
-    /**
-     * Default credentials provider; Not available in browser runtime.
-     * @internal
-     */
+    
     credentialDefaultProvider?: (input: any) => __Provider<__Credentials>;
-    /**
-     * Fetch related hostname, signing name or signing region with given region.
-     * @internal
-     */
+    
     regionInfoProvider?: RegionInfoProvider;
-    /**
-     * The provider populating default tracking information to be sent with `user-agent`, `x-amz-user-agent` header
-     * @internal
-     */
+    
     defaultUserAgentProvider?: Provider<__UserAgent>;
 }
 declare type EFSClientConfigType = Partial<__SmithyConfiguration<__HttpHandlerOptions>> & ClientDefaults & RegionInputConfig & EndpointsInputConfig & RetryInputConfig & HostHeaderInputConfig & AwsAuthInputConfig & UserAgentInputConfig;
-/**
- * The configuration interface of EFSClient class constructor that set the region, credentials and other options.
- */
+
 export interface EFSClientConfig extends EFSClientConfigType {
 }
 declare type EFSClientResolvedConfigType = __SmithyResolvedConfiguration<__HttpHandlerOptions> & Required<ClientDefaults> & RegionResolvedConfig & EndpointsResolvedConfig & RetryResolvedConfig & HostHeaderResolvedConfig & AwsAuthResolvedConfig & UserAgentResolvedConfig;
-/**
- * The resolved configuration interface of EFSClient class. This is resolved and normalized from the {@link EFSClientConfig | constructor configuration interface}.
- */
+
 export interface EFSClientResolvedConfig extends EFSClientResolvedConfigType {
 }
-/**
- * <fullname>Amazon Elastic File System</fullname>
- *          <p>Amazon Elastic File System (Amazon EFS) provides simple, scalable file storage for use
- *       with Amazon EC2 instances in the Amazon Web Services Cloud. With Amazon EFS, storage capacity is elastic,
- *       growing and shrinking automatically as you add and remove files, so your applications have the
- *       storage they need, when they need it. For more information, see the <a href="https://docs.aws.amazon.com/efs/latest/ug/api-reference.html">Amazon Elastic File System API Reference</a> and the <a href="https://docs.aws.amazon.com/efs/latest/ug/whatisefs.html">Amazon Elastic File System User Guide</a>.</p>
- */
+
 export declare class EFSClient extends __Client<__HttpHandlerOptions, ServiceInputTypes, ServiceOutputTypes, EFSClientResolvedConfig> {
-    /**
-     * The resolved configuration of EFSClient class. This is resolved and normalized from the {@link EFSClientConfig | constructor configuration interface}.
-     */
+    
     readonly config: EFSClientResolvedConfig;
     constructor(configuration: EFSClientConfig);
-    /**
-     * Destroy underlying resources, like sockets. It's usually not necessary to do this.
-     * However in Node.js, it's best to explicitly shut down the client's agent when it is no longer needed.
-     * Otherwise, sockets might stay open for quite a long time before the server terminates them.
-     */
+    
     destroy(): void;
 }
 export {};

package/dist-types/ts3.4/commands/CreateAccessPointCommand.d.ts

@@ -6,36 +6,11 @@ export interface CreateAccessPointCommandInput extends CreateAccessPointRequest
 }
 export interface CreateAccessPointCommandOutput extends AccessPointDescription, __MetadataBearer {
 }
-/**
- * <p>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 its own directory and below. To learn more, see <a href="https://docs.aws.amazon.com/efs/latest/ug/efs-access-points.html">Mounting a file system using EFS access
- *         points</a>.</p>
- *          <p>This operation requires permissions for the <code>elasticfilesystem:CreateAccessPoint</code> action.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { EFSClient, CreateAccessPointCommand } from "@aws-sdk/client-efs"; // ES Modules import
- * // const { EFSClient, CreateAccessPointCommand } = require("@aws-sdk/client-efs"); // CommonJS import
- * const client = new EFSClient(config);
- * const command = new CreateAccessPointCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateAccessPointCommandInput} for command's `input` shape.
- * @see {@link CreateAccessPointCommandOutput} for command's `response` shape.
- * @see {@link EFSClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class CreateAccessPointCommand extends $Command<CreateAccessPointCommandInput, CreateAccessPointCommandOutput, EFSClientResolvedConfig> {
     readonly input: CreateAccessPointCommandInput;
     constructor(input: CreateAccessPointCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: EFSClientResolvedConfig, options?: __HttpHandlerOptions): Handler<CreateAccessPointCommandInput, CreateAccessPointCommandOutput>;
     private serialize;
     private deserialize;

package/dist-types/ts3.4/commands/CreateFileSystemCommand.d.ts

@@ -6,82 +6,11 @@ export interface CreateFileSystemCommandInput extends CreateFileSystemRequest {
 }
 export interface CreateFileSystemCommandOutput extends FileSystemDescription, __MetadataBearer {
 }
-/**
- * <p>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 Amazon Web Services account with the specified creation token, this operation does the
- *       following:</p>
- *          <ul>
- *             <li>
- *                <p>Creates a new, empty file system. The file system will have an Amazon EFS assigned
- *           ID, and an initial lifecycle state <code>creating</code>.</p>
- *             </li>
- *             <li>
- *                <p>Returns with the description of the created file system.</p>
- *             </li>
- *          </ul>
- *          <p>Otherwise, this operation returns a <code>FileSystemAlreadyExists</code> error with the
- *       ID of the existing file system.</p>
- *          <note>
- *             <p>For basic use cases, you can use a randomly generated UUID for the creation
- *         token.</p>
- *          </note>
- *          <p> The idempotent operation allows you to retry a <code>CreateFileSystem</code> 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
- *       the same creation token, if the initial call had succeeded in creating a file system, the
- *       client can learn of its existence from the <code>FileSystemAlreadyExists</code> error.</p>
- *          <p>For more information, see
- *       <a href="https://docs.aws.amazon.com/efs/latest/ug/creating-using-create-fs.html#creating-using-create-fs-part1">Creating a file system</a>
- *      in the <i>Amazon EFS User Guide</i>.</p>
- *
- *          <note>
- *             <p>The <code>CreateFileSystem</code> call returns while the file system's lifecycle
- *         state is still <code>creating</code>. You can check the file system creation status by
- *         calling the <a>DescribeFileSystems</a> operation, which among other things returns the file
- *         system state.</p>
- *          </note>
- *
- *          <p>This operation accepts an optional <code>PerformanceMode</code> parameter that you
- *       choose for your file system. We recommend <code>generalPurpose</code> performance mode for
- *       most file systems. File systems using the <code>maxIO</code> 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
- *       the file system has been created. For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/performance.html#performancemodes.html">Amazon EFS performance
- *         modes</a>.</p>
- *
- *          <p>You can set the throughput mode for the file system using the <code>ThroughputMode</code> parameter.</p>
- *
- *          <p>After the file system is fully created, Amazon EFS sets its lifecycle state to
- *         <code>available</code>, at which point you can create one or more mount targets for the file
- *       system in your VPC. For more information, see <a>CreateMountTarget</a>. You mount your Amazon EFS file system on an EC2 instances in
- *       your VPC by using the mount target. For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/how-it-works.html">Amazon EFS: How it Works</a>. </p>
- *
- *          <p> This operation requires permissions for the
- *         <code>elasticfilesystem:CreateFileSystem</code> action. </p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { EFSClient, CreateFileSystemCommand } from "@aws-sdk/client-efs"; // ES Modules import
- * // const { EFSClient, CreateFileSystemCommand } = require("@aws-sdk/client-efs"); // CommonJS import
- * const client = new EFSClient(config);
- * const command = new CreateFileSystemCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateFileSystemCommandInput} for command's `input` shape.
- * @see {@link CreateFileSystemCommandOutput} for command's `response` shape.
- * @see {@link EFSClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class CreateFileSystemCommand extends $Command<CreateFileSystemCommandInput, CreateFileSystemCommandOutput, EFSClientResolvedConfig> {
     readonly input: CreateFileSystemCommandInput;
     constructor(input: CreateFileSystemCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: EFSClientResolvedConfig, options?: __HttpHandlerOptions): Handler<CreateFileSystemCommandInput, CreateFileSystemCommandOutput>;
     private serialize;
     private deserialize;

package/dist-types/ts3.4/commands/CreateMountTargetCommand.d.ts

@@ -6,170 +6,11 @@ export interface CreateMountTargetCommandInput extends CreateMountTargetRequest
 }
 export interface CreateMountTargetCommandOutput extends MountTargetDescription, __MetadataBearer {
 }
-/**
- * <p>Creates a mount target for a file system. You can then mount the file system on EC2
- *       instances by using the mount target.</p>
- *          <p>You can create one mount target in each Availability Zone in your VPC. All EC2
- *       instances in a VPC within a given Availability Zone share a single mount target for a given
- *       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.</p>
- *          <p>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 <code>AvailabilityZoneName</code> and
- *         <code>AvailabiltyZoneId</code> properties in the <a>DescribeFileSystems</a>
- *       response object to get this information. Use the <code>subnetId</code> associated with the
- *       file system's Availability Zone when creating the mount target.</p>
- *          <p>For more information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/how-it-works.html">Amazon EFS: How it Works</a>. </p>
- *          <p>To create a mount target for a file system, the file system's lifecycle state must be
- *         <code>available</code>. For more information, see <a>DescribeFileSystems</a>.</p>
- *          <p>In the request, provide the following:</p>
- *          <ul>
- *             <li>
- *                <p>The file system ID for which you are creating the mount
- *         target.</p>
- *             </li>
- *             <li>
- *                <p>A subnet ID, which determines the following:</p>
- *                <ul>
- *                   <li>
- *                      <p>The VPC in which Amazon EFS creates the mount target</p>
- *                   </li>
- *                   <li>
- *                      <p>The Availability Zone in which Amazon EFS creates the mount target</p>
- *                   </li>
- *                   <li>
- *                      <p>The IP address range from which Amazon EFS selects the IP address of the mount target
- *               (if you don't specify an IP address in the request)</p>
- *                   </li>
- *                </ul>
- *             </li>
- *          </ul>
- *
- *          <p>After creating the mount target, Amazon EFS returns a response that includes, a
- *         <code>MountTargetId</code> and an <code>IpAddress</code>. You use this IP address when
- *       mounting the file system in an EC2 instance. You can also use the mount target's DNS name
- *       when mounting the file system. The EC2 instance on which you mount the file system by using
- *       the mount target can resolve the mount target's DNS name to its IP address. For more
- *       information, see <a href="https://docs.aws.amazon.com/efs/latest/ug/how-it-works.html#how-it-works-implementation">How it Works:
- *         Implementation Overview</a>. </p>
- *          <p>Note that you can create mount targets for a file system in only one VPC, and there can
- *       be only one mount target per Availability Zone. That is, if the file system already has one or
- *       more mount targets created for it, the subnet specified in the request to add another mount
- *       target must meet the following requirements:</p>
- *          <ul>
- *             <li>
- *                <p>Must belong to the same VPC as the subnets of the existing mount targets</p>
- *             </li>
- *             <li>
- *                <p>Must not be in the same Availability Zone as any of the subnets of the existing
- *           mount targets</p>
- *             </li>
- *          </ul>
- *
- *          <p>If the request satisfies the requirements, Amazon EFS does the following:</p>
- *          <ul>
- *             <li>
- *                <p>Creates a new mount target in the specified subnet.</p>
- *             </li>
- *             <li>
- *                <p>Also creates a new network interface in the subnet as follows:</p>
- *                <ul>
- *                   <li>
- *                      <p>If the request provides an <code>IpAddress</code>, Amazon EFS assigns that IP
- *               address to the network interface. Otherwise, Amazon EFS assigns a free address in the
- *               subnet (in the same way that the Amazon EC2 <code>CreateNetworkInterface</code> call
- *               does when a request does not specify a primary private IP address).</p>
- *                   </li>
- *                   <li>
- *                      <p>If the request provides <code>SecurityGroups</code>, this network interface is
- *               associated with those security groups. Otherwise, it belongs to the default security
- *               group for the subnet's VPC.</p>
- *                   </li>
- *                   <li>
- *                      <p>Assigns the description <code>Mount target <i>fsmt-id</i> for
- *                 file system <i>fs-id</i>
- *                         </code> where <code>
- *                            <i>fsmt-id</i>
- *                         </code> is the mount target ID, and <code>
- *                            <i>fs-id</i>
- *                         </code> is the <code>FileSystemId</code>.</p>
- *                   </li>
- *                   <li>
- *                      <p>Sets the <code>requesterManaged</code> property of the network interface to
- *                 <code>true</code>, and the <code>requesterId</code> value to
- *               <code>EFS</code>.</p>
- *                   </li>
- *                </ul>
- *                <p>Each Amazon EFS mount target has one corresponding requester-managed EC2 network
- *           interface. After the network interface is created, Amazon EFS sets the
- *             <code>NetworkInterfaceId</code> field in the mount target's description to the
- *           network interface ID, and the <code>IpAddress</code> field to its address. If network
- *           interface creation fails, the entire <code>CreateMountTarget</code> operation
- *           fails.</p>
- *             </li>
- *          </ul>
- *          <note>
- *             <p>The <code>CreateMountTarget</code> call returns only after creating the network
- *         interface, but while the mount target state is still <code>creating</code>, you can check
- *         the mount target creation status by calling the <a>DescribeMountTargets</a> operation, which among other things returns the mount
- *         target state.</p>
- *          </note>
- *          <p>We recommend that you create a mount target in each of the Availability Zones. There
- *       are cost considerations for using a file system in an Availability Zone through a mount target
- *       created in another Availability Zone. For more information, see <a href="http://aws.amazon.com/efs/">Amazon EFS</a>. In addition, by always using a mount target local to the
- *       instance's Availability Zone, you eliminate a partial failure scenario. If the
- *       Availability Zone in which your mount target is created goes down, then you can't access
- *       your file system through that mount target. </p>
- *          <p>This operation requires permissions for the following action on the file
- *       system:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <code>elasticfilesystem:CreateMountTarget</code>
- *                </p>
- *             </li>
- *          </ul>
- *          <p>This operation also requires permissions for the following Amazon EC2
- *       actions:</p>
- *          <ul>
- *             <li>
- *                <p>
- *                   <code>ec2:DescribeSubnets</code>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <code>ec2:DescribeNetworkInterfaces</code>
- *                </p>
- *             </li>
- *             <li>
- *                <p>
- *                   <code>ec2:CreateNetworkInterface</code>
- *                </p>
- *             </li>
- *          </ul>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { EFSClient, CreateMountTargetCommand } from "@aws-sdk/client-efs"; // ES Modules import
- * // const { EFSClient, CreateMountTargetCommand } = require("@aws-sdk/client-efs"); // CommonJS import
- * const client = new EFSClient(config);
- * const command = new CreateMountTargetCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateMountTargetCommandInput} for command's `input` shape.
- * @see {@link CreateMountTargetCommandOutput} for command's `response` shape.
- * @see {@link EFSClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class CreateMountTargetCommand extends $Command<CreateMountTargetCommandInput, CreateMountTargetCommandOutput, EFSClientResolvedConfig> {
     readonly input: CreateMountTargetCommandInput;
     constructor(input: CreateMountTargetCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: EFSClientResolvedConfig, options?: __HttpHandlerOptions): Handler<CreateMountTargetCommandInput, CreateMountTargetCommandOutput>;
     private serialize;
     private deserialize;

package/dist-types/ts3.4/commands/CreateTagsCommand.d.ts

@@ -6,40 +6,11 @@ export interface CreateTagsCommandInput extends CreateTagsRequest {
 }
 export interface CreateTagsCommandOutput extends __MetadataBearer {
 }
-/**
- * @deprecated
- *
- * <note>
- *             <p>DEPRECATED - CreateTags is deprecated and not maintained. Please use the
- *        API action to create tags for EFS resources.</p>
- *          </note>
- *          <p>Creates or overwrites tags associated with a file system. Each tag is a key-value pair. If
- *       a tag key specified in the request already exists on the file system, this operation
- *       overwrites its value with the value provided in the request. If you add the <code>Name</code>
- *       tag to your file system, Amazon EFS returns it in the response to the <a>DescribeFileSystems</a> operation. </p>
- *          <p>This operation requires permission for the <code>elasticfilesystem:CreateTags</code>
- *       action.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { EFSClient, CreateTagsCommand } from "@aws-sdk/client-efs"; // ES Modules import
- * // const { EFSClient, CreateTagsCommand } = require("@aws-sdk/client-efs"); // CommonJS import
- * const client = new EFSClient(config);
- * const command = new CreateTagsCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link CreateTagsCommandInput} for command's `input` shape.
- * @see {@link CreateTagsCommandOutput} for command's `response` shape.
- * @see {@link EFSClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class CreateTagsCommand extends $Command<CreateTagsCommandInput, CreateTagsCommandOutput, EFSClientResolvedConfig> {
     readonly input: CreateTagsCommandInput;
     constructor(input: CreateTagsCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: EFSClientResolvedConfig, options?: __HttpHandlerOptions): Handler<CreateTagsCommandInput, CreateTagsCommandOutput>;
     private serialize;
     private deserialize;

package/dist-types/ts3.4/commands/DeleteAccessPointCommand.d.ts

@@ -6,32 +6,11 @@ export interface DeleteAccessPointCommandInput extends DeleteAccessPointRequest
 }
 export interface DeleteAccessPointCommandOutput extends __MetadataBearer {
 }
-/**
- * <p>Deletes the specified access point. After deletion is complete, new clients can no
- *       longer connect to the access points. Clients connected to the access point at the time of
- *       deletion will continue to function until they terminate their connection.</p>
- *          <p>This operation requires permissions for the <code>elasticfilesystem:DeleteAccessPoint</code> action.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { EFSClient, DeleteAccessPointCommand } from "@aws-sdk/client-efs"; // ES Modules import
- * // const { EFSClient, DeleteAccessPointCommand } = require("@aws-sdk/client-efs"); // CommonJS import
- * const client = new EFSClient(config);
- * const command = new DeleteAccessPointCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link DeleteAccessPointCommandInput} for command's `input` shape.
- * @see {@link DeleteAccessPointCommandOutput} for command's `response` shape.
- * @see {@link EFSClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class DeleteAccessPointCommand extends $Command<DeleteAccessPointCommandInput, DeleteAccessPointCommandOutput, EFSClientResolvedConfig> {
     readonly input: DeleteAccessPointCommandInput;
     constructor(input: DeleteAccessPointCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: EFSClientResolvedConfig, options?: __HttpHandlerOptions): Handler<DeleteAccessPointCommandInput, DeleteAccessPointCommandOutput>;
     private serialize;
     private deserialize;

package/dist-types/ts3.4/commands/DeleteFileSystemCommand.d.ts

@@ -6,43 +6,11 @@ export interface DeleteFileSystemCommandInput extends DeleteFileSystemRequest {
 }
 export interface DeleteFileSystemCommandOutput extends __MetadataBearer {
 }
-/**
- * <p>Deletes a file system, permanently severing access to its contents. Upon return, the
- *       file system no longer exists and you can't access any contents of the deleted file
- *       system.</p>
- *          <p> You can't delete a file system that is in use. That is, if the file system has
- *       any mount targets, you must first delete them. For more information, see <a>DescribeMountTargets</a> and <a>DeleteMountTarget</a>. </p>
- *
- *          <note>
- *             <p>The <code>DeleteFileSystem</code> call returns while the file system state is still
- *           <code>deleting</code>. You can check the file system deletion status by calling the <a>DescribeFileSystems</a> operation, which returns a list of file systems in your
- *         account. If you pass file system ID or creation token for the deleted file system, the <a>DescribeFileSystems</a> returns a <code>404 FileSystemNotFound</code>
- *         error.</p>
- *          </note>
- *
- *          <p>This operation requires permissions for the
- *         <code>elasticfilesystem:DeleteFileSystem</code> action.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { EFSClient, DeleteFileSystemCommand } from "@aws-sdk/client-efs"; // ES Modules import
- * // const { EFSClient, DeleteFileSystemCommand } = require("@aws-sdk/client-efs"); // CommonJS import
- * const client = new EFSClient(config);
- * const command = new DeleteFileSystemCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link DeleteFileSystemCommandInput} for command's `input` shape.
- * @see {@link DeleteFileSystemCommandOutput} for command's `response` shape.
- * @see {@link EFSClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class DeleteFileSystemCommand extends $Command<DeleteFileSystemCommandInput, DeleteFileSystemCommandOutput, EFSClientResolvedConfig> {
     readonly input: DeleteFileSystemCommandInput;
     constructor(input: DeleteFileSystemCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: EFSClientResolvedConfig, options?: __HttpHandlerOptions): Handler<DeleteFileSystemCommandInput, DeleteFileSystemCommandOutput>;
     private serialize;
     private deserialize;

package/dist-types/ts3.4/commands/DeleteFileSystemPolicyCommand.d.ts

@@ -6,32 +6,11 @@ export interface DeleteFileSystemPolicyCommandInput extends DeleteFileSystemPoli
 }
 export interface DeleteFileSystemPolicyCommandOutput extends __MetadataBearer {
 }
-/**
- * <p>Deletes the <code>FileSystemPolicy</code> for the specified file system.
- *       The default <code>FileSystemPolicy</code> goes into effect once the existing policy is deleted.
- *       For more information about the default file system policy, see <a href="https://docs.aws.amazon.com/efs/latest/ug/res-based-policies-efs.html">Using Resource-based Policies with EFS</a>.</p>
- *          <p>This operation requires permissions for the <code>elasticfilesystem:DeleteFileSystemPolicy</code> action.</p>
- * @example
- * Use a bare-bones client and the command you need to make an API call.
- * ```javascript
- * import { EFSClient, DeleteFileSystemPolicyCommand } from "@aws-sdk/client-efs"; // ES Modules import
- * // const { EFSClient, DeleteFileSystemPolicyCommand } = require("@aws-sdk/client-efs"); // CommonJS import
- * const client = new EFSClient(config);
- * const command = new DeleteFileSystemPolicyCommand(input);
- * const response = await client.send(command);
- * ```
- *
- * @see {@link DeleteFileSystemPolicyCommandInput} for command's `input` shape.
- * @see {@link DeleteFileSystemPolicyCommandOutput} for command's `response` shape.
- * @see {@link EFSClientResolvedConfig | config} for command's `input` shape.
- *
- */
+
 export declare class DeleteFileSystemPolicyCommand extends $Command<DeleteFileSystemPolicyCommandInput, DeleteFileSystemPolicyCommandOutput, EFSClientResolvedConfig> {
     readonly input: DeleteFileSystemPolicyCommandInput;
     constructor(input: DeleteFileSystemPolicyCommandInput);
-    /**
-     * @internal
-     */
+    
     resolveMiddleware(clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>, configuration: EFSClientResolvedConfig, options?: __HttpHandlerOptions): Handler<DeleteFileSystemPolicyCommandInput, DeleteFileSystemPolicyCommandOutput>;
     private serialize;
     private deserialize;