@aws-sdk/client-transfer 3.907.0 → 3.910.0

package/dist-cjs/endpoint/ruleset.js

@@ -2,6 +2,6 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ruleSet = void 0;
 const s = "required", t = "fn", u = "argv", v = "ref";
-const a = true, b = "isSet", c = "booleanEquals", d = "error", e = "endpoint", f = "tree", g = "PartitionResult", h = { [s]: false, "type": "String" }, i = { [s]: true, "default": false, "type": "Boolean" }, j = { [v]: "Endpoint" }, k = { [t]: c, [u]: [{ [v]: "UseFIPS" }, true] }, l = { [t]: c, [u]: [{ [v]: "UseDualStack" }, true] }, m = {}, n = { [t]: "getAttr", [u]: [{ [v]: g }, "supportsFIPS"] }, o = { [t]: c, [u]: [true, { [t]: "getAttr", [u]: [{ [v]: g }, "supportsDualStack"] }] }, p = [k], q = [l], r = [{ [v]: "Region" }];
+const a = true, b = "isSet", c = "booleanEquals", d = "error", e = "endpoint", f = "tree", g = "PartitionResult", h = { [s]: false, "type": "string" }, i = { [s]: true, "default": false, "type": "boolean" }, j = { [v]: "Endpoint" }, k = { [t]: c, [u]: [{ [v]: "UseFIPS" }, true] }, l = { [t]: c, [u]: [{ [v]: "UseDualStack" }, true] }, m = {}, n = { [t]: "getAttr", [u]: [{ [v]: g }, "supportsFIPS"] }, o = { [t]: c, [u]: [true, { [t]: "getAttr", [u]: [{ [v]: g }, "supportsDualStack"] }] }, p = [k], q = [l], r = [{ [v]: "Region" }];
 const _data = { version: "1.0", parameters: { Region: h, UseDualStack: i, UseFIPS: i, Endpoint: h }, rules: [{ conditions: [{ [t]: b, [u]: [j] }], rules: [{ conditions: p, error: "Invalid Configuration: FIPS and custom endpoint are not supported", type: d }, { conditions: q, error: "Invalid Configuration: Dualstack and custom endpoint are not supported", type: d }, { endpoint: { url: j, properties: m, headers: m }, type: e }], type: f }, { conditions: [{ [t]: b, [u]: r }], rules: [{ conditions: [{ [t]: "aws.partition", [u]: r, assign: g }], rules: [{ conditions: [k, l], rules: [{ conditions: [{ [t]: c, [u]: [a, n] }, o], rules: [{ endpoint: { url: "https://transfer-fips.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: m, headers: m }, type: e }], type: f }, { error: "FIPS and DualStack are enabled, but this partition does not support one or both", type: d }], type: f }, { conditions: p, rules: [{ conditions: [{ [t]: c, [u]: [n, a] }], rules: [{ endpoint: { url: "https://transfer-fips.{Region}.{PartitionResult#dnsSuffix}", properties: m, headers: m }, type: e }], type: f }, { error: "FIPS is enabled but this partition does not support FIPS", type: d }], type: f }, { conditions: q, rules: [{ conditions: [o], rules: [{ endpoint: { url: "https://transfer.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: m, headers: m }, type: e }], type: f }, { error: "DualStack is enabled but this partition does not support DualStack", type: d }], type: f }, { endpoint: { url: "https://transfer.{Region}.{PartitionResult#dnsSuffix}", properties: m, headers: m }, type: e }], type: f }], type: f }, { error: "Invalid Configuration: Missing Region", type: d }] };
 exports.ruleSet = _data;

package/dist-cjs/index.js

@@ -315,12 +315,45 @@ class ConflictException extends TransferServiceException {
         this.Message = opts.Message;
     }
 }
+exports.ConnectorEgressConfig = void 0;
+(function (ConnectorEgressConfig) {
+    ConnectorEgressConfig.visit = (value, visitor) => {
+        if (value.VpcLattice !== undefined)
+            return visitor.VpcLattice(value.VpcLattice);
+        return visitor._(value.$unknown[0], value.$unknown[1]);
+    };
+})(exports.ConnectorEgressConfig || (exports.ConnectorEgressConfig = {}));
+const ConnectorEgressType = {
+    SERVICE_MANAGED: "SERVICE_MANAGED",
+    VPC_LATTICE: "VPC_LATTICE",
+};
 const TransferTableStatus = {
     COMPLETED: "COMPLETED",
     FAILED: "FAILED",
     IN_PROGRESS: "IN_PROGRESS",
     QUEUED: "QUEUED",
 };
+exports.DescribedConnectorEgressConfig = void 0;
+(function (DescribedConnectorEgressConfig) {
+    DescribedConnectorEgressConfig.visit = (value, visitor) => {
+        if (value.VpcLattice !== undefined)
+            return visitor.VpcLattice(value.VpcLattice);
+        return visitor._(value.$unknown[0], value.$unknown[1]);
+    };
+})(exports.DescribedConnectorEgressConfig || (exports.DescribedConnectorEgressConfig = {}));
+const ConnectorStatus = {
+    ACTIVE: "ACTIVE",
+    ERRORED: "ERRORED",
+    PENDING: "PENDING",
+};
+exports.UpdateConnectorEgressConfig = void 0;
+(function (UpdateConnectorEgressConfig) {
+    UpdateConnectorEgressConfig.visit = (value, visitor) => {
+        if (value.VpcLattice !== undefined)
+            return visitor.VpcLattice(value.VpcLattice);
+        return visitor._(value.$unknown[0], value.$unknown[1]);
+    };
+})(exports.UpdateConnectorEgressConfig || (exports.UpdateConnectorEgressConfig = {}));
 const OverwriteExisting = {
     FALSE: "FALSE",
     TRUE: "TRUE",
@@ -3536,6 +3569,8 @@ exports.CertificateType = CertificateType;
 exports.CertificateUsageType = CertificateUsageType;
 exports.CompressionEnum = CompressionEnum;
 exports.ConflictException = ConflictException;
+exports.ConnectorEgressType = ConnectorEgressType;
+exports.ConnectorStatus = ConnectorStatus;
 exports.CreateAccessCommand = CreateAccessCommand;
 exports.CreateAgreementCommand = CreateAgreementCommand;
 exports.CreateConnectorCommand = CreateConnectorCommand;

package/dist-es/endpoint/ruleset.js

@@ -1,4 +1,4 @@
 const s = "required", t = "fn", u = "argv", v = "ref";
-const a = true, b = "isSet", c = "booleanEquals", d = "error", e = "endpoint", f = "tree", g = "PartitionResult", h = { [s]: false, "type": "String" }, i = { [s]: true, "default": false, "type": "Boolean" }, j = { [v]: "Endpoint" }, k = { [t]: c, [u]: [{ [v]: "UseFIPS" }, true] }, l = { [t]: c, [u]: [{ [v]: "UseDualStack" }, true] }, m = {}, n = { [t]: "getAttr", [u]: [{ [v]: g }, "supportsFIPS"] }, o = { [t]: c, [u]: [true, { [t]: "getAttr", [u]: [{ [v]: g }, "supportsDualStack"] }] }, p = [k], q = [l], r = [{ [v]: "Region" }];
+const a = true, b = "isSet", c = "booleanEquals", d = "error", e = "endpoint", f = "tree", g = "PartitionResult", h = { [s]: false, "type": "string" }, i = { [s]: true, "default": false, "type": "boolean" }, j = { [v]: "Endpoint" }, k = { [t]: c, [u]: [{ [v]: "UseFIPS" }, true] }, l = { [t]: c, [u]: [{ [v]: "UseDualStack" }, true] }, m = {}, n = { [t]: "getAttr", [u]: [{ [v]: g }, "supportsFIPS"] }, o = { [t]: c, [u]: [true, { [t]: "getAttr", [u]: [{ [v]: g }, "supportsDualStack"] }] }, p = [k], q = [l], r = [{ [v]: "Region" }];
 const _data = { version: "1.0", parameters: { Region: h, UseDualStack: i, UseFIPS: i, Endpoint: h }, rules: [{ conditions: [{ [t]: b, [u]: [j] }], rules: [{ conditions: p, error: "Invalid Configuration: FIPS and custom endpoint are not supported", type: d }, { conditions: q, error: "Invalid Configuration: Dualstack and custom endpoint are not supported", type: d }, { endpoint: { url: j, properties: m, headers: m }, type: e }], type: f }, { conditions: [{ [t]: b, [u]: r }], rules: [{ conditions: [{ [t]: "aws.partition", [u]: r, assign: g }], rules: [{ conditions: [k, l], rules: [{ conditions: [{ [t]: c, [u]: [a, n] }, o], rules: [{ endpoint: { url: "https://transfer-fips.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: m, headers: m }, type: e }], type: f }, { error: "FIPS and DualStack are enabled, but this partition does not support one or both", type: d }], type: f }, { conditions: p, rules: [{ conditions: [{ [t]: c, [u]: [n, a] }], rules: [{ endpoint: { url: "https://transfer-fips.{Region}.{PartitionResult#dnsSuffix}", properties: m, headers: m }, type: e }], type: f }, { error: "FIPS is enabled but this partition does not support FIPS", type: d }], type: f }, { conditions: q, rules: [{ conditions: [o], rules: [{ endpoint: { url: "https://transfer.{Region}.{PartitionResult#dualStackDnsSuffix}", properties: m, headers: m }, type: e }], type: f }, { error: "DualStack is enabled but this partition does not support DualStack", type: d }], type: f }, { endpoint: { url: "https://transfer.{Region}.{PartitionResult#dnsSuffix}", properties: m, headers: m }, type: e }], type: f }], type: f }, { error: "Invalid Configuration: Missing Region", type: d }] };
 export const ruleSet = _data;

package/dist-es/models/models_0.js

@@ -197,12 +197,45 @@ export class ConflictException extends __BaseException {
         this.Message = opts.Message;
     }
 }
+export var ConnectorEgressConfig;
+(function (ConnectorEgressConfig) {
+    ConnectorEgressConfig.visit = (value, visitor) => {
+        if (value.VpcLattice !== undefined)
+            return visitor.VpcLattice(value.VpcLattice);
+        return visitor._(value.$unknown[0], value.$unknown[1]);
+    };
+})(ConnectorEgressConfig || (ConnectorEgressConfig = {}));
+export const ConnectorEgressType = {
+    SERVICE_MANAGED: "SERVICE_MANAGED",
+    VPC_LATTICE: "VPC_LATTICE",
+};
 export const TransferTableStatus = {
     COMPLETED: "COMPLETED",
     FAILED: "FAILED",
     IN_PROGRESS: "IN_PROGRESS",
     QUEUED: "QUEUED",
 };
+export var DescribedConnectorEgressConfig;
+(function (DescribedConnectorEgressConfig) {
+    DescribedConnectorEgressConfig.visit = (value, visitor) => {
+        if (value.VpcLattice !== undefined)
+            return visitor.VpcLattice(value.VpcLattice);
+        return visitor._(value.$unknown[0], value.$unknown[1]);
+    };
+})(DescribedConnectorEgressConfig || (DescribedConnectorEgressConfig = {}));
+export const ConnectorStatus = {
+    ACTIVE: "ACTIVE",
+    ERRORED: "ERRORED",
+    PENDING: "PENDING",
+};
+export var UpdateConnectorEgressConfig;
+(function (UpdateConnectorEgressConfig) {
+    UpdateConnectorEgressConfig.visit = (value, visitor) => {
+        if (value.VpcLattice !== undefined)
+            return visitor.VpcLattice(value.VpcLattice);
+        return visitor._(value.$unknown[0], value.$unknown[1]);
+    };
+})(UpdateConnectorEgressConfig || (UpdateConnectorEgressConfig = {}));
 export const OverwriteExisting = {
     FALSE: "FALSE",
     TRUE: "TRUE",

package/dist-types/commands/CreateConnectorCommand.d.ts

@@ -37,7 +37,7 @@ declare const CreateConnectorCommand_base: {
  * const config = {}; // type is TransferClientConfig
  * const client = new TransferClient(config);
  * const input = { // CreateConnectorRequest
- *   Url: "STRING_VALUE", // required
+ *   Url: "STRING_VALUE",
  *   As2Config: { // As2ConnectorConfig
  *     LocalProfileId: "STRING_VALUE",
  *     PartnerProfileId: "STRING_VALUE",
@@ -66,6 +66,12 @@ declare const CreateConnectorCommand_base: {
  *     MaxConcurrentConnections: Number("int"),
  *   },
  *   SecurityPolicyName: "STRING_VALUE",
+ *   EgressConfig: { // ConnectorEgressConfig Union: only one key present
+ *     VpcLattice: { // ConnectorVpcLatticeEgressConfig
+ *       ResourceConfigurationArn: "STRING_VALUE", // required
+ *       PortNumber: Number("int"),
+ *     },
+ *   },
  * };
  * const command = new CreateConnectorCommand(input);
  * const response = await client.send(command);

package/dist-types/commands/DescribeConnectorCommand.d.ts

@@ -77,6 +77,15 @@ declare const DescribeConnectorCommand_base: {
  * //       "STRING_VALUE",
  * //     ],
  * //     SecurityPolicyName: "STRING_VALUE",
+ * //     EgressConfig: { // DescribedConnectorEgressConfig Union: only one key present
+ * //       VpcLattice: { // DescribedConnectorVpcLatticeEgressConfig
+ * //         ResourceConfigurationArn: "STRING_VALUE", // required
+ * //         PortNumber: Number("int"),
+ * //       },
+ * //     },
+ * //     EgressType: "SERVICE_MANAGED" || "VPC_LATTICE", // required
+ * //     ErrorMessage: "STRING_VALUE",
+ * //     Status: "ACTIVE" || "ERRORED" || "PENDING", // required
  * //   },
  * // };
  *

package/dist-types/commands/UpdateConnectorCommand.d.ts

@@ -61,6 +61,12 @@ declare const UpdateConnectorCommand_base: {
  *     MaxConcurrentConnections: Number("int"),
  *   },
  *   SecurityPolicyName: "STRING_VALUE",
+ *   EgressConfig: { // UpdateConnectorEgressConfig Union: only one key present
+ *     VpcLattice: { // UpdateConnectorVpcLatticeEgressConfig
+ *       ResourceConfigurationArn: "STRING_VALUE",
+ *       PortNumber: Number("int"),
+ *     },
+ *   },
  * };
  * const command = new UpdateConnectorCommand(input);
  * const response = await client.send(command);

package/dist-types/models/models_0.d.ts

@@ -990,6 +990,64 @@ export declare class ConflictException extends __BaseException {
      */
     constructor(opts: __ExceptionOptionType<ConflictException, __BaseException>);
 }
+/**
+ * <p>VPC_LATTICE egress configuration that specifies the Resource Configuration ARN and port for connecting to SFTP servers through customer VPCs. Requires a valid Resource Configuration with appropriate network access.</p>
+ * @public
+ */
+export interface ConnectorVpcLatticeEgressConfig {
+    /**
+     * <p>ARN of the VPC_LATTICE Resource Configuration that defines the target SFTP server location. Must point to a valid Resource Configuration in the customer's VPC with appropriate network connectivity to the SFTP server.</p>
+     * @public
+     */
+    ResourceConfigurationArn: string | undefined;
+    /**
+     * <p>Port number for connecting to the SFTP server through VPC_LATTICE. Defaults to 22 if not specified. Must match the port on which the target SFTP server is listening.</p>
+     * @public
+     */
+    PortNumber?: number | undefined;
+}
+/**
+ * <p>Configuration structure that defines how traffic is routed from the connector to the SFTP server. Contains VPC Lattice settings when using VPC_LATTICE egress type for private connectivity through customer VPCs.</p>
+ * @public
+ */
+export type ConnectorEgressConfig = ConnectorEgressConfig.VpcLatticeMember | ConnectorEgressConfig.$UnknownMember;
+/**
+ * @public
+ */
+export declare namespace ConnectorEgressConfig {
+    /**
+     * <p>VPC_LATTICE configuration for routing connector traffic through customer VPCs. Enables private connectivity to SFTP servers without requiring public internet access or complex network configurations.</p>
+     * @public
+     */
+    interface VpcLatticeMember {
+        VpcLattice: ConnectorVpcLatticeEgressConfig;
+        $unknown?: never;
+    }
+    /**
+     * @public
+     */
+    interface $UnknownMember {
+        VpcLattice?: never;
+        $unknown: [string, any];
+    }
+    interface Visitor<T> {
+        VpcLattice: (value: ConnectorVpcLatticeEgressConfig) => T;
+        _: (name: string, value: any) => T;
+    }
+    const visit: <T>(value: ConnectorEgressConfig, visitor: Visitor<T>) => T;
+}
+/**
+ * @public
+ * @enum
+ */
+export declare const ConnectorEgressType: {
+    readonly SERVICE_MANAGED: "SERVICE_MANAGED";
+    readonly VPC_LATTICE: "VPC_LATTICE";
+};
+/**
+ * @public
+ */
+export type ConnectorEgressType = (typeof ConnectorEgressType)[keyof typeof ConnectorEgressType];
 /**
  * @public
  * @enum
@@ -1041,7 +1099,7 @@ export interface SftpConnectorConfig {
      */
     UserSecretId?: string | undefined;
     /**
-     * <p>The public portion of the host key, or keys, that are used to identify the external server to which you are connecting. You can use the <code>ssh-keyscan</code> command against the SFTP server to retrieve the necessary key.</p> <note> <p> <code>TrustedHostKeys</code> is optional for <code>CreateConnector</code>. If not provided, you can use <code>TestConnection</code> to retrieve the server host key during the initial connection attempt, and subsequently update the connector with the observed host key.</p> </note> <p>The three standard SSH public key format elements are <code>&lt;key type&gt;</code>, <code>&lt;body base64&gt;</code>, and an optional <code>&lt;comment&gt;</code>, with spaces between each element. Specify only the <code>&lt;key type&gt;</code> and <code>&lt;body base64&gt;</code>: do not enter the <code>&lt;comment&gt;</code> portion of the key.</p> <p>For the trusted host key, Transfer Family accepts RSA and ECDSA keys.</p> <ul> <li> <p>For RSA keys, the <code>&lt;key type&gt;</code> string is <code>ssh-rsa</code>.</p> </li> <li> <p>For ECDSA keys, the <code>&lt;key type&gt;</code> string is either <code>ecdsa-sha2-nistp256</code>, <code>ecdsa-sha2-nistp384</code>, or <code>ecdsa-sha2-nistp521</code>, depending on the size of the key you generated.</p> </li> </ul> <p>Run this command to retrieve the SFTP server host key, where your SFTP server name is <code>ftp.host.com</code>.</p> <p> <code>ssh-keyscan ftp.host.com</code> </p> <p>This prints the public host key to standard output.</p> <p> <code>ftp.host.com ssh-rsa AAAAB3Nza...&lt;long-string-for-public-key</code> </p> <p>Copy and paste this string into the <code>TrustedHostKeys</code> field for the <code>create-connector</code> command or into the <b>Trusted host keys</b> field in the console.</p>
+     * <p>The public portion of the host key, or keys, that are used to identify the external server to which you are connecting. You can use the <code>ssh-keyscan</code> command against the SFTP server to retrieve the necessary key.</p> <note> <p> <code>TrustedHostKeys</code> is optional for <code>CreateConnector</code>. If not provided, you can use <code>TestConnection</code> to retrieve the server host key during the initial connection attempt, and subsequently update the connector with the observed host key.</p> </note> <p>When creating connectors with egress config (VPC_LATTICE type connectors), since host name is not something we can verify, the only accepted trusted host key format is <code>key-type key-body</code> without the host name. For example: <code>ssh-rsa AAAAB3Nza...&lt;long-string-for-public-key&gt;</code> </p> <p>The three standard SSH public key format elements are <code>&lt;key type&gt;</code>, <code>&lt;body base64&gt;</code>, and an optional <code>&lt;comment&gt;</code>, with spaces between each element. Specify only the <code>&lt;key type&gt;</code> and <code>&lt;body base64&gt;</code>: do not enter the <code>&lt;comment&gt;</code> portion of the key.</p> <p>For the trusted host key, Transfer Family accepts RSA and ECDSA keys.</p> <ul> <li> <p>For RSA keys, the <code>&lt;key type&gt;</code> string is <code>ssh-rsa</code>.</p> </li> <li> <p>For ECDSA keys, the <code>&lt;key type&gt;</code> string is either <code>ecdsa-sha2-nistp256</code>, <code>ecdsa-sha2-nistp384</code>, or <code>ecdsa-sha2-nistp521</code>, depending on the size of the key you generated.</p> </li> </ul> <p>Run this command to retrieve the SFTP server host key, where your SFTP server name is <code>ftp.host.com</code>.</p> <p> <code>ssh-keyscan ftp.host.com</code> </p> <p>This prints the public host key to standard output.</p> <p> <code>ftp.host.com ssh-rsa AAAAB3Nza...&lt;long-string-for-public-key&gt;</code> </p> <p>Copy and paste this string into the <code>TrustedHostKeys</code> field for the <code>create-connector</code> command or into the <b>Trusted host keys</b> field in the console.</p> <p>For VPC Lattice type connectors (VPC_LATTICE), remove the hostname from the key and use only the <code>key-type key-body</code> format. In this example, it should be: <code>ssh-rsa AAAAB3Nza...&lt;long-string-for-public-key&gt;</code> </p>
      * @public
      */
     TrustedHostKeys?: string[] | undefined;
@@ -1056,10 +1114,10 @@ export interface SftpConnectorConfig {
  */
 export interface CreateConnectorRequest {
     /**
-     * <p>The URL of the partner's AS2 or SFTP endpoint.</p>
+     * <p>The URL of the partner's AS2 or SFTP endpoint.</p> <p>When creating AS2 connectors or service-managed SFTP connectors (connectors without egress configuration), you must provide a URL to specify the remote server endpoint. For VPC Lattice type connectors, the URL must be null.</p>
      * @public
      */
-    Url: string | undefined;
+    Url?: string | undefined;
     /**
      * <p>A structure that contains the parameters for an AS2 connector object.</p>
      * @public
@@ -1090,6 +1148,11 @@ export interface CreateConnectorRequest {
      * @public
      */
     SecurityPolicyName?: string | undefined;
+    /**
+     * <p>Specifies the egress configuration for the connector, which determines how traffic is routed from the connector to the SFTP server. When set to VPC, enables routing through customer VPCs using VPC_LATTICE for private connectivity.</p>
+     * @public
+     */
+    EgressConfig?: ConnectorEgressConfig | undefined;
 }
 /**
  * @public
@@ -1121,6 +1184,65 @@ export interface DescribeConnectorRequest {
      */
     ConnectorId: string | undefined;
 }
+/**
+ * <p>VPC_LATTICE egress configuration details in the response, containing the Resource Configuration ARN and port number currently configured for the connector.</p>
+ * @public
+ */
+export interface DescribedConnectorVpcLatticeEgressConfig {
+    /**
+     * <p>ARN of the VPC_LATTICE Resource Configuration currently used by the connector. This Resource Configuration defines the network path to the SFTP server through the customer's VPC.</p>
+     * @public
+     */
+    ResourceConfigurationArn: string | undefined;
+    /**
+     * <p>Port number currently configured for SFTP connections through VPC_LATTICE. Shows the port on which the connector attempts to connect to the target SFTP server.</p>
+     * @public
+     */
+    PortNumber?: number | undefined;
+}
+/**
+ * <p>Response structure containing the current egress configuration details for the connector. Shows how traffic is currently routed from the connector to the SFTP server.</p>
+ * @public
+ */
+export type DescribedConnectorEgressConfig = DescribedConnectorEgressConfig.VpcLatticeMember | DescribedConnectorEgressConfig.$UnknownMember;
+/**
+ * @public
+ */
+export declare namespace DescribedConnectorEgressConfig {
+    /**
+     * <p>VPC_LATTICE configuration details in the response, showing the current Resource Configuration ARN and port settings for VPC-based connectivity.</p>
+     * @public
+     */
+    interface VpcLatticeMember {
+        VpcLattice: DescribedConnectorVpcLatticeEgressConfig;
+        $unknown?: never;
+    }
+    /**
+     * @public
+     */
+    interface $UnknownMember {
+        VpcLattice?: never;
+        $unknown: [string, any];
+    }
+    interface Visitor<T> {
+        VpcLattice: (value: DescribedConnectorVpcLatticeEgressConfig) => T;
+        _: (name: string, value: any) => T;
+    }
+    const visit: <T>(value: DescribedConnectorEgressConfig, visitor: Visitor<T>) => T;
+}
+/**
+ * @public
+ * @enum
+ */
+export declare const ConnectorStatus: {
+    readonly ACTIVE: "ACTIVE";
+    readonly ERRORED: "ERRORED";
+    readonly PENDING: "PENDING";
+};
+/**
+ * @public
+ */
+export type ConnectorStatus = (typeof ConnectorStatus)[keyof typeof ConnectorStatus];
 /**
  * <p>Describes the parameters for the connector, as identified by the <code>ConnectorId</code>.</p>
  * @public
@@ -1137,7 +1259,7 @@ export interface DescribedConnector {
      */
     ConnectorId?: string | undefined;
     /**
-     * <p>The URL of the partner's AS2 or SFTP endpoint.</p>
+     * <p>The URL of the partner's AS2 or SFTP endpoint.</p> <p>When creating AS2 connectors or service-managed SFTP connectors (connectors without egress configuration), you must provide a URL to specify the remote server endpoint. For VPC Lattice type connectors, the URL must be null.</p>
      * @public
      */
     Url?: string | undefined;
@@ -1176,6 +1298,26 @@ export interface DescribedConnector {
      * @public
      */
     SecurityPolicyName?: string | undefined;
+    /**
+     * <p>Current egress configuration of the connector, showing how traffic is routed to the SFTP server. Contains VPC Lattice settings when using VPC_LATTICE egress type.</p> <p>When using the VPC_LATTICE egress type, Transfer Family uses a managed Service Network to simplify the resource sharing process.</p>
+     * @public
+     */
+    EgressConfig?: DescribedConnectorEgressConfig | undefined;
+    /**
+     * <p>Type of egress configuration for the connector. SERVICE_MANAGED uses Transfer Family managed NAT gateways, while VPC_LATTICE routes traffic through customer VPCs using VPC Lattice.</p>
+     * @public
+     */
+    EgressType: ConnectorEgressType | undefined;
+    /**
+     * <p>Error message providing details when the connector is in ERRORED status. Contains information to help troubleshoot connector creation or operation failures.</p>
+     * @public
+     */
+    ErrorMessage?: string | undefined;
+    /**
+     * <p>Current status of the connector. PENDING indicates creation/update in progress, ACTIVE means ready for operations, and ERRORED indicates a failure requiring attention.</p>
+     * @public
+     */
+    Status: ConnectorStatus | undefined;
 }
 /**
  * @public
@@ -1218,7 +1360,7 @@ export interface ListedConnector {
      */
     ConnectorId?: string | undefined;
     /**
-     * <p>The URL of the partner's AS2 or SFTP endpoint.</p>
+     * <p>The URL of the partner's AS2 or SFTP endpoint.</p> <p>When creating AS2 connectors or service-managed SFTP connectors (connectors without egress configuration), you must provide a URL to specify the remote server endpoint. For VPC Lattice type connectors, the URL must be null.</p>
      * @public
      */
     Url?: string | undefined;
@@ -1238,6 +1380,52 @@ export interface ListConnectorsResponse {
      */
     Connectors: ListedConnector[] | undefined;
 }
+/**
+ * <p>VPC_LATTICE egress configuration updates for modifying how the connector routes traffic through customer VPCs. Changes to these settings may require connector restart to take effect.</p>
+ * @public
+ */
+export interface UpdateConnectorVpcLatticeEgressConfig {
+    /**
+     * <p>Updated ARN of the VPC_LATTICE Resource Configuration. Use this to change the target SFTP server location or modify the network path through the customer's VPC infrastructure.</p>
+     * @public
+     */
+    ResourceConfigurationArn?: string | undefined;
+    /**
+     * <p>Updated port number for SFTP connections through VPC_LATTICE. Change this if the target SFTP server port has been modified or if connecting to a different server endpoint.</p>
+     * @public
+     */
+    PortNumber?: number | undefined;
+}
+/**
+ * <p>Structure for updating the egress configuration of an existing connector. Allows modification of how traffic is routed from the connector to the SFTP server, including VPC_LATTICE settings.</p>
+ * @public
+ */
+export type UpdateConnectorEgressConfig = UpdateConnectorEgressConfig.VpcLatticeMember | UpdateConnectorEgressConfig.$UnknownMember;
+/**
+ * @public
+ */
+export declare namespace UpdateConnectorEgressConfig {
+    /**
+     * <p>VPC_LATTICE configuration updates for the connector. Use this to modify the Resource Configuration ARN or port number for VPC-based connectivity.</p>
+     * @public
+     */
+    interface VpcLatticeMember {
+        VpcLattice: UpdateConnectorVpcLatticeEgressConfig;
+        $unknown?: never;
+    }
+    /**
+     * @public
+     */
+    interface $UnknownMember {
+        VpcLattice?: never;
+        $unknown: [string, any];
+    }
+    interface Visitor<T> {
+        VpcLattice: (value: UpdateConnectorVpcLatticeEgressConfig) => T;
+        _: (name: string, value: any) => T;
+    }
+    const visit: <T>(value: UpdateConnectorEgressConfig, visitor: Visitor<T>) => T;
+}
 /**
  * @public
  */
@@ -1248,7 +1436,7 @@ export interface UpdateConnectorRequest {
      */
     ConnectorId: string | undefined;
     /**
-     * <p>The URL of the partner's AS2 or SFTP endpoint.</p>
+     * <p>The URL of the partner's AS2 or SFTP endpoint.</p> <p>When creating AS2 connectors or service-managed SFTP connectors (connectors without egress configuration), you must provide a URL to specify the remote server endpoint. For VPC Lattice type connectors, the URL must be null.</p>
      * @public
      */
     Url?: string | undefined;
@@ -1277,6 +1465,11 @@ export interface UpdateConnectorRequest {
      * @public
      */
     SecurityPolicyName?: string | undefined;
+    /**
+     * <p>Updates the egress configuration for the connector, allowing you to modify how traffic is routed from the connector to the SFTP server. Changes to VPC configuration may require connector restart.</p>
+     * @public
+     */
+    EgressConfig?: UpdateConnectorEgressConfig | undefined;
 }
 /**
  * @public
@@ -1705,7 +1898,7 @@ export type TlsSessionResumptionMode = (typeof TlsSessionResumptionMode)[keyof t
  */
 export interface ProtocolDetails {
     /**
-     * <p> Indicates passive mode, for FTP and FTPS protocols. Enter a single IPv4 address, such as the public IP address of a firewall, router, or load balancer. For example: </p> <p> <code>aws transfer update-server --protocol-details PassiveIp=0.0.0.0</code> </p> <p>Replace <code>0.0.0.0</code> in the example above with the actual IP address you want to use.</p> <note> <p> If you change the <code>PassiveIp</code> value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see <a href="http://aws.amazon.com/blogs/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/">Configuring your FTPS server behind a firewall or NAT with Transfer Family</a>. </p> </note> <p> <i>Special values</i> </p> <p>The <code>AUTO</code> and <code>0.0.0.0</code> are special values for the <code>PassiveIp</code> parameter. The value <code>PassiveIp=AUTO</code> is assigned by default to FTP and FTPS type servers. In this case, the server automatically responds with one of the endpoint IPs within the PASV response. <code>PassiveIp=0.0.0.0</code> has a more unique application for its usage. For example, if you have a High Availability (HA) Network Load Balancer (NLB) environment, where you have 3 subnets, you can only specify a single IP address using the <code>PassiveIp</code> parameter. This reduces the effectiveness of having High Availability. In this case, you can specify <code>PassiveIp=0.0.0.0</code>. This tells the client to use the same IP address as the Control connection and utilize all AZs for their connections. Note, however, that not all FTP clients support the <code>PassiveIp=0.0.0.0</code> response. FileZilla and WinSCP do support it. If you are using other clients, check to see if your client supports the <code>PassiveIp=0.0.0.0</code> response.</p>
+     * <p> Indicates passive mode, for FTP and FTPS protocols. Enter a single IPv4 address, such as the public IP address of a firewall, router, or load balancer. For example: </p> <p> <code>aws transfer update-server --protocol-details PassiveIp=0.0.0.0</code> </p> <p>Replace <code>0.0.0.0</code> in the example above with the actual IP address you want to use.</p> <note> <p> If you change the <code>PassiveIp</code> value, you must stop and then restart your Transfer Family server for the change to take effect. For details on using passive mode (PASV) in a NAT environment, see <a href="http://aws.amazon.com/blogs/storage/configuring-your-ftps-server-behind-a-firewall-or-nat-with-aws-transfer-family/">Configuring your FTPS server behind a firewall or NAT with Transfer Family</a>. </p> <p>Additionally, avoid placing Network Load Balancers (NLBs) or NAT gateways in front of Transfer Family servers. This configuration increases costs and can cause performance issues. When NLBs or NATs are in the communication path, Transfer Family cannot accurately recognize client IP addresses, which impacts connection sharding and limits FTPS servers to only 300 simultaneous connections instead of 10,000. If you must use an NLB, use port 21 for health checks and enable TLS session resumption by setting <code>TlsSessionResumptionMode = ENFORCED</code>. For optimal performance, migrate to VPC endpoints with Elastic IP addresses instead of using NLBs. For more details, see <a href="https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations"> Avoid placing NLBs and NATs in front of Transfer Family</a>. </p> </note> <p> <i>Special values</i> </p> <p>The <code>AUTO</code> and <code>0.0.0.0</code> are special values for the <code>PassiveIp</code> parameter. The value <code>PassiveIp=AUTO</code> is assigned by default to FTP and FTPS type servers. In this case, the server automatically responds with one of the endpoint IPs within the PASV response. <code>PassiveIp=0.0.0.0</code> has a more unique application for its usage. For example, if you have a High Availability (HA) Network Load Balancer (NLB) environment, where you have 3 subnets, you can only specify a single IP address using the <code>PassiveIp</code> parameter. This reduces the effectiveness of having High Availability. In this case, you can specify <code>PassiveIp=0.0.0.0</code>. This tells the client to use the same IP address as the Control connection and utilize all AZs for their connections. Note, however, that not all FTP clients support the <code>PassiveIp=0.0.0.0</code> response. FileZilla and WinSCP do support it. If you are using other clients, check to see if your client supports the <code>PassiveIp=0.0.0.0</code> response.</p>
      * @public
      */
     PassiveIp?: string | undefined;
@@ -1854,7 +2047,7 @@ export interface CreateServerRequest {
      */
     Protocols?: Protocol[] | undefined;
     /**
-     * <p>The protocol settings that are configured for your server.</p> <ul> <li> <p> To indicate passive mode (for FTP and FTPS protocols), use the <code>PassiveIp</code> parameter. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer. </p> </li> <li> <p>To ignore the error that is generated when the client attempts to use the <code>SETSTAT</code> command on a file that you are uploading to an Amazon S3 bucket, use the <code>SetStatOption</code> parameter. To have the Transfer Family server ignore the <code>SETSTAT</code> command and upload files without needing to make any changes to your SFTP client, set the value to <code>ENABLE_NO_OP</code>. If you set the <code>SetStatOption</code> parameter to <code>ENABLE_NO_OP</code>, Transfer Family generates a log entry to Amazon CloudWatch Logs, so that you can determine when the client is making a <code>SETSTAT</code> call.</p> </li> <li> <p>To determine whether your Transfer Family server resumes recent, negotiated sessions through a unique session ID, use the <code>TlsSessionResumptionMode</code> parameter.</p> </li> <li> <p> <code>As2Transports</code> indicates the transport method for the AS2 messages. Currently, only HTTP is supported.</p> </li> </ul>
+     * <p>The protocol settings that are configured for your server.</p> <note> <p>Avoid placing Network Load Balancers (NLBs) or NAT gateways in front of Transfer Family servers, as this increases costs and can cause performance issues, including reduced connection limits for FTPS. For more details, see <a href="https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations"> Avoid placing NLBs and NATs in front of Transfer Family</a>.</p> </note> <ul> <li> <p> To indicate passive mode (for FTP and FTPS protocols), use the <code>PassiveIp</code> parameter. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer. </p> </li> <li> <p>To ignore the error that is generated when the client attempts to use the <code>SETSTAT</code> command on a file that you are uploading to an Amazon S3 bucket, use the <code>SetStatOption</code> parameter. To have the Transfer Family server ignore the <code>SETSTAT</code> command and upload files without needing to make any changes to your SFTP client, set the value to <code>ENABLE_NO_OP</code>. If you set the <code>SetStatOption</code> parameter to <code>ENABLE_NO_OP</code>, Transfer Family generates a log entry to Amazon CloudWatch Logs, so that you can determine when the client is making a <code>SETSTAT</code> call.</p> </li> <li> <p>To determine whether your Transfer Family server resumes recent, negotiated sessions through a unique session ID, use the <code>TlsSessionResumptionMode</code> parameter.</p> </li> <li> <p> <code>As2Transports</code> indicates the transport method for the AS2 messages. Currently, only HTTP is supported.</p> </li> </ul>
      * @public
      */
     ProtocolDetails?: ProtocolDetails | undefined;
@@ -2928,7 +3121,7 @@ export interface DescribedServer {
      */
     Certificate?: string | undefined;
     /**
-     * <p>The protocol settings that are configured for your server.</p> <ul> <li> <p> To indicate passive mode (for FTP and FTPS protocols), use the <code>PassiveIp</code> parameter. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer. </p> </li> <li> <p>To ignore the error that is generated when the client attempts to use the <code>SETSTAT</code> command on a file that you are uploading to an Amazon S3 bucket, use the <code>SetStatOption</code> parameter. To have the Transfer Family server ignore the <code>SETSTAT</code> command and upload files without needing to make any changes to your SFTP client, set the value to <code>ENABLE_NO_OP</code>. If you set the <code>SetStatOption</code> parameter to <code>ENABLE_NO_OP</code>, Transfer Family generates a log entry to Amazon CloudWatch Logs, so that you can determine when the client is making a <code>SETSTAT</code> call.</p> </li> <li> <p>To determine whether your Transfer Family server resumes recent, negotiated sessions through a unique session ID, use the <code>TlsSessionResumptionMode</code> parameter.</p> </li> <li> <p> <code>As2Transports</code> indicates the transport method for the AS2 messages. Currently, only HTTP is supported.</p> </li> </ul>
+     * <p>The protocol settings that are configured for your server.</p> <note> <p>Avoid placing Network Load Balancers (NLBs) or NAT gateways in front of Transfer Family servers, as this increases costs and can cause performance issues, including reduced connection limits for FTPS. For more details, see <a href="https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations"> Avoid placing NLBs and NATs in front of Transfer Family</a>.</p> </note> <ul> <li> <p> To indicate passive mode (for FTP and FTPS protocols), use the <code>PassiveIp</code> parameter. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer. </p> </li> <li> <p>To ignore the error that is generated when the client attempts to use the <code>SETSTAT</code> command on a file that you are uploading to an Amazon S3 bucket, use the <code>SetStatOption</code> parameter. To have the Transfer Family server ignore the <code>SETSTAT</code> command and upload files without needing to make any changes to your SFTP client, set the value to <code>ENABLE_NO_OP</code>. If you set the <code>SetStatOption</code> parameter to <code>ENABLE_NO_OP</code>, Transfer Family generates a log entry to Amazon CloudWatch Logs, so that you can determine when the client is making a <code>SETSTAT</code> call.</p> </li> <li> <p>To determine whether your Transfer Family server resumes recent, negotiated sessions through a unique session ID, use the <code>TlsSessionResumptionMode</code> parameter.</p> </li> <li> <p> <code>As2Transports</code> indicates the transport method for the AS2 messages. Currently, only HTTP is supported.</p> </li> </ul>
      * @public
      */
     ProtocolDetails?: ProtocolDetails | undefined;
@@ -4242,7 +4435,7 @@ export interface UpdateServerRequest {
      */
     Certificate?: string | undefined;
     /**
-     * <p>The protocol settings that are configured for your server.</p> <ul> <li> <p> To indicate passive mode (for FTP and FTPS protocols), use the <code>PassiveIp</code> parameter. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer. </p> </li> <li> <p>To ignore the error that is generated when the client attempts to use the <code>SETSTAT</code> command on a file that you are uploading to an Amazon S3 bucket, use the <code>SetStatOption</code> parameter. To have the Transfer Family server ignore the <code>SETSTAT</code> command and upload files without needing to make any changes to your SFTP client, set the value to <code>ENABLE_NO_OP</code>. If you set the <code>SetStatOption</code> parameter to <code>ENABLE_NO_OP</code>, Transfer Family generates a log entry to Amazon CloudWatch Logs, so that you can determine when the client is making a <code>SETSTAT</code> call.</p> </li> <li> <p>To determine whether your Transfer Family server resumes recent, negotiated sessions through a unique session ID, use the <code>TlsSessionResumptionMode</code> parameter.</p> </li> <li> <p> <code>As2Transports</code> indicates the transport method for the AS2 messages. Currently, only HTTP is supported.</p> </li> </ul>
+     * <p>The protocol settings that are configured for your server.</p> <note> <p>Avoid placing Network Load Balancers (NLBs) or NAT gateways in front of Transfer Family servers, as this increases costs and can cause performance issues, including reduced connection limits for FTPS. For more details, see <a href="https://docs.aws.amazon.com/transfer/latest/userguide/infrastructure-security.html#nlb-considerations"> Avoid placing NLBs and NATs in front of Transfer Family</a>.</p> </note> <ul> <li> <p> To indicate passive mode (for FTP and FTPS protocols), use the <code>PassiveIp</code> parameter. Enter a single dotted-quad IPv4 address, such as the external IP address of a firewall, router, or load balancer. </p> </li> <li> <p>To ignore the error that is generated when the client attempts to use the <code>SETSTAT</code> command on a file that you are uploading to an Amazon S3 bucket, use the <code>SetStatOption</code> parameter. To have the Transfer Family server ignore the <code>SETSTAT</code> command and upload files without needing to make any changes to your SFTP client, set the value to <code>ENABLE_NO_OP</code>. If you set the <code>SetStatOption</code> parameter to <code>ENABLE_NO_OP</code>, Transfer Family generates a log entry to Amazon CloudWatch Logs, so that you can determine when the client is making a <code>SETSTAT</code> call.</p> </li> <li> <p>To determine whether your Transfer Family server resumes recent, negotiated sessions through a unique session ID, use the <code>TlsSessionResumptionMode</code> parameter.</p> </li> <li> <p> <code>As2Transports</code> indicates the transport method for the AS2 messages. Currently, only HTTP is supported.</p> </li> </ul>
      * @public
      */
     ProtocolDetails?: ProtocolDetails | undefined;

package/dist-types/ts3.4/models/models_0.d.ts

@@ -322,6 +322,34 @@ export declare class ConflictException extends __BaseException {
   Message: string | undefined;
   constructor(opts: __ExceptionOptionType<ConflictException, __BaseException>);
 }
+export interface ConnectorVpcLatticeEgressConfig {
+  ResourceConfigurationArn: string | undefined;
+  PortNumber?: number | undefined;
+}
+export type ConnectorEgressConfig =
+  | ConnectorEgressConfig.VpcLatticeMember
+  | ConnectorEgressConfig.$UnknownMember;
+export declare namespace ConnectorEgressConfig {
+  interface VpcLatticeMember {
+    VpcLattice: ConnectorVpcLatticeEgressConfig;
+    $unknown?: never;
+  }
+  interface $UnknownMember {
+    VpcLattice?: never;
+    $unknown: [string, any];
+  }
+  interface Visitor<T> {
+    VpcLattice: (value: ConnectorVpcLatticeEgressConfig) => T;
+    _: (name: string, value: any) => T;
+  }
+  const visit: <T>(value: ConnectorEgressConfig, visitor: Visitor<T>) => T;
+}
+export declare const ConnectorEgressType: {
+  readonly SERVICE_MANAGED: "SERVICE_MANAGED";
+  readonly VPC_LATTICE: "VPC_LATTICE";
+};
+export type ConnectorEgressType =
+  (typeof ConnectorEgressType)[keyof typeof ConnectorEgressType];
 export declare const TransferTableStatus: {
   readonly COMPLETED: "COMPLETED";
   readonly FAILED: "FAILED";
@@ -342,13 +370,14 @@ export interface SftpConnectorConfig {
   MaxConcurrentConnections?: number | undefined;
 }
 export interface CreateConnectorRequest {
-  Url: string | undefined;
+  Url?: string | undefined;
   As2Config?: As2ConnectorConfig | undefined;
   AccessRole: string | undefined;
   LoggingRole?: string | undefined;
   Tags?: Tag[] | undefined;
   SftpConfig?: SftpConnectorConfig | undefined;
   SecurityPolicyName?: string | undefined;
+  EgressConfig?: ConnectorEgressConfig | undefined;
 }
 export interface CreateConnectorResponse {
   ConnectorId: string | undefined;
@@ -359,6 +388,38 @@ export interface DeleteConnectorRequest {
 export interface DescribeConnectorRequest {
   ConnectorId: string | undefined;
 }
+export interface DescribedConnectorVpcLatticeEgressConfig {
+  ResourceConfigurationArn: string | undefined;
+  PortNumber?: number | undefined;
+}
+export type DescribedConnectorEgressConfig =
+  | DescribedConnectorEgressConfig.VpcLatticeMember
+  | DescribedConnectorEgressConfig.$UnknownMember;
+export declare namespace DescribedConnectorEgressConfig {
+  interface VpcLatticeMember {
+    VpcLattice: DescribedConnectorVpcLatticeEgressConfig;
+    $unknown?: never;
+  }
+  interface $UnknownMember {
+    VpcLattice?: never;
+    $unknown: [string, any];
+  }
+  interface Visitor<T> {
+    VpcLattice: (value: DescribedConnectorVpcLatticeEgressConfig) => T;
+    _: (name: string, value: any) => T;
+  }
+  const visit: <T>(
+    value: DescribedConnectorEgressConfig,
+    visitor: Visitor<T>
+  ) => T;
+}
+export declare const ConnectorStatus: {
+  readonly ACTIVE: "ACTIVE";
+  readonly ERRORED: "ERRORED";
+  readonly PENDING: "PENDING";
+};
+export type ConnectorStatus =
+  (typeof ConnectorStatus)[keyof typeof ConnectorStatus];
 export interface DescribedConnector {
   Arn: string | undefined;
   ConnectorId?: string | undefined;
@@ -370,6 +431,10 @@ export interface DescribedConnector {
   SftpConfig?: SftpConnectorConfig | undefined;
   ServiceManagedEgressIpAddresses?: string[] | undefined;
   SecurityPolicyName?: string | undefined;
+  EgressConfig?: DescribedConnectorEgressConfig | undefined;
+  EgressType: ConnectorEgressType | undefined;
+  ErrorMessage?: string | undefined;
+  Status: ConnectorStatus | undefined;
 }
 export interface DescribeConnectorResponse {
   Connector: DescribedConnector | undefined;
@@ -387,6 +452,31 @@ export interface ListConnectorsResponse {
   NextToken?: string | undefined;
   Connectors: ListedConnector[] | undefined;
 }
+export interface UpdateConnectorVpcLatticeEgressConfig {
+  ResourceConfigurationArn?: string | undefined;
+  PortNumber?: number | undefined;
+}
+export type UpdateConnectorEgressConfig =
+  | UpdateConnectorEgressConfig.VpcLatticeMember
+  | UpdateConnectorEgressConfig.$UnknownMember;
+export declare namespace UpdateConnectorEgressConfig {
+  interface VpcLatticeMember {
+    VpcLattice: UpdateConnectorVpcLatticeEgressConfig;
+    $unknown?: never;
+  }
+  interface $UnknownMember {
+    VpcLattice?: never;
+    $unknown: [string, any];
+  }
+  interface Visitor<T> {
+    VpcLattice: (value: UpdateConnectorVpcLatticeEgressConfig) => T;
+    _: (name: string, value: any) => T;
+  }
+  const visit: <T>(
+    value: UpdateConnectorEgressConfig,
+    visitor: Visitor<T>
+  ) => T;
+}
 export interface UpdateConnectorRequest {
   ConnectorId: string | undefined;
   Url?: string | undefined;
@@ -395,6 +485,7 @@ export interface UpdateConnectorRequest {
   LoggingRole?: string | undefined;
   SftpConfig?: SftpConnectorConfig | undefined;
   SecurityPolicyName?: string | undefined;
+  EgressConfig?: UpdateConnectorEgressConfig | undefined;
 }
 export interface UpdateConnectorResponse {
   ConnectorId: string | undefined;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@aws-sdk/client-transfer",
   "description": "AWS SDK for JavaScript Transfer Client for Node.js, Browser and React Native",
-  "version": "3.907.0",
+  "version": "3.910.0",
   "scripts": {
     "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
     "build:cjs": "node ../../scripts/compilation/inline client-transfer",
@@ -20,43 +20,43 @@
   "dependencies": {
     "@aws-crypto/sha256-browser": "5.2.0",
     "@aws-crypto/sha256-js": "5.2.0",
-    "@aws-sdk/core": "3.907.0",
-    "@aws-sdk/credential-provider-node": "3.907.0",
-    "@aws-sdk/middleware-host-header": "3.901.0",
-    "@aws-sdk/middleware-logger": "3.901.0",
-    "@aws-sdk/middleware-recursion-detection": "3.901.0",
-    "@aws-sdk/middleware-user-agent": "3.907.0",
-    "@aws-sdk/region-config-resolver": "3.901.0",
-    "@aws-sdk/types": "3.901.0",
-    "@aws-sdk/util-endpoints": "3.901.0",
-    "@aws-sdk/util-user-agent-browser": "3.907.0",
-    "@aws-sdk/util-user-agent-node": "3.907.0",
-    "@smithy/config-resolver": "^4.3.0",
-    "@smithy/core": "^3.14.0",
-    "@smithy/fetch-http-handler": "^5.3.0",
-    "@smithy/hash-node": "^4.2.0",
-    "@smithy/invalid-dependency": "^4.2.0",
-    "@smithy/middleware-content-length": "^4.2.0",
-    "@smithy/middleware-endpoint": "^4.3.0",
-    "@smithy/middleware-retry": "^4.4.0",
-    "@smithy/middleware-serde": "^4.2.0",
-    "@smithy/middleware-stack": "^4.2.0",
-    "@smithy/node-config-provider": "^4.3.0",
-    "@smithy/node-http-handler": "^4.3.0",
-    "@smithy/protocol-http": "^5.3.0",
-    "@smithy/smithy-client": "^4.7.0",
-    "@smithy/types": "^4.6.0",
-    "@smithy/url-parser": "^4.2.0",
-    "@smithy/util-base64": "^4.2.0",
+    "@aws-sdk/core": "3.910.0",
+    "@aws-sdk/credential-provider-node": "3.910.0",
+    "@aws-sdk/middleware-host-header": "3.910.0",
+    "@aws-sdk/middleware-logger": "3.910.0",
+    "@aws-sdk/middleware-recursion-detection": "3.910.0",
+    "@aws-sdk/middleware-user-agent": "3.910.0",
+    "@aws-sdk/region-config-resolver": "3.910.0",
+    "@aws-sdk/types": "3.910.0",
+    "@aws-sdk/util-endpoints": "3.910.0",
+    "@aws-sdk/util-user-agent-browser": "3.910.0",
+    "@aws-sdk/util-user-agent-node": "3.910.0",
+    "@smithy/config-resolver": "^4.3.2",
+    "@smithy/core": "^3.16.1",
+    "@smithy/fetch-http-handler": "^5.3.3",
+    "@smithy/hash-node": "^4.2.2",
+    "@smithy/invalid-dependency": "^4.2.2",
+    "@smithy/middleware-content-length": "^4.2.2",
+    "@smithy/middleware-endpoint": "^4.3.3",
+    "@smithy/middleware-retry": "^4.4.3",
+    "@smithy/middleware-serde": "^4.2.2",
+    "@smithy/middleware-stack": "^4.2.2",
+    "@smithy/node-config-provider": "^4.3.2",
+    "@smithy/node-http-handler": "^4.4.1",
+    "@smithy/protocol-http": "^5.3.2",
+    "@smithy/smithy-client": "^4.8.1",
+    "@smithy/types": "^4.7.1",
+    "@smithy/url-parser": "^4.2.2",
+    "@smithy/util-base64": "^4.3.0",
     "@smithy/util-body-length-browser": "^4.2.0",
-    "@smithy/util-body-length-node": "^4.2.0",
-    "@smithy/util-defaults-mode-browser": "^4.2.0",
-    "@smithy/util-defaults-mode-node": "^4.2.0",
-    "@smithy/util-endpoints": "^3.2.0",
-    "@smithy/util-middleware": "^4.2.0",
-    "@smithy/util-retry": "^4.2.0",
+    "@smithy/util-body-length-node": "^4.2.1",
+    "@smithy/util-defaults-mode-browser": "^4.3.2",
+    "@smithy/util-defaults-mode-node": "^4.2.3",
+    "@smithy/util-endpoints": "^3.2.2",
+    "@smithy/util-middleware": "^4.2.2",
+    "@smithy/util-retry": "^4.2.2",
     "@smithy/util-utf8": "^4.2.0",
-    "@smithy/util-waiter": "^4.2.0",
+    "@smithy/util-waiter": "^4.2.2",
     "tslib": "^2.6.2"
   },
   "devDependencies": {