Updates SDK to v2.757.0

.changes/2.757.0.json

@@ -0,0 +1,22 @@
+[
+    {
+        "type": "feature",
+        "category": "CloudWatchEvents",
+        "description": "Add support for Redshift Data API Targets"
+    },
+    {
+        "type": "feature",
+        "category": "EventBridge",
+        "description": "Add support for Redshift Data API Targets"
+    },
+    {
+        "type": "feature",
+        "category": "Glue",
+        "description": "Adding support to update multiple partitions of a table in a single request"
+    },
+    {
+        "type": "feature",
+        "category": "IoTSiteWise",
+        "description": "This release supports IAM mode for SiteWise Monitor portals"
+    }
+]

CHANGELOG.md

@@ -1,7 +1,13 @@
 # Changelog for AWS SDK for JavaScript
-<!--LATEST=2.756.0-->
+<!--LATEST=2.757.0-->
 <!--ENTRYINSERT-->
 
+## 2.757.0
+* feature: CloudWatchEvents: Add support for Redshift Data API Targets
+* feature: EventBridge: Add support for Redshift Data API Targets
+* feature: Glue: Adding support to update multiple partitions of a table in a single request
+* feature: IoTSiteWise: This release supports IAM mode for SiteWise Monitor portals
+
 ## 2.756.0
 * feature: CodeStarconnections: New integration with the GitHub provider type.
 * feature: MediaLive: AWS Elemental MediaLive now supports batch operations, which allow users to start, stop, and delete multiple MediaLive resources with a single request.

README.md

@@ -25,7 +25,7 @@ version.
 To use the SDK in the browser, simply add the following script tag to your
 HTML pages:
 
-    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.756.0.min.js"></script>
+    <script src="https://sdk.amazonaws.com/js/aws-sdk-2.757.0.min.js"></script>
 
 You can also build a custom browser SDK with your specified set of AWS services.
 This can allow you to reduce the SDK's size, specify different API versions of

apis/eventbridge-2015-10-07.min.json

@@ -479,7 +479,7 @@
                 },
                 "Source": {},
                 "Resources": {
-                  "shape": "S37"
+                  "shape": "S3d"
                 },
                 "DetailType": {},
                 "Detail": {},
@@ -526,7 +526,7 @@
                 },
                 "Source": {},
                 "Resources": {
-                  "shape": "S37"
+                  "shape": "S3d"
                 },
                 "DetailType": {},
                 "Detail": {}
@@ -920,6 +920,23 @@
                 "value": {}
               }
             }
+          },
+          "RedshiftDataParameters": {
+            "type": "structure",
+            "required": [
+              "Database",
+              "Sql"
+            ],
+            "members": {
+              "SecretManagerArn": {},
+              "Database": {},
+              "DbUser": {},
+              "Sql": {},
+              "StatementName": {},
+              "WithEvent": {
+                "type": "boolean"
+              }
+            }
           }
         }
       }
@@ -928,7 +945,7 @@
       "type": "list",
       "member": {}
     },
-    "S37": {
+    "S3d": {
       "type": "list",
       "member": {}
     }

apis/eventbridge-2015-10-07.normal.json

@@ -651,7 +651,7 @@
           "shape": "InternalException"
         }
       ],
-      "documentation": "<p>Adds the specified targets to the specified rule, or updates the targets if they are already associated with the rule.</p> <p>Targets are the resources that are invoked when a rule is triggered.</p> <p>You can configure the following as targets for Events:</p> <ul> <li> <p>EC2 instances</p> </li> <li> <p>SSM Run Command</p> </li> <li> <p>SSM Automation</p> </li> <li> <p>AWS Lambda functions</p> </li> <li> <p>Data streams in Amazon Kinesis Data Streams</p> </li> <li> <p>Data delivery streams in Amazon Kinesis Data Firehose</p> </li> <li> <p>Amazon ECS tasks</p> </li> <li> <p>AWS Step Functions state machines</p> </li> <li> <p>AWS Batch jobs</p> </li> <li> <p>AWS CodeBuild projects</p> </li> <li> <p>Pipelines in AWS CodePipeline</p> </li> <li> <p>Amazon Inspector assessment templates</p> </li> <li> <p>Amazon SNS topics</p> </li> <li> <p>Amazon SQS queues, including FIFO queues</p> </li> <li> <p>The default event bus of another AWS account</p> </li> <li> <p>Amazon API Gateway REST APIs</p> </li> </ul> <p>Creating rules with built-in targets is supported only in the AWS Management Console. The built-in targets are <code>EC2 CreateSnapshot API call</code>, <code>EC2 RebootInstances API call</code>, <code>EC2 StopInstances API call</code>, and <code>EC2 TerminateInstances API call</code>. </p> <p>For some target types, <code>PutTargets</code> provides target-specific parameters. If the target is a Kinesis data stream, you can optionally specify which shard the event goes to by using the <code>KinesisParameters</code> argument. To invoke a command on multiple EC2 instances with one rule, you can use the <code>RunCommandParameters</code> field.</p> <p>To be able to make API calls against the resources that you own, Amazon EventBridge (CloudWatch Events) needs the appropriate permissions. For AWS Lambda and Amazon SNS resources, EventBridge relies on resource-based policies. For EC2 instances, Kinesis data streams, AWS Step Functions state machines and API Gateway REST APIs, EventBridge relies on IAM roles that you specify in the <code>RoleARN</code> argument in <code>PutTargets</code>. For more information, see <a href=\"https://docs.aws.amazon.com/eventbridge/latest/userguide/auth-and-access-control-eventbridge.html\">Authentication and Access Control</a> in the <i>Amazon EventBridge User Guide</i>.</p> <p>If another AWS account is in the same region and has granted you permission (using <code>PutPermission</code>), you can send events to that account. Set that account's event bus as a target of the rules in your account. To send the matched events to the other account, specify that account's event bus as the <code>Arn</code> value when you run <code>PutTargets</code>. If your account sends events to another account, your account is charged for each sent event. Each event sent to another account is charged as a custom event. The account receiving the event is not charged. For more information, see <a href=\"https://aws.amazon.com/eventbridge/pricing/\">Amazon EventBridge (CloudWatch Events) Pricing</a>.</p> <note> <p> <code>Input</code>, <code>InputPath</code>, and <code>InputTransformer</code> are not available with <code>PutTarget</code> if the target is an event bus of a different AWS account.</p> </note> <p>If you are setting the event bus of another account as the target, and that account granted permission to your account through an organization instead of directly by the account ID, then you must specify a <code>RoleArn</code> with proper permissions in the <code>Target</code> structure. For more information, see <a href=\"https://docs.aws.amazon.com/eventbridge/latest/userguide/eventbridge-cross-account-event-delivery.html\">Sending and Receiving Events Between AWS Accounts</a> in the <i>Amazon EventBridge User Guide</i>.</p> <p>For more information about enabling cross-account events, see <a>PutPermission</a>.</p> <p> <b>Input</b>, <b>InputPath</b>, and <b>InputTransformer</b> are mutually exclusive and optional parameters of a target. When a rule is triggered due to a matched event:</p> <ul> <li> <p>If none of the following arguments are specified for a target, then the entire event is passed to the target in JSON format (unless the target is Amazon EC2 Run Command or Amazon ECS task, in which case nothing from the event is passed to the target).</p> </li> <li> <p>If <b>Input</b> is specified in the form of valid JSON, then the matched event is overridden with this constant.</p> </li> <li> <p>If <b>InputPath</b> is specified in the form of JSONPath (for example, <code>$.detail</code>), then only the part of the event specified in the path is passed to the target (for example, only the detail part of the event is passed).</p> </li> <li> <p>If <b>InputTransformer</b> is specified, then one or more specified JSONPaths are extracted from the event and used as values in a template that you specify as the input to the target.</p> </li> </ul> <p>When you specify <code>InputPath</code> or <code>InputTransformer</code>, you must use JSON dot notation, not bracket notation.</p> <p>When you add targets to a rule and the associated rule triggers soon after, new or updated targets might not be immediately invoked. Allow a short period of time for changes to take effect.</p> <p>This action can partially fail if too many requests are made at the same time. If that happens, <code>FailedEntryCount</code> is non-zero in the response and each entry in <code>FailedEntries</code> provides the ID of the failed target and the error code.</p>"
+      "documentation": "<p>Adds the specified targets to the specified rule, or updates the targets if they are already associated with the rule.</p> <p>Targets are the resources that are invoked when a rule is triggered.</p> <p>You can configure the following as targets for Events:</p> <ul> <li> <p>EC2 instances</p> </li> <li> <p>SSM Run Command</p> </li> <li> <p>SSM Automation</p> </li> <li> <p>AWS Lambda functions</p> </li> <li> <p>Data streams in Amazon Kinesis Data Streams</p> </li> <li> <p>Data delivery streams in Amazon Kinesis Data Firehose</p> </li> <li> <p>Amazon ECS tasks</p> </li> <li> <p>AWS Step Functions state machines</p> </li> <li> <p>AWS Batch jobs</p> </li> <li> <p>AWS CodeBuild projects</p> </li> <li> <p>Pipelines in AWS CodePipeline</p> </li> <li> <p>Amazon Inspector assessment templates</p> </li> <li> <p>Amazon SNS topics</p> </li> <li> <p>Amazon SQS queues, including FIFO queues</p> </li> <li> <p>The default event bus of another AWS account</p> </li> <li> <p>Amazon API Gateway REST APIs</p> </li> <li> <p>Redshift Clusters to invoke Data API ExecuteStatement on</p> </li> </ul> <p>Creating rules with built-in targets is supported only in the AWS Management Console. The built-in targets are <code>EC2 CreateSnapshot API call</code>, <code>EC2 RebootInstances API call</code>, <code>EC2 StopInstances API call</code>, and <code>EC2 TerminateInstances API call</code>. </p> <p>For some target types, <code>PutTargets</code> provides target-specific parameters. If the target is a Kinesis data stream, you can optionally specify which shard the event goes to by using the <code>KinesisParameters</code> argument. To invoke a command on multiple EC2 instances with one rule, you can use the <code>RunCommandParameters</code> field.</p> <p>To be able to make API calls against the resources that you own, Amazon EventBridge (CloudWatch Events) needs the appropriate permissions. For AWS Lambda and Amazon SNS resources, EventBridge relies on resource-based policies. For EC2 instances, Kinesis data streams, AWS Step Functions state machines and API Gateway REST APIs, EventBridge relies on IAM roles that you specify in the <code>RoleARN</code> argument in <code>PutTargets</code>. For more information, see <a href=\"https://docs.aws.amazon.com/eventbridge/latest/userguide/auth-and-access-control-eventbridge.html\">Authentication and Access Control</a> in the <i>Amazon EventBridge User Guide</i>.</p> <p>If another AWS account is in the same region and has granted you permission (using <code>PutPermission</code>), you can send events to that account. Set that account's event bus as a target of the rules in your account. To send the matched events to the other account, specify that account's event bus as the <code>Arn</code> value when you run <code>PutTargets</code>. If your account sends events to another account, your account is charged for each sent event. Each event sent to another account is charged as a custom event. The account receiving the event is not charged. For more information, see <a href=\"https://aws.amazon.com/eventbridge/pricing/\">Amazon EventBridge (CloudWatch Events) Pricing</a>.</p> <note> <p> <code>Input</code>, <code>InputPath</code>, and <code>InputTransformer</code> are not available with <code>PutTarget</code> if the target is an event bus of a different AWS account.</p> </note> <p>If you are setting the event bus of another account as the target, and that account granted permission to your account through an organization instead of directly by the account ID, then you must specify a <code>RoleArn</code> with proper permissions in the <code>Target</code> structure. For more information, see <a href=\"https://docs.aws.amazon.com/eventbridge/latest/userguide/eventbridge-cross-account-event-delivery.html\">Sending and Receiving Events Between AWS Accounts</a> in the <i>Amazon EventBridge User Guide</i>.</p> <p>For more information about enabling cross-account events, see <a>PutPermission</a>.</p> <p> <b>Input</b>, <b>InputPath</b>, and <b>InputTransformer</b> are mutually exclusive and optional parameters of a target. When a rule is triggered due to a matched event:</p> <ul> <li> <p>If none of the following arguments are specified for a target, then the entire event is passed to the target in JSON format (unless the target is Amazon EC2 Run Command or Amazon ECS task, in which case nothing from the event is passed to the target).</p> </li> <li> <p>If <b>Input</b> is specified in the form of valid JSON, then the matched event is overridden with this constant.</p> </li> <li> <p>If <b>InputPath</b> is specified in the form of JSONPath (for example, <code>$.detail</code>), then only the part of the event specified in the path is passed to the target (for example, only the detail part of the event is passed).</p> </li> <li> <p>If <b>InputTransformer</b> is specified, then one or more specified JSONPaths are extracted from the event and used as values in a template that you specify as the input to the target.</p> </li> </ul> <p>When you specify <code>InputPath</code> or <code>InputTransformer</code>, you must use JSON dot notation, not bracket notation.</p> <p>When you add targets to a rule and the associated rule triggers soon after, new or updated targets might not be immediately invoked. Allow a short period of time for changes to take effect.</p> <p>This action can partially fail if too many requests are made at the same time. If that happens, <code>FailedEntryCount</code> is non-zero in the response and each entry in <code>FailedEntries</code> provides the ID of the failed target and the error code.</p>"
     },
     "RemovePermission": {
       "name": "RemovePermission",
@@ -967,6 +967,18 @@
         }
       }
     },
+    "Database": {
+      "type": "string",
+      "max": 64,
+      "min": 1,
+      "pattern": "([a-zA-Z0-9]+)|(\\$(\\.[\\w_-]+(\\[(\\d+|\\*)\\])*)*)"
+    },
+    "DbUser": {
+      "type": "string",
+      "max": 128,
+      "min": 1,
+      "pattern": "([a-zA-Z0-9]+)|(\\$(\\.[\\w_-]+(\\[(\\d+|\\*)\\])*)*)"
+    },
     "DeactivateEventSourceRequest": {
       "type": "structure",
       "required": [
@@ -2124,6 +2136,46 @@
       "max": 512,
       "pattern": "[^\\x00-\\x09\\x0B\\x0C\\x0E-\\x1F\\x7F]+"
     },
+    "RedshiftDataParameters": {
+      "type": "structure",
+      "required": [
+        "Database",
+        "Sql"
+      ],
+      "members": {
+        "SecretManagerArn": {
+          "shape": "RedshiftSecretManagerArn",
+          "documentation": "<p>The name or ARN of the secret that enables access to the database. Required when authenticating using AWS Secrets Manager.</p>"
+        },
+        "Database": {
+          "shape": "Database",
+          "documentation": "<p>The name of the database. Required when authenticating using temporary credentials.</p>"
+        },
+        "DbUser": {
+          "shape": "DbUser",
+          "documentation": "<p>The database user name. Required when authenticating using temporary credentials.</p>"
+        },
+        "Sql": {
+          "shape": "Sql",
+          "documentation": "<p>The SQL statement text to run.</p>"
+        },
+        "StatementName": {
+          "shape": "StatementName",
+          "documentation": "<p>The name of the SQL statement. You can name the SQL statement when you create it to identify the query.</p>"
+        },
+        "WithEvent": {
+          "shape": "Boolean",
+          "documentation": "<p>Indicates whether to send an event back to EventBridge after the SQL statement runs.</p>"
+        }
+      },
+      "documentation": "<p>These are custom parameters to be used when the target is a Redshift cluster to invoke the Redshift Data API ExecuteStatement based on EventBridge events.</p>"
+    },
+    "RedshiftSecretManagerArn": {
+      "type": "string",
+      "max": 1600,
+      "min": 1,
+      "pattern": "(^arn:aws([a-z]|\\-)*:secretsmanager:[a-z0-9-.]+:.*)|(\\$(\\.[\\w_-]+(\\[(\\d+|\\*)\\])*)*)"
+    },
     "RemovePermissionRequest": {
       "type": "structure",
       "required": [
@@ -2345,6 +2397,11 @@
       "type": "string",
       "max": 256
     },
+    "Sql": {
+      "type": "string",
+      "max": 100000,
+      "min": 1
+    },
     "SqsParameters": {
       "type": "structure",
       "members": {
@@ -2361,6 +2418,11 @@
       "min": 1,
       "pattern": "[a-zA-Z0-9-_]+"
     },
+    "StatementName": {
+      "type": "string",
+      "max": 500,
+      "min": 1
+    },
     "String": {
       "type": "string"
     },
@@ -2485,6 +2547,10 @@
         "HttpParameters": {
           "shape": "HttpParameters",
           "documentation": "<p>Contains the HTTP parameters to use when the target is a API Gateway REST endpoint.</p> <p>If you specify an API Gateway REST API as a target, you can use this parameter to specify headers, path parameter, query string keys/values as part of your target invoking request.</p>"
+        },
+        "RedshiftDataParameters": {
+          "shape": "RedshiftDataParameters",
+          "documentation": "<p>Contains the Redshift Data API parameters to use when the target is a Redshift cluster.</p> <p>If you specify a Redshift Cluster as a Target, you can use this to specify parameters to invoke the Redshift Data API ExecuteStatement based on EventBridge events.</p>"
         }
       },
       "documentation": "<p>Targets are the resources to be invoked when a rule is triggered. For a complete list of services and resources that can be set as a target, see <a>PutTargets</a>.</p> <p>If you are setting the event bus of another account as the target, and that account granted permission to your account through an organization instead of directly by the account ID, then you must specify a <code>RoleArn</code> with proper permissions in the <code>Target</code> structure. For more information, see <a href=\"https://docs.aws.amazon.com/eventbridge/latest/userguide/eventbridge-cross-account-event-delivery.html\">Sending and Receiving Events Between AWS Accounts</a> in the <i>Amazon EventBridge User Guide</i>.</p>"

apis/events-2015-10-07.min.json

@@ -479,7 +479,7 @@
                 },
                 "Source": {},
                 "Resources": {
-                  "shape": "S37"
+                  "shape": "S3d"
                 },
                 "DetailType": {},
                 "Detail": {},
@@ -526,7 +526,7 @@
                 },
                 "Source": {},
                 "Resources": {
-                  "shape": "S37"
+                  "shape": "S3d"
                 },
                 "DetailType": {},
                 "Detail": {}
@@ -920,6 +920,23 @@
                 "value": {}
               }
             }
+          },
+          "RedshiftDataParameters": {
+            "type": "structure",
+            "required": [
+              "Database",
+              "Sql"
+            ],
+            "members": {
+              "SecretManagerArn": {},
+              "Database": {},
+              "DbUser": {},
+              "Sql": {},
+              "StatementName": {},
+              "WithEvent": {
+                "type": "boolean"
+              }
+            }
           }
         }
       }
@@ -928,7 +945,7 @@
       "type": "list",
       "member": {}
     },
-    "S37": {
+    "S3d": {
       "type": "list",
       "member": {}
     }