cdk-lambda-subminute 2.0.284 → 2.0.286

package/node_modules/aws-sdk/clients/m2.d.ts

@@ -431,6 +431,10 @@ declare namespace M2 {
      * Specifies a file associated with a specific batch job.
      */
     fileBatchJobIdentifier?: FileBatchJobIdentifier;
+    /**
+     * Specifies an Amazon S3 location that identifies the batch jobs that you want to run. Use this identifier to run ad hoc batch jobs.
+     */
+    s3BatchJobIdentifier?: S3BatchJobIdentifier;
     /**
      * A batch job identifier in which the batch job to run is identified by the script name.
      */
@@ -580,7 +584,7 @@ declare namespace M2 {
      */
     name: EntityName;
     /**
-     * Configures the maintenance window you want for the runtime environment. If you do not provide a value, a random system-generated value will be assigned.
+     * Configures the maintenance window that you want for the runtime environment. The maintenance window must have the format ddd:hh24:mi-ddd:hh24:mi and must be less than 24 hours. The following two examples are valid maintenance windows: sun:23:45-mon:00:15 or sat:01:00-sat:03:00.  If you do not provide a value, a random system-generated value will be assigned.
      */
     preferredMaintenanceWindow?: String50;
     /**
@@ -680,6 +684,10 @@ declare namespace M2 {
      * The status of the data set import task.
      */
     status: DataSetTaskLifecycle;
+    /**
+     * If dataset import failed, the failure reason will show here.
+     */
+    statusReason?: String;
     /**
      * A summary of the data set import task.
      */
@@ -716,7 +724,7 @@ declare namespace M2 {
      */
     lastUpdatedTime?: Timestamp;
   }
-  export type DataSetTaskLifecycle = "Creating"|"Running"|"Completed"|string;
+  export type DataSetTaskLifecycle = "Creating"|"Running"|"Completed"|"Failed"|string;
   export type DataSetsSummaryList = DataSetSummary[];
   export interface DatasetDetailOrgAttributes {
     /**
@@ -806,7 +814,7 @@ declare namespace M2 {
      */
     statusReason?: String;
   }
-  export type DeploymentLifecycle = "Deploying"|"Succeeded"|"Failed"|string;
+  export type DeploymentLifecycle = "Deploying"|"Succeeded"|"Failed"|"Updating Deployment"|string;
   export type DeploymentList = DeploymentSummary[];
   export interface DeploymentSummary {
     /**
@@ -1171,6 +1179,10 @@ declare namespace M2 {
      * The type of data set. The only supported value is VSAM.
      */
     dataSetOrg?: DatasetDetailOrgAttributes;
+    /**
+     * File size of the dataset.
+     */
+    fileSize?: Long;
     /**
      * The last time the data set was referenced.
      */
@@ -1260,7 +1272,7 @@ declare namespace M2 {
   }
   export interface GetEnvironmentResponse {
     /**
-     * The number of instances included in the runtime environment. A standalone runtime environment has a maxiumum of one instance. Currently, a high availability runtime environment has a maximum of two instances. 
+     * The number of instances included in the runtime environment. A standalone runtime environment has a maximum of one instance. Currently, a high availability runtime environment has a maximum of two instances. 
      */
     actualCapacity?: CapacityValue;
     /**
@@ -1312,7 +1324,7 @@ declare namespace M2 {
      */
     pendingMaintenance?: PendingMaintenance;
     /**
-     * Configures the maintenance window you want for the runtime environment. If you do not provide a value, a random system-generated value will be assigned.
+     * The maintenance window for the runtime environment. If you don't provide a value for the maintenance window, the service assigns a random value.
      */
     preferredMaintenanceWindow?: String50;
     /**
@@ -1363,6 +1375,16 @@ declare namespace M2 {
   export type Identifier = string;
   export type IdentifierList = Identifier[];
   export type Integer = number;
+  export interface JobIdentifier {
+    /**
+     * The name of the file that contains the batch job definition.
+     */
+    fileName?: String;
+    /**
+     * The name of the script that contains the batch job definition.
+     */
+    scriptName?: String;
+  }
   export interface ListApplicationVersionsRequest {
     /**
      * The unique identifier of the application.
@@ -1520,6 +1542,10 @@ declare namespace M2 {
      * The maximum number of objects to return.
      */
     maxResults?: MaxResults;
+    /**
+     * Filter dataset name matching the specified pattern. Can use * and % as wild cards.
+     */
+    nameFilter?: String200;
     /**
      * A pagination token returned from a previous call to this operation. This specifies the next item to return. To return to the beginning of the list, exclude this parameter.
      */
@@ -1639,6 +1665,7 @@ declare namespace M2 {
      */
     logType: String20;
   }
+  export type Long = number;
   export interface MaintenanceSchedule {
     /**
      * The time the scheduled maintenance is to end.
@@ -1730,6 +1757,20 @@ declare namespace M2 {
      */
     min: Integer;
   }
+  export interface S3BatchJobIdentifier {
+    /**
+     * The Amazon S3 bucket that contains the batch job definitions.
+     */
+    bucket: String;
+    /**
+     * Identifies the batch job definition. This identifier can also point to any batch job definition that already exists in the application or to one of the batch job definitions within the directory that is specified in keyPrefix.
+     */
+    identifier: JobIdentifier;
+    /**
+     * The key prefix that specifies the path to the folder in the S3 bucket that has the batch job definitions.
+     */
+    keyPrefix?: String;
+  }
   export interface ScriptBatchJobDefinition {
     /**
      * The name of the script containing the batch job definition.
@@ -1872,12 +1913,16 @@ declare namespace M2 {
      * The unique identifier of the runtime environment that you want to update.
      */
     environmentId: Identifier;
+    /**
+     * Forces the updates on the environment. This option is needed if the applications in the environment are not stopped or if there are ongoing application-related activities in the environment. If you use this option, be aware that it could lead to data corruption in the applications, and that you might need to perform repair and recovery procedures for the applications. This option is not needed if the attribute being updated is preferredMaintenanceWindow.
+     */
+    forceUpdate?: Boolean;
     /**
      * The instance type for the runtime environment to update.
      */
     instanceType?: String20;
     /**
-     * Configures the maintenance window you want for the runtime environment. If you do not provide a value, a random system-generated value will be assigned.
+     * Configures the maintenance window that you want for the runtime environment. The maintenance window must have the format ddd:hh24:mi-ddd:hh24:mi and must be less than 24 hours. The following two examples are valid maintenance windows: sun:23:45-mon:00:15 or sat:01:00-sat:03:00.  If you do not provide a value, a random system-generated value will be assigned.
      */
     preferredMaintenanceWindow?: String;
   }

package/node_modules/aws-sdk/clients/neptunedata.d.ts

@@ -116,19 +116,19 @@ declare class Neptunedata extends Service {
    */
   executeGremlinQuery(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteGremlinQueryOutput) => void): Request<Neptunedata.Types.ExecuteGremlinQueryOutput, AWSError>;
   /**
-   * Executes an openCypher explain request. See The openCypher explain feature for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ReadDataViaQuery IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
+   * Executes an openCypher explain request. See The openCypher explain feature for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ReadDataViaQuery IAM action in that cluster. Note that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
    */
   executeOpenCypherExplainQuery(params: Neptunedata.Types.ExecuteOpenCypherExplainQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.ExecuteOpenCypherExplainQueryOutput) => void): Request<Neptunedata.Types.ExecuteOpenCypherExplainQueryOutput, AWSError>;
   /**
-   * Executes an openCypher explain request. See The openCypher explain feature for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ReadDataViaQuery IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
+   * Executes an openCypher explain request. See The openCypher explain feature for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:ReadDataViaQuery IAM action in that cluster. Note that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
    */
   executeOpenCypherExplainQuery(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteOpenCypherExplainQueryOutput) => void): Request<Neptunedata.Types.ExecuteOpenCypherExplainQueryOutput, AWSError>;
   /**
-   * Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information. Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs. The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license. Note that when invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query:    neptune-db:ReadDataViaQuery     neptune-db:WriteDataViaQuery     neptune-db:DeleteDataViaQuery    Note also that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
+   * Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information. Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs. The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license. Note that when invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query:    neptune-db:ReadDataViaQuery     neptune-db:WriteDataViaQuery     neptune-db:DeleteDataViaQuery    Note also that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
    */
   executeOpenCypherQuery(params: Neptunedata.Types.ExecuteOpenCypherQueryInput, callback?: (err: AWSError, data: Neptunedata.Types.ExecuteOpenCypherQueryOutput) => void): Request<Neptunedata.Types.ExecuteOpenCypherQueryOutput, AWSError>;
   /**
-   * Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information. Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs. The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license. Note that when invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query:    neptune-db:ReadDataViaQuery     neptune-db:WriteDataViaQuery     neptune-db:DeleteDataViaQuery    Note also that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
+   * Executes an openCypher query. See Accessing the Neptune Graph with openCypher for more information. Neptune supports building graph applications using openCypher, which is currently one of the most popular query languages among developers working with graph databases. Developers, business analysts, and data scientists like openCypher's declarative, SQL-inspired syntax because it provides a familiar structure in which to querying property graphs. The openCypher language was originally developed by Neo4j, then open-sourced in 2015 and contributed to the openCypher project under an Apache 2 open-source license. Note that when invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows one of the following IAM actions in that cluster, depending on the query:    neptune-db:ReadDataViaQuery     neptune-db:WriteDataViaQuery     neptune-db:DeleteDataViaQuery    Note also that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
    */
   executeOpenCypherQuery(callback?: (err: AWSError, data: Neptunedata.Types.ExecuteOpenCypherQueryOutput) => void): Request<Neptunedata.Types.ExecuteOpenCypherQueryOutput, AWSError>;
   /**
@@ -184,11 +184,11 @@ declare class Neptunedata extends Service {
    */
   getMLModelTransformJob(callback?: (err: AWSError, data: Neptunedata.Types.GetMLModelTransformJobOutput) => void): Request<Neptunedata.Types.GetMLModelTransformJobOutput, AWSError>;
   /**
-   * Retrieves the status of a specified openCypher query. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
+   * Retrieves the status of a specified openCypher query. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
    */
   getOpenCypherQueryStatus(params: Neptunedata.Types.GetOpenCypherQueryStatusInput, callback?: (err: AWSError, data: Neptunedata.Types.GetOpenCypherQueryStatusOutput) => void): Request<Neptunedata.Types.GetOpenCypherQueryStatusOutput, AWSError>;
   /**
-   * Retrieves the status of a specified openCypher query. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
+   * Retrieves the status of a specified openCypher query. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
    */
   getOpenCypherQueryStatus(callback?: (err: AWSError, data: Neptunedata.Types.GetOpenCypherQueryStatusOutput) => void): Request<Neptunedata.Types.GetOpenCypherQueryStatusOutput, AWSError>;
   /**
@@ -196,11 +196,11 @@ declare class Neptunedata extends Service {
    */
   getPropertygraphStatistics(callback?: (err: AWSError, data: Neptunedata.Types.GetPropertygraphStatisticsOutput) => void): Request<Neptunedata.Types.GetPropertygraphStatisticsOutput, AWSError>;
   /**
-   * Gets a stream for a property graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetPropertygraphStream lets you collect these change-log entries for a property graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStreamRecords IAM action in that cluster. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that enables one of the following IAM actions, depending on the query: Note that you can restrict property-graph queries using the following IAM context keys:    neptune-db:QueryLanguage:Gremlin     neptune-db:QueryLanguage:Opencypher    See Condition keys available in Neptune IAM data-access policy statements).
+   * Gets a stream for a property graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetPropertygraphStream lets you collect these change-log entries for a property graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStreamRecords IAM action in that cluster. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that enables one of the following IAM actions, depending on the query: Note that you can restrict property-graph queries using the following IAM context keys:    neptune-db:QueryLanguage:Gremlin     neptune-db:QueryLanguage:OpenCypher    See Condition keys available in Neptune IAM data-access policy statements).
    */
   getPropertygraphStream(params: Neptunedata.Types.GetPropertygraphStreamInput, callback?: (err: AWSError, data: Neptunedata.Types.GetPropertygraphStreamOutput) => void): Request<Neptunedata.Types.GetPropertygraphStreamOutput, AWSError>;
   /**
-   * Gets a stream for a property graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetPropertygraphStream lets you collect these change-log entries for a property graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStreamRecords IAM action in that cluster. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that enables one of the following IAM actions, depending on the query: Note that you can restrict property-graph queries using the following IAM context keys:    neptune-db:QueryLanguage:Gremlin     neptune-db:QueryLanguage:Opencypher    See Condition keys available in Neptune IAM data-access policy statements).
+   * Gets a stream for a property graph. With the Neptune Streams feature, you can generate a complete sequence of change-log entries that record every change made to your graph data as it happens. GetPropertygraphStream lets you collect these change-log entries for a property graph. The Neptune streams feature needs to be enabled on your Neptune DBcluster. To enable streams, set the neptune_streams DB cluster parameter to 1. See Capturing graph changes in real time using Neptune streams. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetStreamRecords IAM action in that cluster. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that enables one of the following IAM actions, depending on the query: Note that you can restrict property-graph queries using the following IAM context keys:    neptune-db:QueryLanguage:Gremlin     neptune-db:QueryLanguage:OpenCypher    See Condition keys available in Neptune IAM data-access policy statements).
    */
   getPropertygraphStream(callback?: (err: AWSError, data: Neptunedata.Types.GetPropertygraphStreamOutput) => void): Request<Neptunedata.Types.GetPropertygraphStreamOutput, AWSError>;
   /**
@@ -280,11 +280,11 @@ declare class Neptunedata extends Service {
    */
   listMLModelTransformJobs(callback?: (err: AWSError, data: Neptunedata.Types.ListMLModelTransformJobsOutput) => void): Request<Neptunedata.Types.ListMLModelTransformJobsOutput, AWSError>;
   /**
-   * Lists active openCypher queries. See Neptune openCypher status endpoint for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
+   * Lists active openCypher queries. See Neptune openCypher status endpoint for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
    */
   listOpenCypherQueries(params: Neptunedata.Types.ListOpenCypherQueriesInput, callback?: (err: AWSError, data: Neptunedata.Types.ListOpenCypherQueriesOutput) => void): Request<Neptunedata.Types.ListOpenCypherQueriesOutput, AWSError>;
   /**
-   * Lists active openCypher queries. See Neptune openCypher status endpoint for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:Opencypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
+   * Lists active openCypher queries. See Neptune openCypher status endpoint for more information. When invoking this operation in a Neptune cluster that has IAM authentication enabled, the IAM user or role making the request must have a policy attached that allows the neptune-db:GetQueryStatus IAM action in that cluster. Note that the neptune-db:QueryLanguage:OpenCypher IAM condition key can be used in the policy document to restrict the use of openCypher queries (see Condition keys available in Neptune IAM data-access policy statements).
    */
   listOpenCypherQueries(callback?: (err: AWSError, data: Neptunedata.Types.ListOpenCypherQueriesOutput) => void): Request<Neptunedata.Types.ListOpenCypherQueriesOutput, AWSError>;
   /**
@@ -1643,7 +1643,7 @@ declare namespace Neptunedata {
      */
     updateSingleCardinalityProperties?: Boolean;
     /**
-     * This is an optional flag parameter that indicates whether the load request can be queued up or not.  You don't have to wait for one load job to complete before issuing the next one, because Neptune can queue up as many as 64 jobs at a time, provided that their queueRequest parameters are all set to "TRUE". If the queueRequest parameter is omitted or set to "FALSE", the load request will fail if another load job is already running.  Allowed values: "TRUE", "FALSE".  Default value: "FALSE".
+     * This is an optional flag parameter that indicates whether the load request can be queued up or not.  You don't have to wait for one load job to complete before issuing the next one, because Neptune can queue up as many as 64 jobs at a time, provided that their queueRequest parameters are all set to "TRUE". The queue order of the jobs will be first-in-first-out (FIFO). If the queueRequest parameter is omitted or set to "FALSE", the load request will fail if another load job is already running.  Allowed values: "TRUE", "FALSE".  Default value: "FALSE".
      */
     queueRequest?: Boolean;
     /**

package/node_modules/aws-sdk/clients/rds.d.ts

@@ -1601,6 +1601,10 @@ declare namespace RDS {
      * The allocated storage size in gibibytes (GiB) for all database engines except Amazon Aurora. For Aurora, AllocatedStorage always returns 1, because Aurora DB cluster storage size isn't fixed, but instead automatically adjusts as needed.
      */
     AllocatedStorage?: IntegerOptional;
+    /**
+     * Reserved for future use.
+     */
+    RdsCustomClusterConfiguration?: RdsCustomClusterConfiguration;
     /**
      * The Provisioned IOPS (I/O operations per second) value. This setting is only for non-Aurora Multi-AZ DB clusters.
      */
@@ -1991,6 +1995,10 @@ declare namespace RDS {
      * For DB clusters in serverless DB engine mode, the scaling properties of the DB cluster. Valid for Cluster Type: Aurora DB clusters only
      */
     ScalingConfiguration?: ScalingConfiguration;
+    /**
+     * Reserved for future use.
+     */
+    RdsCustomClusterConfiguration?: RdsCustomClusterConfiguration;
     /**
      * Specifies whether the DB cluster has deletion protection enabled. The database can't be deleted when deletion protection is enabled. By default, deletion protection isn't enabled. Valid for Cluster Type: Aurora DB clusters and Multi-AZ DB clusters
      */
@@ -3010,6 +3018,10 @@ declare namespace RDS {
      */
     EngineMode?: String;
     ScalingConfigurationInfo?: ScalingConfigurationInfo;
+    /**
+     * Reserved for future use.
+     */
+    RdsCustomClusterConfiguration?: RdsCustomClusterConfiguration;
     /**
      * Indicates whether the DB cluster has deletion protection enabled. The database can't be deleted when deletion protection is enabled.
      */
@@ -8012,6 +8024,16 @@ declare namespace RDS {
     Step?: IntegerOptional;
   }
   export type RangeList = Range[];
+  export interface RdsCustomClusterConfiguration {
+    /**
+     * Reserved for future use.
+     */
+    InterconnectSubnetId?: String;
+    /**
+     * Reserved for future use.
+     */
+    TransitGatewayMulticastDomainId?: String;
+  }
   export type ReadReplicaDBClusterIdentifierList = String[];
   export type ReadReplicaDBInstanceIdentifierList = String[];
   export type ReadReplicaIdentifierList = String[];
@@ -8559,6 +8581,10 @@ declare namespace RDS {
      * The network type of the DB cluster. Valid Values:    IPV4     DUAL    The network type is determined by the DBSubnetGroup specified for the DB cluster. A DBSubnetGroup can support only the IPv4 protocol or the IPv4 and the IPv6 protocols (DUAL). For more information, see  Working with a DB instance in a VPC in the Amazon Aurora User Guide.  Valid for: Aurora DB clusters only
      */
     NetworkType?: String;
+    /**
+     * Reserved for future use.
+     */
+    RdsCustomClusterConfiguration?: RdsCustomClusterConfiguration;
   }
   export interface RestoreDBClusterFromSnapshotResult {
     DBCluster?: DBCluster;
@@ -8670,6 +8696,10 @@ declare namespace RDS {
      * The resource ID of the source DB cluster from which to restore.
      */
     SourceDbClusterResourceId?: String;
+    /**
+     * Reserved for future use.
+     */
+    RdsCustomClusterConfiguration?: RdsCustomClusterConfiguration;
   }
   export interface RestoreDBClusterToPointInTimeResult {
     DBCluster?: DBCluster;

package/node_modules/aws-sdk/clients/redshift.d.ts

@@ -728,6 +728,14 @@ declare class Redshift extends Service {
    * Enables the automatic copy of snapshots from one region to another region for a specified cluster.
    */
   enableSnapshotCopy(callback?: (err: AWSError, data: Redshift.Types.EnableSnapshotCopyResult) => void): Request<Redshift.Types.EnableSnapshotCopyResult, AWSError>;
+  /**
+   * Fails over the primary compute unit of the specified Multi-AZ cluster to another Availability Zone.
+   */
+  failoverPrimaryCompute(params: Redshift.Types.FailoverPrimaryComputeInputMessage, callback?: (err: AWSError, data: Redshift.Types.FailoverPrimaryComputeResult) => void): Request<Redshift.Types.FailoverPrimaryComputeResult, AWSError>;
+  /**
+   * Fails over the primary compute unit of the specified Multi-AZ cluster to another Availability Zone.
+   */
+  failoverPrimaryCompute(callback?: (err: AWSError, data: Redshift.Types.FailoverPrimaryComputeResult) => void): Request<Redshift.Types.FailoverPrimaryComputeResult, AWSError>;
   /**
    * Returns a database user name and temporary password with temporary authorization to log on to an Amazon Redshift database. The action returns the database user name prefixed with IAM: if AutoCreate is False or IAMA: if AutoCreate is True. You can optionally specify one or more database user groups that the user will join at log on. By default, the temporary credentials expire in 900 seconds. You can optionally specify a duration between 900 seconds (15 minutes) and 3600 seconds (60 minutes). For more information, see Using IAM Authentication to Generate Database User Credentials in the Amazon Redshift Cluster Management Guide. The Identity and Access Management (IAM) user or role that runs GetClusterCredentials must have an IAM policy attached that allows access to all necessary actions and resources. For more information about permissions, see Resource Policies for GetClusterCredentials in the Amazon Redshift Cluster Management Guide. If the DbGroups parameter is specified, the IAM policy must allow the redshift:JoinGroup action with access to the listed dbgroups.  In addition, if the AutoCreate parameter is set to True, then the policy must include the redshift:CreateClusterUser permission. If the DbName parameter is specified, the IAM policy must allow access to the resource dbname for the specified database name. 
    */
@@ -1541,6 +1549,14 @@ declare namespace Redshift {
      * The IP address type for the cluster. Possible values are ipv4 and dualstack.
      */
     IpAddressType?: String;
+    /**
+     * A boolean value that, if true, indicates that the cluster is deployed in two Availability Zones.
+     */
+    MultiAZ?: String;
+    /**
+     * The secondary compute unit of a cluster, if Multi-AZ deployment is turned on.
+     */
+    MultiAZSecondary?: SecondaryClusterInfo;
   }
   export interface ClusterAssociatedToSchedule {
     /**
@@ -2047,6 +2063,10 @@ declare namespace Redshift {
      * The IP address types that the cluster supports. Possible values are ipv4 and dualstack.
      */
     IpAddressType?: String;
+    /**
+     * If true, Amazon Redshift will deploy the cluster in two Availability Zones (AZ).
+     */
+    MultiAZ?: BooleanOptional;
   }
   export interface CreateClusterParameterGroupMessage {
     /**
@@ -3834,6 +3854,15 @@ declare namespace Redshift {
      */
     Events?: EventList;
   }
+  export interface FailoverPrimaryComputeInputMessage {
+    /**
+     * The unique identifier of the cluster for which the primary compute unit will be failed over to another Availability Zone.
+     */
+    ClusterIdentifier: String;
+  }
+  export interface FailoverPrimaryComputeResult {
+    Cluster?: Cluster;
+  }
   export interface GetClusterCredentialsMessage {
     /**
      * The name of a database user. If a user name matching DbUser exists in the database, the temporary user credentials have the same permissions as the existing user. If DbUser doesn't exist in the database and Autocreate is True, a new user is created using the value for DbUser with PUBLIC permissions. If a database user matching the value for DbUser doesn't exist and Autocreate is False, then the command succeeds but the connection attempt will fail because the user doesn't exist in the database. For more information, see CREATE USER in the Amazon Redshift Database Developer Guide.  Constraints:   Must be 1 to 64 alphanumeric characters or hyphens. The user name can't be PUBLIC.   Must contain uppercase or lowercase letters, numbers, underscore, plus sign, period (dot), at symbol (@), or hyphen.   First character must be a letter.   Must not contain a colon ( : ) or slash ( / ).    Cannot be a reserved word. A list of reserved words can be found in Reserved Words in the Amazon Redshift Database Developer Guide.  
@@ -4356,6 +4385,10 @@ declare namespace Redshift {
      * The IP address types that the cluster supports. Possible values are ipv4 and dualstack.
      */
     IpAddressType?: String;
+    /**
+     * If true and the cluster is currently only deployed in a single Availability Zone, the cluster will be modified to be deployed in two Availability Zones.
+     */
+    MultiAZ?: BooleanOptional;
   }
   export interface ModifyClusterParameterGroupMessage {
     /**
@@ -5323,6 +5356,10 @@ declare namespace Redshift {
      * The IP address type for the cluster. Possible values are ipv4 and dualstack.
      */
     IpAddressType?: String;
+    /**
+     * If true, the snapshot will be restored to a cluster deployed in two Availability Zones.
+     */
+    MultiAZ?: BooleanOptional;
   }
   export interface RestoreFromClusterSnapshotResult {
     Cluster?: Cluster;
@@ -5568,6 +5605,16 @@ declare namespace Redshift {
     ScheduledActions?: ScheduledActionList;
   }
   export type ScheduledSnapshotTimeList = TStamp[];
+  export interface SecondaryClusterInfo {
+    /**
+     * The name of the Availability Zone in which the secondary compute unit of the cluster is located.
+     */
+    AvailabilityZone?: String;
+    /**
+     * The nodes in the secondary compute unit.
+     */
+    ClusterNodes?: ClusterNodesList;
+  }
   export type SensitiveString = string;
   export interface Snapshot {
     /**

package/node_modules/aws-sdk/clients/sagemaker.d.ts

@@ -16867,6 +16867,7 @@ declare namespace SageMaker {
      */
     MonitoringAlertSummaries?: MonitoringAlertSummaryList;
     LastMonitoringExecutionSummary?: MonitoringExecutionSummary;
+    BatchTransformInput?: BatchTransformInput;
   }
   export type ModelDashboardMonitoringSchedules = ModelDashboardMonitoringSchedule[];
   export interface ModelDataQuality {

package/node_modules/aws-sdk/clients/translate.d.ts

@@ -132,11 +132,11 @@ declare class Translate extends Service {
    */
   tagResource(callback?: (err: AWSError, data: Translate.Types.TagResourceResponse) => void): Request<Translate.Types.TagResourceResponse, AWSError>;
   /**
-   * Translates the input document from the source language to the target language. This synchronous operation supports plain text or HTML for the input document. TranslateDocument supports translations from English to any supported language, and from any supported language to English. Therefore, specify either the source language code or the target language code as “en” (English).   TranslateDocument does not support language auto-detection.   If you set the Formality parameter, the request will fail if the target language does not support formality. For a list of target languages that support formality, see Setting formality. 
+   * Translates the input document from the source language to the target language. This synchronous operation supports text, HTML, or Word documents as the input document. TranslateDocument supports translations from English to any supported language, and from any supported language to English. Therefore, specify either the source language code or the target language code as “en” (English).   If you set the Formality parameter, the request will fail if the target language does not support formality. For a list of target languages that support formality, see Setting formality. 
    */
   translateDocument(params: Translate.Types.TranslateDocumentRequest, callback?: (err: AWSError, data: Translate.Types.TranslateDocumentResponse) => void): Request<Translate.Types.TranslateDocumentResponse, AWSError>;
   /**
-   * Translates the input document from the source language to the target language. This synchronous operation supports plain text or HTML for the input document. TranslateDocument supports translations from English to any supported language, and from any supported language to English. Therefore, specify either the source language code or the target language code as “en” (English).   TranslateDocument does not support language auto-detection.   If you set the Formality parameter, the request will fail if the target language does not support formality. For a list of target languages that support formality, see Setting formality. 
+   * Translates the input document from the source language to the target language. This synchronous operation supports text, HTML, or Word documents as the input document. TranslateDocument supports translations from English to any supported language, and from any supported language to English. Therefore, specify either the source language code or the target language code as “en” (English).   If you set the Formality parameter, the request will fail if the target language does not support formality. For a list of target languages that support formality, see Setting formality. 
    */
   translateDocument(callback?: (err: AWSError, data: Translate.Types.TranslateDocumentResponse) => void): Request<Translate.Types.TranslateDocumentResponse, AWSError>;
   /**
@@ -177,6 +177,7 @@ declare namespace Translate {
   }
   export type AppliedTerminologyList = AppliedTerminology[];
   export type BoundedLengthString = string;
+  export type Brevity = "ON"|string;
   export type ClientTokenString = string;
   export type ContentType = string;
   export interface CreateParallelDataRequest {
@@ -520,11 +521,11 @@ declare namespace Translate {
     /**
      * The URI of the Amazon S3 folder that contains the parallel data input file. The folder must be in the same Region as the API endpoint you are calling.
      */
-    S3Uri: S3Uri;
+    S3Uri?: S3Uri;
     /**
      * The format of the parallel data input file.
      */
-    Format: ParallelDataFormat;
+    Format?: ParallelDataFormat;
   }
   export interface ParallelDataDataLocation {
     /**
@@ -649,7 +650,7 @@ declare namespace Translate {
      */
     ClientToken: ClientTokenString;
     /**
-     * Settings to configure your translation output, including the option to set the formality level of the output text and the option to mask profane words and phrases.
+     * Settings to configure your translation output. You can configure the following options:   Brevity: not supported.   Formality: sets the formality level of the output text.   Profanity: masks profane words and phrases in your translation output.  
      */
     Settings?: TranslationSettings;
   }
@@ -896,13 +897,16 @@ declare namespace Translate {
      */
     TerminologyNames?: ResourceNameList;
     /**
-     * The language code for the language of the source text. Do not use auto, because TranslateDocument does not support language auto-detection. For a list of supported language codes, see Supported languages.
+     * The language code for the language of the source text. For a list of supported language codes, see Supported languages. To have Amazon Translate determine the source language of your text, you can specify auto in the SourceLanguageCode field. If you specify auto, Amazon Translate will call Amazon Comprehend to determine the source language.  If you specify auto, you must send the TranslateDocument request in a region that supports Amazon Comprehend. Otherwise, the request returns an error indicating that autodetect is not supported.  
      */
     SourceLanguageCode: LanguageCodeString;
     /**
      * The language code requested for the translated document. For a list of supported language codes, see Supported languages.
      */
     TargetLanguageCode: LanguageCodeString;
+    /**
+     * Settings to configure your translation output. You can configure the following options:   Brevity: not supported.   Formality: sets the formality level of the output text.   Profanity: masks profane words and phrases in your translation output.  
+     */
     Settings?: TranslationSettings;
   }
   export interface TranslateDocumentResponse {
@@ -942,7 +946,7 @@ declare namespace Translate {
      */
     TargetLanguageCode: LanguageCodeString;
     /**
-     * Settings to configure your translation output, including the option to set the formality level of the output text and the option to mask profane words and phrases.
+     * Settings to configure your translation output. You can configure the following options:   Brevity: reduces the length of the translated output for most translations.   Formality: sets the formality level of the output text.   Profanity: masks profane words and phrases in your translation output.  
      */
     Settings?: TranslationSettings;
   }
@@ -978,13 +982,17 @@ declare namespace Translate {
   export type TranslatedTextString = string;
   export interface TranslationSettings {
     /**
-     * You can optionally specify the desired level of formality for translations to supported target languages. The formality setting controls the level of formal language usage (also known as register) in the translation output. You can set the value to informal or formal. If you don't specify a value for formality, or if the target language doesn't support formality, the translation will ignore the formality setting.  If you specify multiple target languages for the job, translate ignores the formality setting for any unsupported target language. For a list of target languages that support formality, see Supported languages in the Amazon Translate Developer Guide.
+     * You can specify the desired level of formality for translations to supported target languages. The formality setting controls the level of formal language usage (also known as register) in the translation output. You can set the value to informal or formal. If you don't specify a value for formality, or if the target language doesn't support formality, the translation will ignore the formality setting.  If you specify multiple target languages for the job, translate ignores the formality setting for any unsupported target language. For a list of target languages that support formality, see Supported languages in the Amazon Translate Developer Guide.
      */
     Formality?: Formality;
     /**
-     * Enable the profanity setting if you want Amazon Translate to mask profane words and phrases in your translation output. To mask profane words and phrases, Amazon Translate replaces them with the grawlix string “?$#@$“. This 5-character sequence is used for each profane word or phrase, regardless of the length or number of words. Amazon Translate doesn't detect profanity in all of its supported languages. For languages that don't support profanity detection, see Unsupported languages in the Amazon Translate Developer Guide. If you specify multiple target languages for the job, all the target languages must support profanity masking. If any of the target languages don't support profanity masking, the translation job won't mask profanity for any target language.
+     * You can enable the profanity setting if you want to mask profane words and phrases in your translation output. To mask profane words and phrases, Amazon Translate replaces them with the grawlix string “?$#@$“. This 5-character sequence is used for each profane word or phrase, regardless of the length or number of words. Amazon Translate doesn't detect profanity in all of its supported languages. For languages that don't support profanity detection, see Unsupported languages in the Amazon Translate Developer Guide. If you specify multiple target languages for the job, all the target languages must support profanity masking. If any of the target languages don't support profanity masking, the translation job won't mask profanity for any target language.
      */
     Profanity?: Profanity;
+    /**
+     * When you turn on brevity, Amazon Translate reduces the length of the translation output for most translations (when compared with the same translation with brevity turned off). By default, brevity is turned off. If you turn on brevity for a translation request with an unsupported language pair, the translation proceeds with the brevity setting turned off. For the language pairs that brevity supports, see Using brevity in the Amazon Translate Developer Guide.
+     */
+    Brevity?: Brevity;
   }
   export type UnboundedLengthString = string;
   export interface UntagResourceRequest {

package/node_modules/aws-sdk/dist/aws-sdk-core-react-native.js

@@ -83,7 +83,7 @@ return /******/ (function(modules) { // webpackBootstrap
 	  /**
 	   * @constant
 	   */
-	  VERSION: '2.1484.0',
+	  VERSION: '2.1486.0',
 
 	  /**
 	   * @api private