import type { MetadataBearer as __MetadataBearer } from "@smithy/types"; import type { AssociateFileSystemAliasesRequest, AssociateFileSystemAliasesResponse } from "../models/models_0"; /** * @public */ export type { __MetadataBearer }; /** * @public * * The input for {@link AssociateFileSystemAliasesCommand}. */ export interface AssociateFileSystemAliasesCommandInput extends AssociateFileSystemAliasesRequest { } /** * @public * * The output of {@link AssociateFileSystemAliasesCommand}. */ export interface AssociateFileSystemAliasesCommandOutput extends AssociateFileSystemAliasesResponse, __MetadataBearer { } declare const AssociateFileSystemAliasesCommand_base: { new (input: AssociateFileSystemAliasesCommandInput): import("@smithy/core/client").CommandImpl; new (input: AssociateFileSystemAliasesCommandInput): import("@smithy/core/client").CommandImpl; getEndpointParameterInstructions(): import("@smithy/types").EndpointParameterInstructions; }; /** *

Use this action to associate one or more Domain Name Server (DNS) aliases with an existing Amazon FSx for Windows File Server file system. * A file system can have a maximum of 50 DNS aliases associated with it at any one time. If you try to * associate a DNS alias that is already associated with the file system, FSx takes no action on that alias in the request. * For more information, see Working with DNS Aliases and * Walkthrough 5: Using DNS aliases to access your file system, including * additional steps you must take to be able to access your file system using a DNS alias.

*

The system response shows the DNS aliases that * Amazon FSx is attempting to associate with the file system. * Use the API * operation to monitor the status of the aliases Amazon FSx is * associating with the file system.

* @example * Use a bare-bones client and the command you need to make an API call. * ```javascript * import { FSxClient, AssociateFileSystemAliasesCommand } from "@aws-sdk/client-fsx"; // ES Modules import * // const { FSxClient, AssociateFileSystemAliasesCommand } = require("@aws-sdk/client-fsx"); // CommonJS import * // import type { FSxClientConfig } from "@aws-sdk/client-fsx"; * const config = {}; // type is FSxClientConfig * const client = new FSxClient(config); * const input = { // AssociateFileSystemAliasesRequest * ClientRequestToken: "STRING_VALUE", * FileSystemId: "STRING_VALUE", // required * Aliases: [ // AlternateDNSNames // required * "STRING_VALUE", * ], * }; * const command = new AssociateFileSystemAliasesCommand(input); * const response = await client.send(command); * // { // AssociateFileSystemAliasesResponse * // Aliases: [ // Aliases * // { // Alias * // Name: "STRING_VALUE", * // Lifecycle: "AVAILABLE" || "CREATING" || "DELETING" || "CREATE_FAILED" || "DELETE_FAILED", * // }, * // ], * // }; * * ``` * * @param AssociateFileSystemAliasesCommandInput - {@link AssociateFileSystemAliasesCommandInput} * @returns {@link AssociateFileSystemAliasesCommandOutput} * @see {@link AssociateFileSystemAliasesCommandInput} for command's `input` shape. * @see {@link AssociateFileSystemAliasesCommandOutput} for command's `response` shape. * @see {@link FSxClientResolvedConfig | config} for FSxClient's `config` shape. * * @throws {@link BadRequest} (client fault) *

A generic error indicating a failure with a client request.

* * @throws {@link FileSystemNotFound} (client fault) *

No Amazon FSx file systems were found based upon supplied parameters.

* * @throws {@link InternalServerError} (server fault) *

A generic error indicating a server-side failure.

* * @throws {@link FSxServiceException} *

Base exception class for all service exceptions from FSx service.

* * * @public */ export declare class AssociateFileSystemAliasesCommand extends AssociateFileSystemAliasesCommand_base { /** @internal type navigation helper, not in runtime. */ protected static __types: { api: { input: AssociateFileSystemAliasesRequest; output: AssociateFileSystemAliasesResponse; }; sdk: { input: AssociateFileSystemAliasesCommandInput; output: AssociateFileSystemAliasesCommandOutput; }; }; }