cdk-lambda-subminute 2.0.283 → 2.0.285

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/mediapackagev2.d.ts

@@ -378,6 +378,7 @@ declare namespace MediaPackageV2 {
      * Inserts EXT-X-PROGRAM-DATE-TIME tags in the output manifest at the interval that you specify. If you don't enter an interval, EXT-X-PROGRAM-DATE-TIME tags aren't included in the manifest. The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player. ID3Timed metadata messages generate every 5 seconds whenever the content is ingested. Irrespective of this parameter, if any ID3Timed metadata is in the HLS input, it is passed through to the HLS output.
      */
     ProgramDateTimeIntervalSeconds?: CreateHlsManifestConfigurationProgramDateTimeIntervalSecondsInteger;
+    FilterConfiguration?: FilterConfiguration;
   }
   export type CreateHlsManifestConfigurationManifestWindowSecondsInteger = number;
   export type CreateHlsManifestConfigurationProgramDateTimeIntervalSecondsInteger = number;
@@ -400,6 +401,7 @@ declare namespace MediaPackageV2 {
      * Inserts EXT-X-PROGRAM-DATE-TIME tags in the output manifest at the interval that you specify. If you don't enter an interval, EXT-X-PROGRAM-DATE-TIME tags aren't included in the manifest. The tags sync the stream to the wall clock so that viewers can seek to a specific time in the playback timeline on the player. ID3Timed metadata messages generate every 5 seconds whenever the content is ingested. Irrespective of this parameter, if any ID3Timed metadata is in the HLS input, it is passed through to the HLS output.
      */
     ProgramDateTimeIntervalSeconds?: CreateLowLatencyHlsManifestConfigurationProgramDateTimeIntervalSecondsInteger;
+    FilterConfiguration?: FilterConfiguration;
   }
   export type CreateLowLatencyHlsManifestConfigurationManifestWindowSecondsInteger = number;
   export type CreateLowLatencyHlsManifestConfigurationProgramDateTimeIntervalSecondsInteger = number;
@@ -610,6 +612,26 @@ declare namespace MediaPackageV2 {
      */
     CmafEncryptionMethod?: CmafEncryptionMethod;
   }
+  export interface FilterConfiguration {
+    /**
+     * Optionally specify one or more manifest filters for all of your manifest egress requests. When you include a manifest filter, note that you cannot use an identical manifest filter query parameter for this manifest's endpoint URL.
+     */
+    ManifestFilter?: FilterConfigurationManifestFilterString;
+    /**
+     * Optionally specify the start time for all of your manifest egress requests. When you include start time, note that you cannot use start time query parameters for this manifest's endpoint URL.
+     */
+    Start?: Timestamp;
+    /**
+     * Optionally specify the end time for all of your manifest egress requests. When you include end time, note that you cannot use end time query parameters for this manifest's endpoint URL.
+     */
+    End?: Timestamp;
+    /**
+     * Optionally specify the time delay for all of your manifest egress requests. Enter a value that is smaller than your endpoint's startover window. When you include time delay, note that you cannot use time delay query parameters for this manifest's endpoint URL.
+     */
+    TimeDelaySeconds?: FilterConfigurationTimeDelaySecondsInteger;
+  }
+  export type FilterConfigurationManifestFilterString = string;
+  export type FilterConfigurationTimeDelaySecondsInteger = number;
   export interface GetChannelGroupRequest {
     /**
      * The name that describes the channel group. The name is the primary identifier for the channel group, and must be unique for your account in the AWS Region.
@@ -733,6 +755,7 @@ declare namespace MediaPackageV2 {
      */
     ProgramDateTimeIntervalSeconds?: Integer;
     ScteHls?: ScteHls;
+    FilterConfiguration?: FilterConfiguration;
   }
   export type GetHlsManifests = GetHlsManifestConfiguration[];
   export interface GetLowLatencyHlsManifestConfiguration {
@@ -757,6 +780,7 @@ declare namespace MediaPackageV2 {
      */
     ProgramDateTimeIntervalSeconds?: Integer;
     ScteHls?: ScteHls;
+    FilterConfiguration?: FilterConfiguration;
   }
   export type GetLowLatencyHlsManifests = GetLowLatencyHlsManifestConfiguration[];
   export interface GetOriginEndpointPolicyRequest {

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

@@ -245,6 +245,14 @@ declare class RDS extends Service {
    * Creates an Aurora global database spread across multiple Amazon Web Services Regions. The global database contains a single primary cluster with read-write capability, and a read-only secondary cluster that receives data from the primary cluster through high-speed replication performed by the Aurora storage subsystem. You can create a global database that is initially empty, and then create the primary and secondary DB clusters in the global database. Or you can specify an existing Aurora cluster during the create operation, and this cluster becomes the primary cluster of the global database.  This operation applies only to Aurora DB clusters. 
    */
   createGlobalCluster(callback?: (err: AWSError, data: RDS.Types.CreateGlobalClusterResult) => void): Request<RDS.Types.CreateGlobalClusterResult, AWSError>;
+  /**
+   * Creates a zero-ETL integration with Amazon Redshift. For more information, see Working with Amazon Aurora zero-ETL integrations with Amazon Redshift in the Amazon Aurora User Guide.
+   */
+  createIntegration(params: RDS.Types.CreateIntegrationMessage, callback?: (err: AWSError, data: RDS.Types.Integration) => void): Request<RDS.Types.Integration, AWSError>;
+  /**
+   * Creates a zero-ETL integration with Amazon Redshift. For more information, see Working with Amazon Aurora zero-ETL integrations with Amazon Redshift in the Amazon Aurora User Guide.
+   */
+  createIntegration(callback?: (err: AWSError, data: RDS.Types.Integration) => void): Request<RDS.Types.Integration, AWSError>;
   /**
    * Creates a new option group. You can create up to 20 option groups. This command doesn't apply to RDS Custom.
    */
@@ -389,6 +397,14 @@ declare class RDS extends Service {
    * Deletes a global database cluster. The primary and secondary clusters must already be detached or destroyed first.  This action only applies to Aurora DB clusters. 
    */
   deleteGlobalCluster(callback?: (err: AWSError, data: RDS.Types.DeleteGlobalClusterResult) => void): Request<RDS.Types.DeleteGlobalClusterResult, AWSError>;
+  /**
+   * Deletes a zero-ETL integration with Amazon Redshift. For more information, see Deleting Amazon Aurora zero-ETL integrations with Amazon Redshift in the Amazon Aurora User Guide 
+   */
+  deleteIntegration(params: RDS.Types.DeleteIntegrationMessage, callback?: (err: AWSError, data: RDS.Types.Integration) => void): Request<RDS.Types.Integration, AWSError>;
+  /**
+   * Deletes a zero-ETL integration with Amazon Redshift. For more information, see Deleting Amazon Aurora zero-ETL integrations with Amazon Redshift in the Amazon Aurora User Guide 
+   */
+  deleteIntegration(callback?: (err: AWSError, data: RDS.Types.Integration) => void): Request<RDS.Types.Integration, AWSError>;
   /**
    * Deletes an existing option group.
    */
@@ -661,6 +677,14 @@ declare class RDS extends Service {
    * Returns information about Aurora global database clusters. This API supports pagination. For more information on Amazon Aurora, see  What is Amazon Aurora? in the Amazon Aurora User Guide.  This action only applies to Aurora DB clusters. 
    */
   describeGlobalClusters(callback?: (err: AWSError, data: RDS.Types.GlobalClustersMessage) => void): Request<RDS.Types.GlobalClustersMessage, AWSError>;
+  /**
+   * Describe one or more zero-ETL integration with Amazon Redshift. For more information, see Viewing and monitoring Amazon Aurora zero-ETL integrations with Amazon Redshift in the Amazon Aurora User Guide 
+   */
+  describeIntegrations(params: RDS.Types.DescribeIntegrationsMessage, callback?: (err: AWSError, data: RDS.Types.DescribeIntegrationsResponse) => void): Request<RDS.Types.DescribeIntegrationsResponse, AWSError>;
+  /**
+   * Describe one or more zero-ETL integration with Amazon Redshift. For more information, see Viewing and monitoring Amazon Aurora zero-ETL integrations with Amazon Redshift in the Amazon Aurora User Guide 
+   */
+  describeIntegrations(callback?: (err: AWSError, data: RDS.Types.DescribeIntegrationsResponse) => void): Request<RDS.Types.DescribeIntegrationsResponse, AWSError>;
   /**
    * Describes all available options.
    */
@@ -1328,6 +1352,7 @@ declare namespace RDS {
   export interface ApplyPendingMaintenanceActionResult {
     ResourcePendingMaintenanceActions?: ResourcePendingMaintenanceActions;
   }
+  export type Arn = string;
   export type AttributeValueList = String[];
   export type AuditPolicyState = "locked"|"unlocked"|string;
   export type AuthScheme = "SECRETS"|string;
@@ -2749,6 +2774,29 @@ declare namespace RDS {
   export interface CreateGlobalClusterResult {
     GlobalCluster?: GlobalCluster;
   }
+  export interface CreateIntegrationMessage {
+    /**
+     * The Amazon Resource Name (ARN) of the Aurora DB cluster to use as the source for replication.
+     */
+    SourceArn: SourceArn;
+    /**
+     * The ARN of the Redshift data warehouse to use as the target for replication.
+     */
+    TargetArn: Arn;
+    /**
+     * The name of the integration.
+     */
+    IntegrationName: IntegrationName;
+    /**
+     * The Amazon Web Services Key Management System (Amazon Web Services KMS) key identifier for the key to use to encrypt the integration. If you don't specify an encryption key, Aurora uses a default Amazon Web Services owned key. 
+     */
+    KMSKeyId?: String;
+    /**
+     * An optional set of non-secret key–value pairs that contains additional contextual information about the data. For more information, see Encryption context in the Amazon Web Services Key Management Service Developer Guide. You can only include this parameter if you specify the KMSKeyId parameter.
+     */
+    AdditionalEncryptionContext?: EncryptionContextMap;
+    Tags?: TagList;
+  }
   export interface CreateOptionGroupMessage {
     /**
      * Specifies the name of the option group to be created. Constraints:   Must be 1 to 255 letters, numbers, or hyphens   First character must be a letter   Can't end with a hyphen or contain two consecutive hyphens   Example: myoptiongroup 
@@ -3654,6 +3702,10 @@ declare namespace RDS {
      * Indicates whether the DB engine version supports forwarding write operations from reader DB instances to the writer DB instance in the DB cluster. By default, write operations aren't allowed on reader DB instances. Valid for: Aurora DB clusters only
      */
     SupportsLocalWriteForwarding?: BooleanOptional;
+    /**
+     * Indicates whether the DB engine version supports Aurora zero-ETL integrations with Amazon Redshift.
+     */
+    SupportsIntegrations?: Boolean;
   }
   export type DBEngineVersionList = DBEngineVersion[];
   export interface DBEngineVersionMessage {
@@ -4868,6 +4920,12 @@ declare namespace RDS {
   export interface DeleteGlobalClusterResult {
     GlobalCluster?: GlobalCluster;
   }
+  export interface DeleteIntegrationMessage {
+    /**
+     * The unique identifier of the integration.
+     */
+    IntegrationIdentifier: IntegrationIdentifier;
+  }
   export interface DeleteOptionGroupMessage {
     /**
      * The name of the option group to be deleted.  You can't delete default option groups. 
@@ -5657,6 +5715,34 @@ declare namespace RDS {
      */
     Marker?: String;
   }
+  export interface DescribeIntegrationsMessage {
+    /**
+     * The unique identifier of the integration.
+     */
+    IntegrationIdentifier?: IntegrationIdentifier;
+    /**
+     * A filter that specifies one or more resources to return.
+     */
+    Filters?: FilterList;
+    /**
+     * The maximum number of records to include in the response. If more records exist than the specified MaxRecords value, a pagination token called a marker is included in the response so that you can retrieve the remaining results. Default: 100 Constraints: Minimum 20, maximum 100.
+     */
+    MaxRecords?: IntegerOptional;
+    /**
+     * An optional pagination token provided by a previous DescribeIntegrations request. If this parameter is specified, the response includes only records beyond the marker, up to the value specified by MaxRecords.
+     */
+    Marker?: Marker;
+  }
+  export interface DescribeIntegrationsResponse {
+    /**
+     * A pagination token that can be used in a later DescribeIntegrations request.
+     */
+    Marker?: Marker;
+    /**
+     * A list of integrations.
+     */
+    Integrations?: IntegrationList;
+  }
   export interface DescribeOptionGroupOptionsMessage {
     /**
      * A required parameter. Options available for the given engine name are described. Valid Values:    mariadb     mysql     oracle-ee     oracle-ee-cdb     oracle-se2     oracle-se2-cdb     postgres     sqlserver-ee     sqlserver-se     sqlserver-ex     sqlserver-web   
@@ -5968,6 +6054,7 @@ declare namespace RDS {
     EC2SecurityGroupOwnerId?: String;
   }
   export type EC2SecurityGroupList = EC2SecurityGroup[];
+  export type EncryptionContextMap = {[key: string]: String};
   export interface Endpoint {
     /**
      * Specifies the DNS address of the DB instance.
@@ -6346,6 +6433,61 @@ declare namespace RDS {
   export type IPRangeList = IPRange[];
   export type Integer = number;
   export type IntegerOptional = number;
+  export interface Integration {
+    /**
+     * The Amazon Resource Name (ARN) of the Aurora DB cluster used as the source for replication.
+     */
+    SourceArn?: SourceArn;
+    /**
+     * The ARN of the Redshift data warehouse used as the target for replication.
+     */
+    TargetArn?: Arn;
+    /**
+     * The name of the integration.
+     */
+    IntegrationName?: IntegrationName;
+    /**
+     * The ARN of the integration.
+     */
+    IntegrationArn?: IntegrationArn;
+    /**
+     * The Amazon Web Services Key Management System (Amazon Web Services KMS) key identifier for the key used to to encrypt the integration. 
+     */
+    KMSKeyId?: String;
+    /**
+     * The encryption context for the integration. For more information, see Encryption context in the Amazon Web Services Key Management Service Developer Guide.
+     */
+    AdditionalEncryptionContext?: EncryptionContextMap;
+    /**
+     * The current status of the integration.
+     */
+    Status?: IntegrationStatus;
+    Tags?: TagList;
+    /**
+     * The time when the integration was created, in Universal Coordinated Time (UTC).
+     */
+    CreateTime?: TStamp;
+    /**
+     * Any errors associated with the integration.
+     */
+    Errors?: IntegrationErrorList;
+  }
+  export type IntegrationArn = string;
+  export interface IntegrationError {
+    /**
+     * The error code associated with the integration.
+     */
+    ErrorCode: String;
+    /**
+     * A message explaining the error.
+     */
+    ErrorMessage?: String;
+  }
+  export type IntegrationErrorList = IntegrationError[];
+  export type IntegrationIdentifier = string;
+  export type IntegrationList = Integration[];
+  export type IntegrationName = string;
+  export type IntegrationStatus = "creating"|"active"|"modifying"|"failed"|"deleting"|"syncing"|"needs_attention"|string;
   export type KeyList = String[];
   export type KmsKeyIdOrArn = string;
   export interface ListTagsForResourceMessage {
@@ -6362,6 +6504,7 @@ declare namespace RDS {
   export type LogTypeList = String[];
   export type Long = number;
   export type LongOptional = number;
+  export type Marker = string;
   export interface MasterUserSecret {
     /**
      * The Amazon Resource Name (ARN) of the secret.
@@ -9179,6 +9322,7 @@ declare namespace RDS {
      */
     MaxCapacity?: DoubleOptional;
   }
+  export type SourceArn = string;
   export type SourceIdsList = String[];
   export interface SourceRegion {
     /**
@@ -9545,6 +9689,10 @@ declare namespace RDS {
      * Indicates whether the target engine version supports forwarding write operations from reader DB instances to the writer DB instance in the DB cluster. By default, write operations aren't allowed on reader DB instances. Valid for: Aurora DB clusters only
      */
     SupportsLocalWriteForwarding?: BooleanOptional;
+    /**
+     * Indicates whether the DB engine version supports Aurora zero-ETL integrations with Amazon Redshift.
+     */
+    SupportsIntegrations?: BooleanOptional;
   }
   export interface UserAuthConfig {
     /**