@aws-sdk/client-efs 3.32.0 → 3.36.0

package/commands/CreateMountTargetCommand.ts

@@ -1,235 +0,0 @@
-import { EFSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../EFSClient";
-import { CreateMountTargetRequest, MountTargetDescription } from "../models/models_0";
-import {
-  deserializeAws_restJson1CreateMountTargetCommand,
-  serializeAws_restJson1CreateMountTargetCommand,
-} from "../protocols/Aws_restJson1";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-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 class CreateMountTargetCommand extends $Command<
-  CreateMountTargetCommandInput,
-  CreateMountTargetCommandOutput,
-  EFSClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: CreateMountTargetCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: EFSClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<CreateMountTargetCommandInput, CreateMountTargetCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "EFSClient";
-    const commandName = "CreateMountTargetCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: CreateMountTargetRequest.filterSensitiveLog,
-      outputFilterSensitiveLog: MountTargetDescription.filterSensitiveLog,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: CreateMountTargetCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_restJson1CreateMountTargetCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<CreateMountTargetCommandOutput> {
-    return deserializeAws_restJson1CreateMountTargetCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}

package/commands/CreateTagsCommand.ts

@@ -1,105 +0,0 @@
-import { EFSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../EFSClient";
-import { CreateTagsRequest } from "../models/models_0";
-import {
-  deserializeAws_restJson1CreateTagsCommand,
-  serializeAws_restJson1CreateTagsCommand,
-} from "../protocols/Aws_restJson1";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-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 class CreateTagsCommand extends $Command<
-  CreateTagsCommandInput,
-  CreateTagsCommandOutput,
-  EFSClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: CreateTagsCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: EFSClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<CreateTagsCommandInput, CreateTagsCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "EFSClient";
-    const commandName = "CreateTagsCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: CreateTagsRequest.filterSensitiveLog,
-      outputFilterSensitiveLog: (output: any) => output,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: CreateTagsCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_restJson1CreateTagsCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<CreateTagsCommandOutput> {
-    return deserializeAws_restJson1CreateTagsCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}

package/commands/DeleteAccessPointCommand.ts

@@ -1,97 +0,0 @@
-import { EFSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../EFSClient";
-import { DeleteAccessPointRequest } from "../models/models_0";
-import {
-  deserializeAws_restJson1DeleteAccessPointCommand,
-  serializeAws_restJson1DeleteAccessPointCommand,
-} from "../protocols/Aws_restJson1";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-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 class DeleteAccessPointCommand extends $Command<
-  DeleteAccessPointCommandInput,
-  DeleteAccessPointCommandOutput,
-  EFSClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: DeleteAccessPointCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: EFSClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<DeleteAccessPointCommandInput, DeleteAccessPointCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "EFSClient";
-    const commandName = "DeleteAccessPointCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: DeleteAccessPointRequest.filterSensitiveLog,
-      outputFilterSensitiveLog: (output: any) => output,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: DeleteAccessPointCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_restJson1DeleteAccessPointCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<DeleteAccessPointCommandOutput> {
-    return deserializeAws_restJson1DeleteAccessPointCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}

package/commands/DeleteFileSystemCommand.ts

@@ -1,108 +0,0 @@
-import { EFSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../EFSClient";
-import { DeleteFileSystemRequest } from "../models/models_0";
-import {
-  deserializeAws_restJson1DeleteFileSystemCommand,
-  serializeAws_restJson1DeleteFileSystemCommand,
-} from "../protocols/Aws_restJson1";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-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 class DeleteFileSystemCommand extends $Command<
-  DeleteFileSystemCommandInput,
-  DeleteFileSystemCommandOutput,
-  EFSClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: DeleteFileSystemCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: EFSClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<DeleteFileSystemCommandInput, DeleteFileSystemCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "EFSClient";
-    const commandName = "DeleteFileSystemCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: DeleteFileSystemRequest.filterSensitiveLog,
-      outputFilterSensitiveLog: (output: any) => output,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: DeleteFileSystemCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_restJson1DeleteFileSystemCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<DeleteFileSystemCommandOutput> {
-    return deserializeAws_restJson1DeleteFileSystemCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}

package/commands/DeleteFileSystemPolicyCommand.ts

@@ -1,97 +0,0 @@
-import { EFSClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../EFSClient";
-import { DeleteFileSystemPolicyRequest } from "../models/models_0";
-import {
-  deserializeAws_restJson1DeleteFileSystemPolicyCommand,
-  serializeAws_restJson1DeleteFileSystemPolicyCommand,
-} from "../protocols/Aws_restJson1";
-import { getSerdePlugin } from "@aws-sdk/middleware-serde";
-import { HttpRequest as __HttpRequest, HttpResponse as __HttpResponse } from "@aws-sdk/protocol-http";
-import { Command as $Command } from "@aws-sdk/smithy-client";
-import {
-  FinalizeHandlerArguments,
-  Handler,
-  HandlerExecutionContext,
-  MiddlewareStack,
-  HttpHandlerOptions as __HttpHandlerOptions,
-  MetadataBearer as __MetadataBearer,
-  SerdeContext as __SerdeContext,
-} from "@aws-sdk/types";
-
-export interface DeleteFileSystemPolicyCommandInput extends DeleteFileSystemPolicyRequest {}
-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 class DeleteFileSystemPolicyCommand extends $Command<
-  DeleteFileSystemPolicyCommandInput,
-  DeleteFileSystemPolicyCommandOutput,
-  EFSClientResolvedConfig
-> {
-  // Start section: command_properties
-  // End section: command_properties
-
-  constructor(readonly input: DeleteFileSystemPolicyCommandInput) {
-    // Start section: command_constructor
-    super();
-    // End section: command_constructor
-  }
-
-  /**
-   * @internal
-   */
-  resolveMiddleware(
-    clientStack: MiddlewareStack<ServiceInputTypes, ServiceOutputTypes>,
-    configuration: EFSClientResolvedConfig,
-    options?: __HttpHandlerOptions
-  ): Handler<DeleteFileSystemPolicyCommandInput, DeleteFileSystemPolicyCommandOutput> {
-    this.middlewareStack.use(getSerdePlugin(configuration, this.serialize, this.deserialize));
-
-    const stack = clientStack.concat(this.middlewareStack);
-
-    const { logger } = configuration;
-    const clientName = "EFSClient";
-    const commandName = "DeleteFileSystemPolicyCommand";
-    const handlerExecutionContext: HandlerExecutionContext = {
-      logger,
-      clientName,
-      commandName,
-      inputFilterSensitiveLog: DeleteFileSystemPolicyRequest.filterSensitiveLog,
-      outputFilterSensitiveLog: (output: any) => output,
-    };
-    const { requestHandler } = configuration;
-    return stack.resolve(
-      (request: FinalizeHandlerArguments<any>) =>
-        requestHandler.handle(request.request as __HttpRequest, options || {}),
-      handlerExecutionContext
-    );
-  }
-
-  private serialize(input: DeleteFileSystemPolicyCommandInput, context: __SerdeContext): Promise<__HttpRequest> {
-    return serializeAws_restJson1DeleteFileSystemPolicyCommand(input, context);
-  }
-
-  private deserialize(output: __HttpResponse, context: __SerdeContext): Promise<DeleteFileSystemPolicyCommandOutput> {
-    return deserializeAws_restJson1DeleteFileSystemPolicyCommand(output, context);
-  }
-
-  // Start section: command_body_extra
-  // End section: command_body_extra
-}