From fb245b6ceafc2032d397838aa9a97a16ed6c1c94 Mon Sep 17 00:00:00 2001 From: AWS SDK for Go v2 automation user Date: Wed, 13 Apr 2022 18:03:30 +0000 Subject: [PATCH] Update API model --- .../sdk-codegen/aws-models/cloudwatch.json | 97 +++++++++++++++++-- codegen/sdk-codegen/aws-models/fsx.json | 22 +++-- 2 files changed, 100 insertions(+), 19 deletions(-) diff --git a/codegen/sdk-codegen/aws-models/cloudwatch.json b/codegen/sdk-codegen/aws-models/cloudwatch.json index 230a6a986e3..746a63d4042 100644 --- a/codegen/sdk-codegen/aws-models/cloudwatch.json +++ b/codegen/sdk-codegen/aws-models/cloudwatch.json @@ -1412,7 +1412,7 @@ "Name": { "target": "com.amazonaws.cloudwatch#DimensionName", "traits": { - "smithy.api#documentation": "

The name of the dimension. Dimension names must contain only ASCII characters and must include \n\t\t\tat least one non-whitespace character.

", + "smithy.api#documentation": "

The name of the dimension. Dimension names must contain only ASCII characters, must include \n\t\t\tat least one non-whitespace character, and cannot start with a colon (:).

", "smithy.api#required": {} } }, @@ -1425,7 +1425,7 @@ } }, "traits": { - "smithy.api#documentation": "

A dimension is a name/value pair that is part of the identity of a metric. You \n\t\t\tcan assign up to 10 dimensions to a metric. Because dimensions are part of the unique \n\t\t\tidentifier for a metric, whenever you add a unique name/value pair to one of \n\t\t\tyour metrics, you are creating a new variation of that metric.

" + "smithy.api#documentation": "

A dimension is a name/value pair that is part of the identity of a metric. Because dimensions are part of the unique \n\t\t\tidentifier for a metric, whenever you add a unique name/value pair to one of \n\t\t\tyour metrics, you are creating a new variation of that metric. For example, many Amazon EC2 metrics publish\n\t\tInstanceId as a dimension name, and the actual instance ID as the value for that dimension.

\n\t\t

You \n\t\tcan assign up to 10 dimensions to a metric.

" } }, "com.amazonaws.cloudwatch#DimensionFilter": { @@ -1869,7 +1869,7 @@ } ], "traits": { - "smithy.api#documentation": "

You can use the GetMetricData API to retrieve as many as 500 different\n\t\t\tmetrics in a single request, with a total of as many as 100,800 data points. You can also\n\t\t\toptionally perform math expressions on the values of the returned statistics, to create\n\t\t\tnew time series that represent new insights into your data. For example, using Lambda\n\t\t\tmetrics, you could divide the Errors metric by the Invocations metric to get an error\n\t\t\trate time series. For more information about metric math expressions, see Metric Math Syntax and Functions in the Amazon CloudWatch User\n\t\t\t\tGuide.

\n\t\t\n\t\t

Calls to the GetMetricData API have a different pricing structure than \n\t\t\tcalls to GetMetricStatistics. For more information about pricing, see \n\t\t\tAmazon CloudWatch Pricing.

\n\n\t\t

Amazon CloudWatch retains metric data as follows:

\n\t\t \n\t\t

Data points that are initially published with a shorter period are aggregated together for long-term storage. For example, if you collect \n\t\t\tdata using a period of 1 minute, the data remains available for 15 days with 1-minute resolution. After 15 days, this data is still available, \n\t\t\tbut is aggregated and retrievable only with a resolution of 5 minutes. After 63 days, the data is further aggregated and is available with \n\t\t\ta resolution of 1 hour.

\n\t\t\n\t\t

If you omit Unit in your request, all data that was collected with any unit is returned, along with the corresponding units that were specified\n\t\t\twhen the data was reported to CloudWatch. If you specify a unit, the operation returns only data that was collected with that unit specified.\n\t\t\tIf you specify a unit that does not match the data collected, the results of the operation are null. CloudWatch does not perform unit conversions.

", + "smithy.api#documentation": "

You can use the GetMetricData API to retrieve CloudWatch metric values. The operation \n\t\t\tcan also include a CloudWatch Metrics Insights query, and one or more metric math functions.

\n\t\t

A GetMetricData operation that does not include a query can retrieve as many as 500 different\n\t\t\tmetrics in a single request, with a total of as many as 100,800 data points. You can also\n\t\t\toptionally perform metric math expressions on the values of the returned statistics, to create\n\t\t\tnew time series that represent new insights into your data. For example, using Lambda\n\t\t\tmetrics, you could divide the Errors metric by the Invocations metric to get an error\n\t\t\trate time series. For more information about metric math expressions, see Metric Math Syntax and Functions in the Amazon CloudWatch User\n\t\t\t\t\tGuide.

\n\t\t\n\t\t\t\t\n\t\t

If you include a Metrics Insights query, each GetMetricData operation can include only one\n\t\t\tquery. But the same GetMetricData operation can also retrieve other metrics. Metrics Insights queries\n\t\tcan query only the most recent three hours of metric data. For more information about Metrics Insights, \n\t\tsee Query your metrics with CloudWatch Metrics Insights.

\n\t\t\n\t\t

Calls to the GetMetricData API have a different pricing structure than \n\t\t\tcalls to GetMetricStatistics. For more information about pricing, see \n\t\t\tAmazon CloudWatch Pricing.

\n\n\t\t

Amazon CloudWatch retains metric data as follows:

\n\t\t \n\t\t

Data points that are initially published with a shorter period are aggregated together for long-term storage. For example, if you collect \n\t\t\tdata using a period of 1 minute, the data remains available for 15 days with 1-minute resolution. After 15 days, this data is still available, \n\t\t\tbut is aggregated and retrievable only with a resolution of 5 minutes. After 63 days, the data is further aggregated and is available with \n\t\t\ta resolution of 1 hour.

\n\t\t\n\t\t

If you omit Unit in your request, all data that was collected with any unit is returned, along with the corresponding units that were specified\n\t\t\twhen the data was reported to CloudWatch. If you specify a unit, the operation returns only data that was collected with that unit specified.\n\t\t\tIf you specify a unit that does not match the data collected, the results of the operation are null. CloudWatch does not perform unit conversions.

\n\t\n\t\t

\n Using Metrics Insights queries with metric math\n

\n\t\t

You can't mix a Metric Insights query and metric math syntax in the same expression, but \n\t\t\tyou can reference results from a Metrics Insights query within other Metric math expressions. A Metrics Insights \n\t\t\tquery without a GROUP BY clause returns a single time-series (TS), \n\t\t\tand can be used as input for a metric math expression that expects a single time series. A Metrics Insights \n\t\t\tquery with a GROUP BY clause returns an array of time-series (TS[]), \n\t\t\tand can be used as input for a metric math expression that expects an array of time series.

", "smithy.api#paginated": { "inputToken": "NextToken", "outputToken": "NextToken", @@ -1883,7 +1883,7 @@ "MetricDataQueries": { "target": "com.amazonaws.cloudwatch#MetricDataQueries", "traits": { - "smithy.api#documentation": "

The metric queries to be returned. A single GetMetricData call can include as many as 500 MetricDataQuery\n\t\tstructures. Each of these structures can specify either a metric to retrieve, or a math expression to perform on retrieved data.

", + "smithy.api#documentation": "

The metric queries to be returned. A single GetMetricData call can include as many as 500 MetricDataQuery\n\t\tstructures. Each of these structures can specify either a metric to retrieve, a Metrics Insights query,\n\t\tor a math expression to perform on retrieved data.

", "smithy.api#required": {} } }, @@ -2167,7 +2167,13 @@ "OutputFormat": { "target": "com.amazonaws.cloudwatch#MetricStreamOutputFormat", "traits": { - "smithy.api#documentation": "

" + "smithy.api#documentation": "

The output format for the stream. Valid values are json\n\t\t\tand opentelemetry0.7. For more information about metric stream\n\t\t\toutput formats, see \n\t\t\t\n\t\t\t\tMetric streams output formats.

" + } + }, + "StatisticsConfigurations": { + "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsConfigurations", + "traits": { + "smithy.api#documentation": "

Each entry in this array displays information about one or more metrics that include extended statistics\n\t\t\tin the metric stream. For more information about extended statistics, see \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions.

" } } } @@ -3293,7 +3299,7 @@ "TreatMissingData": { "target": "com.amazonaws.cloudwatch#TreatMissingData", "traits": { - "smithy.api#documentation": "

Sets how this alarm is to handle missing data points. If this parameter is omitted, the default behavior of missing is used.

" + "smithy.api#documentation": "

Sets how this alarm is to handle missing data points. The valid values\n \tare breaching, notBreaching, ignore, and \n \tmissing. For more information, see\n \tConfiguring how CloudWatch alarms treat missing data.

\n\t\t

If this parameter is omitted, the default \n \tbehavior of missing is used.

" } }, "EvaluateLowSampleCountPercentile": { @@ -3356,7 +3362,7 @@ "Expression": { "target": "com.amazonaws.cloudwatch#MetricExpression", "traits": { - "smithy.api#documentation": "

The math expression to be performed on the returned data, if this object is performing a math expression. This expression\n\t\t\tcan use the Id of the other metrics to refer to those metrics, and can also use the Id of other \n\t\t\texpressions to use the result of those expressions. For more information about metric math expressions, see \n\t\t\tMetric Math Syntax and Functions in the\n\t\t\tAmazon CloudWatch User Guide.

\n\t\t

Within each MetricDataQuery object, you must specify either \n\t\t\tExpression or MetricStat but not both.

" + "smithy.api#documentation": "

This field can contain either a Metrics Insights query, or a metric math expression to be performed on the \n\t\t\treturned data. For more information about Metrics Insights queries, see \n\t\t\tMetrics Insights query components and syntax in the\n\t\t\tAmazon CloudWatch User Guide.

\n\t\t

A math expression\n\t\t\tcan use the Id of the other metrics or queries to refer to those metrics, and can also use \n\t\t\tthe Id of other \n\t\t\texpressions to use the result of those expressions. For more information about metric math expressions, see \n\t\t\tMetric Math Syntax and Functions in the\n\t\t\tAmazon CloudWatch User Guide.

\n\t\t

Within each MetricDataQuery object, you must specify either \n\t\t\tExpression or MetricStat but not both.

" } }, "Label": { @@ -3385,7 +3391,7 @@ } }, "traits": { - "smithy.api#documentation": "

This structure is used in both GetMetricData and PutMetricAlarm. The supported\n\t\t\tuse of this structure is different for those two operations.

\n\t\t

When used in GetMetricData, it indicates the metric data to return, and whether this call is just retrieving\n\t\t\ta batch set of data for one metric, or is performing a math expression on metric data. A\n\t\t\tsingle GetMetricData call can include up to 500 MetricDataQuery\n\t\t\tstructures.

\n\t\t

When used in PutMetricAlarm, it enables you to create an alarm based on a\n\t\t\tmetric math expression. Each MetricDataQuery in the array specifies either\n\t\t\ta metric to retrieve, or a math expression to be performed on retrieved metrics. A\n\t\t\tsingle PutMetricAlarm call can include up to 20\n\t\t\t\tMetricDataQuery structures in the array. The 20 structures can include\n\t\t\tas many as 10 structures that contain a MetricStat parameter to retrieve a\n\t\t\tmetric, and as many as 10 structures that contain the Expression parameter\n\t\t\tto perform a math expression. Of those Expression structures, one must have True\n\t\tas the value for ReturnData. The result of this expression is the value the alarm watches.

\n\n\t\t

Any expression used in a PutMetricAlarm\n\t\t\toperation must return a single time series. For more information, see Metric Math Syntax and Functions in the Amazon CloudWatch User\n\t\t\t\tGuide.

\n\n\t\t

Some of the parameters of this structure also have different uses whether you are using this structure in a GetMetricData\n\t\t\toperation or a PutMetricAlarm operation. These differences are explained in the following parameter list.

" + "smithy.api#documentation": "

This structure is used in both GetMetricData and PutMetricAlarm. The supported\n\t\t\tuse of this structure is different for those two operations.

\n\t\t

When used in GetMetricData, it indicates the metric data to return, and whether this call is just retrieving\n\t\t\ta batch set of data for one metric, or is performing a Metrics Insights query or a math expression. A\n\t\t\tsingle GetMetricData call can include up to 500 MetricDataQuery\n\t\t\tstructures.

\n\t\t

When used in PutMetricAlarm, it enables you to create an alarm based on a\n\t\t\tmetric math expression. Each MetricDataQuery in the array specifies either\n\t\t\ta metric to retrieve, or a math expression to be performed on retrieved metrics. A\n\t\t\tsingle PutMetricAlarm call can include up to 20\n\t\t\t\tMetricDataQuery structures in the array. The 20 structures can include\n\t\t\tas many as 10 structures that contain a MetricStat parameter to retrieve a\n\t\t\tmetric, and as many as 10 structures that contain the Expression parameter\n\t\t\tto perform a math expression. Of those Expression structures, one must have True\n\t\tas the value for ReturnData. The result of this expression is the value the alarm watches.

\n\n\t\t

Any expression used in a PutMetricAlarm\n\t\t\toperation must return a single time series. For more information, see Metric Math Syntax and Functions in the Amazon CloudWatch User\n\t\t\t\tGuide.

\n\n\t\t

Some of the parameters of this structure also have different uses whether you are using this structure in a GetMetricData\n\t\t\toperation or a PutMetricAlarm operation. These differences are explained in the following parameter list.

" } }, "com.amazonaws.cloudwatch#MetricDataResult": { @@ -3699,6 +3705,71 @@ "com.amazonaws.cloudwatch#MetricStreamState": { "type": "string" }, + "com.amazonaws.cloudwatch#MetricStreamStatistic": { + "type": "string" + }, + "com.amazonaws.cloudwatch#MetricStreamStatisticsAdditionalStatistics": { + "type": "list", + "member": { + "target": "com.amazonaws.cloudwatch#MetricStreamStatistic" + } + }, + "com.amazonaws.cloudwatch#MetricStreamStatisticsConfiguration": { + "type": "structure", + "members": { + "IncludeMetrics": { + "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsIncludeMetrics", + "traits": { + "smithy.api#documentation": "

An array of metric name and namespace pairs that stream the extended statistics listed\n\t\tin the value of the AdditionalStatistics parameter. There can be as many as \n\t\t100 pairs in the array.

\n\t\t

All metrics that match the combination of metric name and namespace will be streamed\n\t\twith the extended statistics, no matter their dimensions.

", + "smithy.api#required": {} + } + }, + "AdditionalStatistics": { + "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsAdditionalStatistics", + "traits": { + "smithy.api#documentation": "

The list of extended statistics that are to be streamed for the metrics listed\n\t\tin the IncludeMetrics array in this structure. This list can include as many as 20 statistics.

\n\t\t

If the OutputFormat for the stream is opentelemetry0.7, the only \n\t\t\tvalid values are p??\n percentile statistics such as p90, p99 and so on.

\n\t\t

If the OutputFormat for the stream is json, \n\t\t\tthe valid values are include the abbreviations for all of the extended statistics listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions. For example, this includes\n\t\ttm98, \n wm90, PR(:300), and so on.

", + "smithy.api#required": {} + } + } + }, + "traits": { + "smithy.api#documentation": "

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. This structure contains information for\n\t\t\tone metric that includes extended statistics in the stream. For more information about extended statistics, \n\t\t\tsee CloudWatch, listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions.

" + } + }, + "com.amazonaws.cloudwatch#MetricStreamStatisticsConfigurations": { + "type": "list", + "member": { + "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsConfiguration" + } + }, + "com.amazonaws.cloudwatch#MetricStreamStatisticsIncludeMetrics": { + "type": "list", + "member": { + "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsMetric" + } + }, + "com.amazonaws.cloudwatch#MetricStreamStatisticsMetric": { + "type": "structure", + "members": { + "Namespace": { + "target": "com.amazonaws.cloudwatch#Namespace", + "traits": { + "smithy.api#documentation": "

The metric namespace for the metric.

", + "smithy.api#required": {} + } + }, + "MetricName": { + "target": "com.amazonaws.cloudwatch#MetricName", + "traits": { + "smithy.api#documentation": "

The name of the metric.

", + "smithy.api#required": {} + } + } + }, + "traits": { + "smithy.api#documentation": "

This object contains the information for one metric that is to streamed with \n\t\textended statistics.

" + } + }, "com.amazonaws.cloudwatch#MetricWidget": { "type": "string" }, @@ -3891,7 +3962,7 @@ } ], "traits": { - "smithy.api#documentation": "

Creates or updates a composite alarm. When you create a composite\n\t\t\talarm, you specify a rule expression for the alarm that takes into account the alarm\n\t\t\tstates of other alarms that you have created. The composite alarm goes into ALARM state\n\t\t\tonly if all conditions of the rule are met.

\n\t\t

The alarms specified in a composite alarm's rule expression can include metric alarms\n\t\t\tand other composite alarms.

\n\t\t

Using composite alarms can reduce\n\t\t\talarm noise. You can create multiple metric alarms,\n\t\t\tand also create a composite alarm and\n\t\t\tset up alerts only\n\t\t\tfor the composite alarm. For example, you could create a composite\n\t\t\talarm that goes into ALARM state only when more than one of the underlying metric alarms\n\t\t\tare in ALARM state.

\n\t\t

Currently, the only alarm actions that can be taken by composite alarms are notifying\n\t\t\tSNS topics.

\n\t\t \n

It is possible to create a loop or cycle of composite alarms, where composite alarm A depends on composite alarm B, and \n\t\t\tcomposite alarm B also depends on composite alarm A. In this scenario, you can't delete any composite alarm that is part of the cycle \n\t\t\tbecause there is always still a composite alarm that depends on that alarm that you want to delete.

\n\t\t\t

To get out of such a situation, you must\n\t\t\tbreak the cycle by changing the rule of one of the composite alarms in the cycle to remove a dependency that creates the cycle. The simplest\n\t\t\tchange to make to break a cycle is to change the AlarmRule of one of the alarms to False.

\n\t\t\t

Additionally, the evaluation of composite alarms stops if CloudWatch detects a cycle in the evaluation path.\n\t\t

\n \n\t\t

When this operation creates an alarm, the alarm state is immediately set to\n\t\t\t\tINSUFFICIENT_DATA. The alarm is then evaluated and its state is set\n\t\t\tappropriately. Any actions associated with the new state are then executed. For a\n\t\t\tcomposite alarm, this initial time after creation is the only time that\n\t\t\tthe\n\t\t\talarm can be in INSUFFICIENT_DATA state.

\n\t\t

When you update an existing alarm, its state is left unchanged, but the update\n\t\t\tcompletely overwrites the previous configuration of the alarm.

\n\t\t\n\t\t

To use this operation, you must be signed on with \n\t\t\tthe cloudwatch:PutCompositeAlarm permission that is scoped to *. You can't create a\n\t\t\tcomposite alarms if your cloudwatch:PutCompositeAlarm permission has a narrower scope.

\n\t\t\n\t\t

If you are an IAM user, you must have iam:CreateServiceLinkedRole to create\n\t\t\ta composite alarm that has Systems Manager OpsItem actions.

" + "smithy.api#documentation": "

Creates or updates a composite alarm. When you create a composite\n\t\t\talarm, you specify a rule expression for the alarm that takes into account the alarm\n\t\t\tstates of other alarms that you have created. The composite alarm goes into ALARM state\n\t\t\tonly if all conditions of the rule are met.

\n\t\t

The alarms specified in a composite alarm's rule expression can include metric alarms\n\t\t\tand other composite alarms. The rule expression of a composite alarm can include as many as 100 underlying alarms. \n\t\t\tAny single alarm can be included in the rule expressions of as many as 150 composite alarms.

\n\t\t

Using composite alarms can reduce\n\t\t\talarm noise. You can create multiple metric alarms,\n\t\t\tand also create a composite alarm and\n\t\t\tset up alerts only\n\t\t\tfor the composite alarm. For example, you could create a composite\n\t\t\talarm that goes into ALARM state only when more than one of the underlying metric alarms\n\t\t\tare in ALARM state.

\n\t\t

Currently, the only alarm actions that can be taken by composite alarms are notifying\n\t\t\tSNS topics.

\n\t\t \n

It is possible to create a loop or cycle of composite alarms, where composite alarm A depends on composite alarm B, and \n\t\t\tcomposite alarm B also depends on composite alarm A. In this scenario, you can't delete any composite alarm that is part of the cycle \n\t\t\tbecause there is always still a composite alarm that depends on that alarm that you want to delete.

\n\t\t\t

To get out of such a situation, you must\n\t\t\tbreak the cycle by changing the rule of one of the composite alarms in the cycle to remove a dependency that creates the cycle. The simplest\n\t\t\tchange to make to break a cycle is to change the AlarmRule of one of the alarms to False.

\n\t\t\t

Additionally, the evaluation of composite alarms stops if CloudWatch detects a cycle in the evaluation path.\n\t\t

\n \n\t\t

When this operation creates an alarm, the alarm state is immediately set to\n\t\t\t\tINSUFFICIENT_DATA. The alarm is then evaluated and its state is set\n\t\t\tappropriately. Any actions associated with the new state are then executed. For a\n\t\t\tcomposite alarm, this initial time after creation is the only time that\n\t\t\tthe\n\t\t\talarm can be in INSUFFICIENT_DATA state.

\n\t\t

When you update an existing alarm, its state is left unchanged, but the update\n\t\t\tcompletely overwrites the previous configuration of the alarm.

\n\t\t\n\t\t

To use this operation, you must be signed on with \n\t\t\tthe cloudwatch:PutCompositeAlarm permission that is scoped to *. You can't create a\n\t\t\tcomposite alarms if your cloudwatch:PutCompositeAlarm permission has a narrower scope.

\n\t\t\n\t\t

If you are an IAM user, you must have iam:CreateServiceLinkedRole to create\n\t\t\ta composite alarm that has Systems Manager OpsItem actions.

" } }, "com.amazonaws.cloudwatch#PutCompositeAlarmInput": { @@ -4279,7 +4350,7 @@ } ], "traits": { - "smithy.api#documentation": "

Creates or updates a metric stream. Metric streams can automatically stream CloudWatch metrics \n\t\t\tto Amazon Web Services destinations including\n\t\t\tAmazon S3 and to many third-party solutions.

\n\t\t

For more information, see \n\t\tUsing Metric Streams.

\n\t\t

To create a metric stream, \n\t\t\tyou must be logged on to an account that has the iam:PassRole permission\n\t\t\tand either the CloudWatchFullAccess\n\t\tpolicy or the cloudwatch:PutMetricStream \n\t\tpermission.

\n\t\t

When you create or update a metric stream, you choose one of the following:

\n\t\t \n\t\t\n\t\t

When you use PutMetricStream to create a new metric stream, the stream \n\t\tis created in the running state. If you use it to update an existing stream, \n\t\tthe state of the stream is not changed.

" + "smithy.api#documentation": "

Creates or updates a metric stream. Metric streams can automatically stream CloudWatch metrics \n\t\t\tto Amazon Web Services destinations including\n\t\t\tAmazon S3 and to many third-party solutions.

\n\t\t

For more information, see \n\t\tUsing Metric Streams.

\n\t\t

To create a metric stream, \n\t\t\tyou must be logged on to an account that has the iam:PassRole permission\n\t\t\tand either the CloudWatchFullAccess\n\t\tpolicy or the cloudwatch:PutMetricStream \n\t\tpermission.

\n\t\t

When you create or update a metric stream, you choose one of the following:

\n\t\t \n\t\t\n\t\t

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. You can use the\n\t\t\tStatisticsConfigurations parameter to have \n\t\t\tthe metric stream also send extended statistics in the stream. Streaming extended statistics incurs\n\t\t\tadditional costs. For more information, see Amazon CloudWatch Pricing.

\n\t\t\n\t\t

When you use PutMetricStream to create a new metric stream, the stream \n\t\tis created in the running state. If you use it to update an existing stream, \n\t\tthe state of the stream is not changed.

" } }, "com.amazonaws.cloudwatch#PutMetricStreamInput": { @@ -4330,6 +4401,12 @@ "traits": { "smithy.api#documentation": "

A list of key-value pairs to associate with the metric stream. You can associate as \n\t\t\tmany as 50 tags with a metric stream.

\n\t\t

Tags can help you organize and categorize your resources. You can also use them to scope user\n\t\t\tpermissions by granting a user\n\t\t\tpermission to access or change only resources with certain tag values.

\n\t\t

You can use this parameter only when you are creating a new metric stream. If you are using this operation to update an existing metric stream, any tags\n\t\t\tyou specify in this parameter are ignored. To change the tags of an existing metric stream, use\n\t\t\tTagResource\n\t\t\tor UntagResource.

" } + }, + "StatisticsConfigurations": { + "target": "com.amazonaws.cloudwatch#MetricStreamStatisticsConfigurations", + "traits": { + "smithy.api#documentation": "

By default, a metric stream always sends the MAX, MIN, SUM, \n\t\t\tand SAMPLECOUNT statistics for each metric that is streamed. You can use this parameter to have \n\t\t\tthe metric stream also send extended statistics in the stream. This \n\t\t\tarray can have up to 100 members.

\n\t\t

For each entry in this array, you specify one or more metrics and the list of extended statistics to stream\n\t\t\tfor those metrics. The extended statistics that you can stream depend on the stream's OutputFormat.\n\t\t\tIf the OutputFormat is json, you can stream any extended statistic that is supported \n\t\t\tby CloudWatch, listed in \n\t\t\t\n\t\t\t\tCloudWatch statistics definitions. If the OutputFormat is \n\t\t\topentelemetry0.7, you can stream percentile statistics (p??).

" + } } } }, diff --git a/codegen/sdk-codegen/aws-models/fsx.json b/codegen/sdk-codegen/aws-models/fsx.json index 071d7dbb54e..95d1d84a198 100644 --- a/codegen/sdk-codegen/aws-models/fsx.json +++ b/codegen/sdk-codegen/aws-models/fsx.json @@ -1607,14 +1607,14 @@ "DeploymentType": { "target": "com.amazonaws.fsx#OntapDeploymentType", "traits": { - "smithy.api#documentation": "

Specifies the FSx for ONTAP file system deployment type to use in creating the file system. \n MULTI_AZ_1 is the supported ONTAP deployment type.

", + "smithy.api#documentation": "

Specifies the FSx for ONTAP file system deployment type to use in creating\n the file system.

\n \n

For information about the use cases for Multi-AZ and Single-AZ deployments, refer to\n Choosing Multi-AZ or\n Single-AZ file system deployment.

", "smithy.api#required": {} } }, "EndpointIpAddressRange": { "target": "com.amazonaws.fsx#IpAddressRange", "traits": { - "smithy.api#documentation": "

Specifies the IP address range in which the endpoints to access your file system\n will be created. By default, Amazon FSx selects an unused IP address range for you\n from the 198.19.* range.

\n \n

The Endpoint IP address range you select for your file system\n must exist outside the VPC's CIDR range and must be at least /30 or larger.

\n " + "smithy.api#documentation": "

(Multi-AZ only) Specifies the IP address range in which the endpoints to access your\n file system will be created. By default, Amazon FSx selects an unused IP address\n range for you from the 198.19.* range.

\n \n

The Endpoint IP address range you select for your file system must exist outside\n the VPC's CIDR range and must be at least /30 or larger.

\n " } }, "FsxAdminPassword": { @@ -1632,19 +1632,19 @@ "PreferredSubnetId": { "target": "com.amazonaws.fsx#SubnetId", "traits": { - "smithy.api#documentation": "

Required when DeploymentType is set to MULTI_AZ_1. This specifies the subnet \n in which you want the preferred file server to be located.

" + "smithy.api#documentation": "

Required when DeploymentType is set to MULTI_AZ_1. This\n specifies the subnet in which you want the preferred file server to be located.

" } }, "RouteTableIds": { "target": "com.amazonaws.fsx#RouteTableIds", "traits": { - "smithy.api#documentation": "

Specifies the virtual private cloud (VPC) route tables in which your file system's\n endpoints will be created. You should specify all VPC route tables associated with the\n subnets in which your clients are located. By default, Amazon FSx selects your VPC's\n default route table.

" + "smithy.api#documentation": "

(Multi-AZ only) Specifies the virtual private cloud (VPC) route tables in which your\n file system's endpoints will be created. You should specify all VPC route tables\n associated with the subnets in which your clients are located. By default, Amazon FSx\n selects your VPC's default route table.

" } }, "ThroughputCapacity": { "target": "com.amazonaws.fsx#MegabytesPerSecond", "traits": { - "smithy.api#documentation": "

Sets the throughput capacity for the file system that you're creating. \n Valid values are 128, 256, 512, 1024, and 2048 MBps.

", + "smithy.api#documentation": "

Sets the throughput capacity for the file system that you're creating. Valid values\n are 128, 256, 512, 1024, and 2048 MBps.

", "smithy.api#required": {} } }, @@ -1653,7 +1653,7 @@ } }, "traits": { - "smithy.api#documentation": "

The ONTAP configuration properties of the FSx for ONTAP file system that you are creating.

" + "smithy.api#documentation": "

The ONTAP configuration properties of the FSx for ONTAP file system that you\n are creating.

" } }, "com.amazonaws.fsx#CreateFileSystemOpenZFSConfiguration": { @@ -5460,6 +5460,10 @@ { "value": "MULTI_AZ_1", "name": "MULTI_AZ_1" + }, + { + "value": "SINGLE_AZ_1", + "name": "SINGLE_AZ_1" } ] } @@ -5488,13 +5492,13 @@ "DeploymentType": { "target": "com.amazonaws.fsx#OntapDeploymentType", "traits": { - "smithy.api#documentation": "

The ONTAP file system deployment type.

" + "smithy.api#documentation": "

Specifies the FSx for ONTAP file system deployment type in use in the file\n system.

\n \n

For information about the use cases for Multi-AZ and Single-AZ deployments, refer to\n Choosing Multi-AZ or\n Single-AZ file system deployment.

" } }, "EndpointIpAddressRange": { "target": "com.amazonaws.fsx#IpAddressRange", "traits": { - "smithy.api#documentation": "

The IP address range in which the endpoints to access your file system\n are created.

\n \n

The Endpoint IP address range you select for your file system\n must exist outside the VPC's CIDR range and must be at least /30 or larger.\n If you do not specify this optional parameter, Amazon FSx will automatically\n select a CIDR block for you.

\n " + "smithy.api#documentation": "

(Multi-AZ only) The IP address range in which the endpoints to access your file system\n are created.

\n \n

The Endpoint IP address range you select for your file system\n must exist outside the VPC's CIDR range and must be at least /30 or larger.\n If you do not specify this optional parameter, Amazon FSx will automatically\n select a CIDR block for you.

\n " } }, "Endpoints": { @@ -5515,7 +5519,7 @@ "RouteTableIds": { "target": "com.amazonaws.fsx#RouteTableIds", "traits": { - "smithy.api#documentation": "

The VPC route tables in which your file system's endpoints are\n created.

" + "smithy.api#documentation": "

(Multi-AZ only) The VPC route tables in which your file system's endpoints are\n created.

" } }, "ThroughputCapacity": {