Skip to content

Commit

Permalink
Updates SDK to v2.1275.0
Browse files Browse the repository at this point in the history
  • Loading branch information
awstools committed Dec 14, 2022
1 parent 7ba0bd2 commit 3fde1ce
Show file tree
Hide file tree
Showing 23 changed files with 445 additions and 257 deletions.
22 changes: 22 additions & 0 deletions .changes/2.1275.0.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
[
{
"type": "feature",
"category": "CloudWatch",
"description": "Adding support for Metrics Insights Alarms"
},
{
"type": "feature",
"category": "CostExplorer",
"description": "This release supports percentage-based thresholds on Cost Anomaly Detection alert subscriptions."
},
{
"type": "feature",
"category": "NetworkManager",
"description": "Appliance Mode support for AWS Cloud WAN."
},
{
"type": "feature",
"category": "RedshiftData",
"description": "This release adds a new --client-token field to ExecuteStatement and BatchExecuteStatement operations. Customers can now run queries with the additional client token parameter to ensures idempotency."
}
]
8 changes: 7 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,13 @@
# Changelog for AWS SDK for JavaScript
<!--LATEST=2.1274.0-->
<!--LATEST=2.1275.0-->
<!--ENTRYINSERT-->

## 2.1275.0
* feature: CloudWatch: Adding support for Metrics Insights Alarms
* feature: CostExplorer: This release supports percentage-based thresholds on Cost Anomaly Detection alert subscriptions.
* feature: NetworkManager: Appliance Mode support for AWS Cloud WAN.
* feature: RedshiftData: This release adds a new --client-token field to ExecuteStatement and BatchExecuteStatement operations. Customers can now run queries with the additional client token parameter to ensures idempotency.

## 2.1274.0
* feature: CloudTrail: Merging mainline branch for service model into mainline release branch. There are no new APIs.
* feature: RDS: This deployment adds ClientPasswordAuthType field to the Auth structure of the DBProxy.
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ for further details.
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.1274.0.min.js"></script>
<script src="https://sdk.amazonaws.com/js/aws-sdk-2.1275.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
Expand Down
24 changes: 21 additions & 3 deletions apis/ce-2017-10-25.min.json
Original file line number Diff line number Diff line change
Expand Up @@ -289,6 +289,15 @@
},
"TotalImpact": {
"type": "double"
},
"TotalActualSpend": {
"type": "double"
},
"TotalExpectedSpend": {
"type": "double"
},
"TotalImpactPercentage": {
"type": "double"
}
}
},
Expand Down Expand Up @@ -1599,6 +1608,8 @@
"members": {
"SubscriptionArn": {},
"Threshold": {
"deprecated": true,
"deprecatedMessage": "Threshold has been deprecated in favor of ThresholdExpression",
"type": "double"
},
"Frequency": {},
Expand All @@ -1608,7 +1619,10 @@
"Subscribers": {
"shape": "St"
},
"SubscriptionName": {}
"SubscriptionName": {},
"ThresholdExpression": {
"shape": "S7"
}
}
},
"output": {
Expand Down Expand Up @@ -1800,7 +1814,6 @@
"required": [
"MonitorArnList",
"Subscribers",
"Threshold",
"Frequency",
"SubscriptionName"
],
Expand All @@ -1814,10 +1827,15 @@
"shape": "St"
},
"Threshold": {
"deprecated": true,
"deprecatedMessage": "Threshold has been deprecated in favor of ThresholdExpression",
"type": "double"
},
"Frequency": {},
"SubscriptionName": {}
"SubscriptionName": {},
"ThresholdExpression": {
"shape": "S7"
}
}
},
"Sr": {
Expand Down
50 changes: 38 additions & 12 deletions apis/ce-2017-10-25.normal.json

Large diffs are not rendered by default.

60 changes: 33 additions & 27 deletions apis/monitoring-2010-08-01.min.json
Original file line number Diff line number Diff line change
Expand Up @@ -338,7 +338,7 @@
"deprecatedMessage": "Use SingleMetricAnomalyDetector.Stat property."
},
"Configuration": {
"shape": "S2m"
"shape": "S2n"
},
"StateValue": {},
"SingleMetricAnomalyDetector": {
Expand Down Expand Up @@ -660,14 +660,14 @@
},
"StatusCode": {},
"Messages": {
"shape": "S44"
"shape": "S45"
}
}
}
},
"NextToken": {},
"Messages": {
"shape": "S44"
"shape": "S45"
}
}
}
Expand Down Expand Up @@ -777,10 +777,10 @@
"Arn": {},
"Name": {},
"IncludeFilters": {
"shape": "S4i"
"shape": "S4j"
},
"ExcludeFilters": {
"shape": "S4i"
"shape": "S4j"
},
"FirehoseArn": {},
"RoleArn": {},
Expand All @@ -793,7 +793,7 @@
},
"OutputFormat": {},
"StatisticsConfigurations": {
"shape": "S4m"
"shape": "S4n"
}
}
}
Expand Down Expand Up @@ -996,7 +996,7 @@
"type": "structure",
"members": {
"Tags": {
"shape": "S5p"
"shape": "S5q"
}
}
}
Expand All @@ -1023,7 +1023,7 @@
"deprecatedMessage": "Use SingleMetricAnomalyDetector."
},
"Configuration": {
"shape": "S2m"
"shape": "S2n"
},
"SingleMetricAnomalyDetector": {
"shape": "Sc"
Expand Down Expand Up @@ -1063,7 +1063,7 @@
"shape": "S1t"
},
"Tags": {
"shape": "S5p"
"shape": "S5q"
},
"ActionsSuppressor": {},
"ActionsSuppressorWaitPeriod": {
Expand Down Expand Up @@ -1116,7 +1116,7 @@
"RuleState": {},
"RuleDefinition": {},
"Tags": {
"shape": "S5p"
"shape": "S5q"
}
}
},
Expand Down Expand Up @@ -1145,7 +1145,7 @@
"TemplateName": {},
"ResourceARN": {},
"Tags": {
"shape": "S5p"
"shape": "S5q"
}
}
}
Expand Down Expand Up @@ -1212,7 +1212,7 @@
"shape": "Se"
},
"Tags": {
"shape": "S5p"
"shape": "S5q"
},
"ThresholdMetricId": {}
}
Expand Down Expand Up @@ -1302,19 +1302,19 @@
"members": {
"Name": {},
"IncludeFilters": {
"shape": "S4i"
"shape": "S4j"
},
"ExcludeFilters": {
"shape": "S4i"
"shape": "S4j"
},
"FirehoseArn": {},
"RoleArn": {},
"OutputFormat": {},
"Tags": {
"shape": "S5p"
"shape": "S5q"
},
"StatisticsConfigurations": {
"shape": "S4m"
"shape": "S4n"
}
}
},
Expand Down Expand Up @@ -1350,7 +1350,7 @@
],
"members": {
"Names": {
"shape": "S6k"
"shape": "S6l"
}
}
},
Expand All @@ -1368,7 +1368,7 @@
],
"members": {
"Names": {
"shape": "S6k"
"shape": "S6l"
}
}
},
Expand All @@ -1388,7 +1388,7 @@
"members": {
"ResourceARN": {},
"Tags": {
"shape": "S5p"
"shape": "S5q"
}
}
},
Expand Down Expand Up @@ -1595,7 +1595,11 @@
"Metrics": {
"shape": "Se"
},
"ThresholdMetricId": {}
"ThresholdMetricId": {},
"EvaluationState": {},
"StateTransitionedTimestamp": {
"type": "timestamp"
}
},
"xmlOrder": [
"AlarmName",
Expand Down Expand Up @@ -1624,11 +1628,13 @@
"EvaluateLowSampleCountPercentile",
"DatapointsToAlarm",
"Metrics",
"ThresholdMetricId"
"ThresholdMetricId",
"EvaluationState",
"StateTransitionedTimestamp"
]
}
},
"S2m": {
"S2n": {
"type": "structure",
"members": {
"ExcludedTimeRanges": {
Expand Down Expand Up @@ -1656,7 +1662,7 @@
"MetricTimezone": {}
}
},
"S44": {
"S45": {
"type": "list",
"member": {
"type": "structure",
Expand All @@ -1666,7 +1672,7 @@
}
}
},
"S4i": {
"S4j": {
"type": "list",
"member": {
"type": "structure",
Expand All @@ -1675,7 +1681,7 @@
}
}
},
"S4m": {
"S4n": {
"type": "list",
"member": {
"type": "structure",
Expand Down Expand Up @@ -1705,7 +1711,7 @@
}
}
},
"S5p": {
"S5q": {
"type": "list",
"member": {
"type": "structure",
Expand All @@ -1719,7 +1725,7 @@
}
}
},
"S6k": {
"S6l": {
"type": "list",
"member": {}
}
Expand Down
22 changes: 19 additions & 3 deletions apis/monitoring-2010-08-01.normal.json
Original file line number Diff line number Diff line change
Expand Up @@ -719,7 +719,7 @@
"shape": "LimitExceededFault"
}
],
"documentation": "<p>Creates or updates an alarm and associates it with the specified metric, metric math expression, or anomaly detection model.</p> <p>Alarms based on anomaly detection models cannot have Auto Scaling actions.</p> <p>When this operation creates an alarm, the alarm state is immediately set to <code>INSUFFICIENT_DATA</code>. The alarm is then evaluated and its state is set appropriately. Any actions associated with the new state are then executed.</p> <p>When you update an existing alarm, its state is left unchanged, but the update completely overwrites the previous configuration of the alarm.</p> <p>If you are an IAM user, you must have Amazon EC2 permissions for some alarm operations:</p> <ul> <li> <p>The <code>iam:CreateServiceLinkedRole</code> for all alarms with EC2 actions</p> </li> <li> <p>The <code>iam:CreateServiceLinkedRole</code> to create an alarm with Systems Manager OpsItem actions.</p> </li> </ul> <p>The first time you create an alarm in the Amazon Web Services Management Console, the CLI, or by using the PutMetricAlarm API, CloudWatch creates the necessary service-linked role for you. The service-linked roles are called <code>AWSServiceRoleForCloudWatchEvents</code> and <code>AWSServiceRoleForCloudWatchAlarms_ActionSSM</code>. For more information, see <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role\">Amazon Web Services service-linked role</a>.</p> <p> <b>Cross-account alarms</b> </p> <p>You can set an alarm on metrics in the current account, or in another account. To create a cross-account alarm that watches a metric in a different account, you must have completed the following pre-requisites:</p> <ul> <li> <p>The account where the metrics are located (the <i>sharing account</i>) must already have a sharing role named <b>CloudWatch-CrossAccountSharingRole</b>. If it does not already have this role, you must create it using the instructions in <b>Set up a sharing account</b> in <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Cross-Account-Cross-Region.html#enable-cross-account-cross-Region\"> Cross-account cross-Region CloudWatch console</a>. The policy for that role must grant access to the ID of the account where you are creating the alarm. </p> </li> <li> <p>The account where you are creating the alarm (the <i>monitoring account</i>) must already have a service-linked role named <b>AWSServiceRoleForCloudWatchCrossAccount</b> to allow CloudWatch to assume the sharing role in the sharing account. If it does not, you must create it following the directions in <b>Set up a monitoring account</b> in <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Cross-Account-Cross-Region.html#enable-cross-account-cross-Region\"> Cross-account cross-Region CloudWatch console</a>.</p> </li> </ul>"
"documentation": "<p>Creates or updates an alarm and associates it with the specified metric, metric math expression, anomaly detection model, or Metrics Insights query. For more information about using a Metrics Insights query for an alarm, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create_Metrics_Insights_Alarm.html\">Create alarms on Metrics Insights queries</a>.</p> <p>Alarms based on anomaly detection models cannot have Auto Scaling actions.</p> <p>When this operation creates an alarm, the alarm state is immediately set to <code>INSUFFICIENT_DATA</code>. The alarm is then evaluated and its state is set appropriately. Any actions associated with the new state are then executed.</p> <p>When you update an existing alarm, its state is left unchanged, but the update completely overwrites the previous configuration of the alarm.</p> <p>If you are an IAM user, you must have Amazon EC2 permissions for some alarm operations:</p> <ul> <li> <p>The <code>iam:CreateServiceLinkedRole</code> for all alarms with EC2 actions</p> </li> <li> <p>The <code>iam:CreateServiceLinkedRole</code> to create an alarm with Systems Manager OpsItem actions.</p> </li> </ul> <p>The first time you create an alarm in the Amazon Web Services Management Console, the CLI, or by using the PutMetricAlarm API, CloudWatch creates the necessary service-linked role for you. The service-linked roles are called <code>AWSServiceRoleForCloudWatchEvents</code> and <code>AWSServiceRoleForCloudWatchAlarms_ActionSSM</code>. For more information, see <a href=\"https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html#iam-term-service-linked-role\">Amazon Web Services service-linked role</a>.</p> <p> <b>Cross-account alarms</b> </p> <p>You can set an alarm on metrics in the current account, or in another account. To create a cross-account alarm that watches a metric in a different account, you must have completed the following pre-requisites:</p> <ul> <li> <p>The account where the metrics are located (the <i>sharing account</i>) must already have a sharing role named <b>CloudWatch-CrossAccountSharingRole</b>. If it does not already have this role, you must create it using the instructions in <b>Set up a sharing account</b> in <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Cross-Account-Cross-Region.html#enable-cross-account-cross-Region\"> Cross-account cross-Region CloudWatch console</a>. The policy for that role must grant access to the ID of the account where you are creating the alarm. </p> </li> <li> <p>The account where you are creating the alarm (the <i>monitoring account</i>) must already have a service-linked role named <b>AWSServiceRoleForCloudWatchCrossAccount</b> to allow CloudWatch to assume the sharing role in the sharing account. If it does not, you must create it following the directions in <b>Set up a monitoring account</b> in <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Cross-Account-Cross-Region.html#enable-cross-account-cross-Region\"> Cross-account cross-Region CloudWatch console</a>.</p> </li> </ul>"
},
"PutMetricData": {
"name": "PutMetricData",
Expand Down Expand Up @@ -1869,6 +1869,12 @@
"type": "integer",
"min": 1
},
"EvaluationState": {
"type": "string",
"enum": [
"PARTIAL_DATA"
]
},
"ExceptionType": {
"type": "string"
},
Expand Down Expand Up @@ -2792,7 +2798,7 @@
},
"StateUpdatedTimestamp": {
"shape": "Timestamp",
"documentation": "<p>The time stamp of the last update to the alarm state.</p>"
"documentation": "<p>The time stamp of the last update to the value of either the <code>StateValue</code> or <code>EvaluationState</code> parameters.</p>"
},
"MetricName": {
"shape": "MetricName",
Expand Down Expand Up @@ -2853,6 +2859,14 @@
"ThresholdMetricId": {
"shape": "MetricId",
"documentation": "<p>In an alarm based on an anomaly detection model, this is the ID of the <code>ANOMALY_DETECTION_BAND</code> function used as the threshold for the alarm.</p>"
},
"EvaluationState": {
"shape": "EvaluationState",
"documentation": "<p>If the value of this field is <code>PARTIAL_DATA</code>, the alarm is being evaluated based on only partial data. This happens if the query used for the alarm returns more than 10,000 metrics. For more information, see <a href=\"https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Create_Metrics_Insights_Alarm.html\">Create alarms on Metrics Insights queries</a>.</p>"
},
"StateTransitionedTimestamp": {
"shape": "Timestamp",
"documentation": "<p>The date and time that the alarm's <code>StateValue</code> most recently changed.</p>"
}
},
"documentation": "<p>The details about a metric alarm.</p>",
Expand Down Expand Up @@ -2883,7 +2897,9 @@
"EvaluateLowSampleCountPercentile",
"DatapointsToAlarm",
"Metrics",
"ThresholdMetricId"
"ThresholdMetricId",
"EvaluationState",
"StateTransitionedTimestamp"
]
},
"MetricAlarms": {
Expand Down
Loading

0 comments on commit 3fde1ce

Please sign in to comment.