From ca190b054e7a07bcde270356ffe0ad06fd722ccc Mon Sep 17 00:00:00 2001 From: AWS SDK for Go v2 automation user Date: Fri, 23 Feb 2024 19:09:36 +0000 Subject: [PATCH] Update API model --- codegen/sdk-codegen/aws-models/appsync.json | 10 ++-- codegen/sdk-codegen/aws-models/qldb.json | 44 ++++++++-------- codegen/sdk-codegen/aws-models/rds.json | 20 +++++-- codegen/sdk-codegen/aws-models/rum.json | 58 ++++++++++----------- 4 files changed, 71 insertions(+), 61 deletions(-) diff --git a/codegen/sdk-codegen/aws-models/appsync.json b/codegen/sdk-codegen/aws-models/appsync.json index 8b30eca4a3e..925e9273fe0 100644 --- a/codegen/sdk-codegen/aws-models/appsync.json +++ b/codegen/sdk-codegen/aws-models/appsync.json @@ -2250,7 +2250,7 @@ "healthMetricsConfig": { "target": "com.amazonaws.appsync#CacheHealthMetricsConfig", "traits": { - "smithy.api#documentation": "

Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include:

\n \n

Metrics will be recorded by API ID. You can set the value to ENABLED or\n DISABLED.

" + "smithy.api#documentation": "

Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include:

\n \n

Metrics will be recorded by API ID. You can set the value to ENABLED or\n DISABLED.

" } } }, @@ -4331,14 +4331,14 @@ "resolverLevelMetricsBehavior": { "target": "com.amazonaws.appsync#ResolverLevelMetricsBehavior", "traits": { - "smithy.api#documentation": "

Controls how resolver metrics will be emitted to CloudWatch. Resolver metrics include:

\n \n

These metrics can be emitted to CloudWatch per resolver or for all resolvers in the request. Metrics will be\n recorded by API ID and resolver name. resolverLevelMetricsBehavior accepts one of these values at\n a time:

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

Controls how resolver metrics will be emitted to CloudWatch. Resolver metrics include:

\n \n

These metrics can be emitted to CloudWatch per resolver or for all resolvers in the request. Metrics will be\n recorded by API ID and resolver name. resolverLevelMetricsBehavior accepts one of these values at\n a time:

\n ", "smithy.api#required": {} } }, "dataSourceLevelMetricsBehavior": { "target": "com.amazonaws.appsync#DataSourceLevelMetricsBehavior", "traits": { - "smithy.api#documentation": "

Controls how data source metrics will be emitted to CloudWatch. Data source metrics include:

\n \n

These metrics can be emitted to CloudWatch per data source or for all data sources in the request. Metrics\n will be recorded by API ID and data source name. dataSourceLevelMetricsBehavior accepts one of\n these values at a time:

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

Controls how data source metrics will be emitted to CloudWatch. Data source metrics include:

\n \n

These metrics can be emitted to CloudWatch per data source or for all data sources in the request. Metrics\n will be recorded by API ID and data source name. dataSourceLevelMetricsBehavior accepts one of\n these values at a time:

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

Enables and controls the enhanced metrics feature. Enhanced metrics emit granular data on API usage and\n performance such as AppSync request and error counts, latency, and cache hits/misses. All enhanced metric data\n is sent to your CloudWatch account, and you can configure the types of data that will be sent.

\n

Enhanced metrics can be configured at the resolver, data source, and operation levels.\n EnhancedMetricsConfig contains three required parameters, each controlling one of these\n categories:

\n
    \n
  1. \n

    \n resolverLevelMetricsBehavior: Controls how resolver metrics will be emitted to\n CloudWatch. Resolver metrics include:

    \n
      \n
    • \n

      GraphQL errors: The number of GraphQL errors that occurred.

      \n
      • \n
    • \n

      Requests: The number of invocations that occurred during a request.

      \n
      • \n
    • \n

      Latency: The time to complete a resolver invocation.

      \n
      • \n
    • \n

      Cache hits: The number of cache hits during a request.

      \n
      • \n
    • \n

      Cache misses: The number of cache misses during a request.

      \n
      • \n
    \n

    These metrics can be emitted to CloudWatch per resolver or for all resolvers in the request. Metrics\n will be recorded by API ID and resolver name. resolverLevelMetricsBehavior accepts one of\n these values at a time:

    \n
      \n
    • \n

      \n FULL_REQUEST_RESOLVER_METRICS: Records and emits metric data for all resolvers\n in the request.

      \n
      • \n
    • \n

      \n PER_RESOLVER_METRICS: Records and emits metric data for resolvers that have the\n metricConfig value set to ENABLED.

      \n
      • \n
    \n
    2. \n
  2. \n

    \n dataSourceLevelMetricsBehavior: Controls how data source metrics will be emitted to\n CloudWatch. Data source metrics include:

    \n
      \n
    • \n

      Requests: The number of invocations that occured during a request.

      \n
      • \n
    • \n

      Latency: The time to complete a data source invocation.

      \n
      • \n
    • \n

      Errors: The number of errors that occurred during a data source invocation.

      \n
      • \n
    \n

    These metrics can be emitted to CloudWatch per data source or for all data sources in the request.\n Metrics will be recorded by API ID and data source name. dataSourceLevelMetricsBehavior\n accepts one of these values at a time:

    \n
      \n
    • \n

      \n FULL_REQUEST_DATA_SOURCE_METRICS: Records and emits metric data for all data\n sources in the request.

      \n
      • \n
    • \n

      \n PER_DATA_SOURCE_METRICS: Records and emits metric data for data sources that\n have the metricConfig value set to ENABLED.

      \n
      • \n
    \n
    3. \n
  3. \n

    \n operationLevelMetricsConfig: Controls how operation metrics will be emitted to\n CloudWatch. Operation metrics include:

    \n
      \n
    • \n

      Requests: The number of times a specified GraphQL operation was called.

      \n
      • \n
    • \n

      GraphQL errors: The number of GraphQL errors that occurred during a specified GraphQL\n operation.

      \n
      • \n
    \n

    Metrics will be recorded by API ID and operation name. You can set the value to ENABLED\n or DISABLED.

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

Enables and controls the enhanced metrics feature. Enhanced metrics emit granular data on API usage and\n performance such as AppSync request and error counts, latency, and cache hits/misses. All enhanced metric data\n is sent to your CloudWatch account, and you can configure the types of data that will be sent.

\n

Enhanced metrics can be configured at the resolver, data source, and operation levels.\n EnhancedMetricsConfig contains three required parameters, each controlling one of these\n categories:

\n
    \n
  1. \n

    \n resolverLevelMetricsBehavior: Controls how resolver metrics will be emitted to\n CloudWatch. Resolver metrics include:

    \n
      \n
    • \n

      GraphQL errors: The number of GraphQL errors that occurred.

      \n
      • \n
    • \n

      Requests: The number of invocations that occurred during a request.

      \n
      • \n
    • \n

      Latency: The time to complete a resolver invocation.

      \n
      • \n
    • \n

      Cache hits: The number of cache hits during a request.

      \n
      • \n
    • \n

      Cache misses: The number of cache misses during a request.

      \n
      • \n
    \n

    These metrics can be emitted to CloudWatch per resolver or for all resolvers in the request. Metrics\n will be recorded by API ID and resolver name. resolverLevelMetricsBehavior accepts one of\n these values at a time:

    \n
      \n
    • \n

      \n FULL_REQUEST_RESOLVER_METRICS: Records and emits metric data for all resolvers\n in the request.

      \n
      • \n
    • \n

      \n PER_RESOLVER_METRICS: Records and emits metric data for resolvers that have the\n metricsConfig value set to ENABLED.

      \n
      • \n
    \n
    2. \n
  2. \n

    \n dataSourceLevelMetricsBehavior: Controls how data source metrics will be emitted to\n CloudWatch. Data source metrics include:

    \n
      \n
    • \n

      Requests: The number of invocations that occured during a request.

      \n
      • \n
    • \n

      Latency: The time to complete a data source invocation.

      \n
      • \n
    • \n

      Errors: The number of errors that occurred during a data source invocation.

      \n
      • \n
    \n

    These metrics can be emitted to CloudWatch per data source or for all data sources in the request.\n Metrics will be recorded by API ID and data source name. dataSourceLevelMetricsBehavior\n accepts one of these values at a time:

    \n
      \n
    • \n

      \n FULL_REQUEST_DATA_SOURCE_METRICS: Records and emits metric data for all data\n sources in the request.

      \n
      • \n
    • \n

      \n PER_DATA_SOURCE_METRICS: Records and emits metric data for data sources that\n have the metricsConfig value set to ENABLED.

      \n
      • \n
    \n
    3. \n
  3. \n

    \n operationLevelMetricsConfig: Controls how operation metrics will be emitted to\n CloudWatch. Operation metrics include:

    \n
      \n
    • \n

      Requests: The number of times a specified GraphQL operation was called.

      \n
      • \n
    • \n

      GraphQL errors: The number of GraphQL errors that occurred during a specified GraphQL\n operation.

      \n
      • \n
    \n

    Metrics will be recorded by API ID and operation name. You can set the value to ENABLED\n or DISABLED.

    \n
    4. \n
" } }, "com.amazonaws.appsync#EnvironmentVariableKey": { @@ -8422,7 +8422,7 @@ "healthMetricsConfig": { "target": "com.amazonaws.appsync#CacheHealthMetricsConfig", "traits": { - "smithy.api#documentation": "

Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include:

\n \n

Metrics will be recorded by API ID. You can set the value to ENABLED or\n DISABLED.

" + "smithy.api#documentation": "

Controls how cache health metrics will be emitted to CloudWatch. Cache health metrics include:

\n \n

Metrics will be recorded by API ID. You can set the value to ENABLED or\n DISABLED.

" } } }, diff --git a/codegen/sdk-codegen/aws-models/qldb.json b/codegen/sdk-codegen/aws-models/qldb.json index 26471be1935..638deaab8a0 100644 --- a/codegen/sdk-codegen/aws-models/qldb.json +++ b/codegen/sdk-codegen/aws-models/qldb.json @@ -153,7 +153,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -196,7 +195,8 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -209,7 +209,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -223,7 +222,6 @@ "assign": "PartitionResult" } ], - "type": "tree", "rules": [ { "conditions": [ @@ -246,7 +244,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -281,7 +278,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -292,14 +288,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS and DualStack are enabled, but this partition does not support one or both", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -313,14 +311,12 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ - true, { "fn": "getAttr", "argv": [ @@ -329,11 +325,11 @@ }, "supportsFIPS" ] - } + }, + true ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -344,14 +340,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS is enabled but this partition does not support FIPS", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -365,7 +363,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -385,7 +382,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -396,14 +392,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "DualStack is enabled but this partition does not support DualStack", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [], @@ -414,9 +412,11 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" } - ] + ], + "type": "tree" }, { "conditions": [], @@ -1369,7 +1369,7 @@ "EncryptionDescription": { "target": "com.amazonaws.qldb#LedgerEncryptionDescription", "traits": { - "smithy.api#documentation": "

Information about the encryption of data at rest in the ledger. This includes the\n current status, the KMS key, and when the key became inaccessible (in the case of an\n error).

" + "smithy.api#documentation": "

Information about the encryption of data at rest in the ledger. This includes the\n current status, the KMS key, and when the key became inaccessible (in the case of an\n error). If this parameter is undefined, the ledger uses an Amazon Web Services owned KMS key for encryption.

" } } }, @@ -1997,7 +1997,7 @@ "KmsKeyArn": { "target": "com.amazonaws.qldb#Arn", "traits": { - "smithy.api#documentation": "

The Amazon Resource Name (ARN) of the customer managed KMS key that the ledger uses for\n encryption at rest. If this parameter is undefined, the ledger uses an Amazon Web Services owned KMS key\n for encryption.

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

The Amazon Resource Name (ARN) of the customer managed KMS key that the ledger uses for\n encryption at rest. If this parameter is undefined, the ledger uses an Amazon Web Services owned KMS key\n for encryption. It will display AWS_OWNED_KMS_KEY when updating the ledger's encryption configuration to the Amazon Web Services owned KMS key.

", "smithy.api#required": {} } }, diff --git a/codegen/sdk-codegen/aws-models/rds.json b/codegen/sdk-codegen/aws-models/rds.json index f397dde2c88..67674344919 100644 --- a/codegen/sdk-codegen/aws-models/rds.json +++ b/codegen/sdk-codegen/aws-models/rds.json @@ -10988,7 +10988,7 @@ } }, "DBShardGroupIdentifier": { - "target": "com.amazonaws.rds#String", + "target": "com.amazonaws.rds#DBShardGroupIdentifier", "traits": { "smithy.api#documentation": "

The name of the DB shard group.

" } @@ -11048,6 +11048,16 @@ "smithy.api#httpError": 400 } }, + "com.amazonaws.rds#DBShardGroupIdentifier": { + "type": "string", + "traits": { + "smithy.api#length": { + "min": 1, + "max": 63 + }, + "smithy.api#pattern": "^[a-zA-Z][a-zA-Z0-9]*(-[a-zA-Z0-9]+)*$" + } + }, "com.amazonaws.rds#DBShardGroupNotFoundFault": { "type": "structure", "members": { @@ -12588,7 +12598,7 @@ "type": "structure", "members": { "DBShardGroupIdentifier": { - "target": "com.amazonaws.rds#String", + "target": "com.amazonaws.rds#DBShardGroupIdentifier", "traits": { "smithy.api#clientOptional": {}, "smithy.api#documentation": "

Teh name of the DB shard group to delete.

", @@ -15744,7 +15754,7 @@ "type": "structure", "members": { "DBShardGroupIdentifier": { - "target": "com.amazonaws.rds#String", + "target": "com.amazonaws.rds#DBShardGroupIdentifier", "traits": { "smithy.api#documentation": "

The user-supplied DB shard group identifier or the Amazon Resource Name (ARN) of the DB shard group. If this parameter is specified, \n information for only the specific DB shard group is returned. This parameter isn't case-sensitive.

\n

Constraints:

\n " } @@ -22695,7 +22705,7 @@ "type": "structure", "members": { "DBShardGroupIdentifier": { - "target": "com.amazonaws.rds#String", + "target": "com.amazonaws.rds#DBShardGroupIdentifier", "traits": { "smithy.api#clientOptional": {}, "smithy.api#documentation": "

The name of the DB shard group to modify.

", @@ -25288,7 +25298,7 @@ "type": "structure", "members": { "DBShardGroupIdentifier": { - "target": "com.amazonaws.rds#String", + "target": "com.amazonaws.rds#DBShardGroupIdentifier", "traits": { "smithy.api#clientOptional": {}, "smithy.api#documentation": "

The name of the DB shard group to reboot.

", diff --git a/codegen/sdk-codegen/aws-models/rum.json b/codegen/sdk-codegen/aws-models/rum.json index b37fa1da48e..eb9793f243b 100644 --- a/codegen/sdk-codegen/aws-models/rum.json +++ b/codegen/sdk-codegen/aws-models/rum.json @@ -122,7 +122,7 @@ "GuestRoleArn": { "target": "com.amazonaws.rum#Arn", "traits": { - "smithy.api#documentation": "

The ARN of the guest IAM role that is attached to the Amazon Cognito identity pool \n that is used to authorize the sending of data to RUM.

" + "smithy.api#documentation": "

The ARN of the guest IAM role that is attached to the Amazon Cognito identity pool \n that is used to authorize the sending of data to RUM.

\n \n

It is possible that an app monitor does not have a value for GuestRoleArn. For example, \n this can happen when you use the console to create an app monitor and you allow CloudWatch RUM to \n create a new identity pool for Authorization. In this case, GuestRoleArn is not present in the \n GetAppMonitor\n response because it is not stored by the service.

\n

If this issue affects you, you can take one of the following steps:

\n \n " } }, "AllowCookies": { @@ -340,7 +340,7 @@ } ], "traits": { - "smithy.api#documentation": "

Specifies the extended metrics and custom metrics that you want a CloudWatch RUM app monitor to send to a destination. Valid\n destinations include CloudWatch and Evidently.

\n

By default, RUM app monitors send some metrics to CloudWatch. These default metrics\n are listed in CloudWatch metrics that you can collect \n with CloudWatch RUM.

\n

In addition to these default metrics, you can choose to send extended metrics or custom metrics or both.

\n \n

The maximum number of metric definitions that you can specify in one \n BatchCreateRumMetricDefinitions operation is 200.

\n

The maximum number of metric definitions that one destination can contain is 2000.

\n

Extended metrics sent to CloudWatch and RUM custom metrics are charged as CloudWatch custom metrics. Each combination of additional dimension name and dimension\n value counts as a custom metric. For more information, see \n Amazon CloudWatch Pricing.

\n

You must have\n already created a destination for the metrics before you send them. For more information, see \n PutRumMetricsDestination.

\n

If some metric definitions specified in a BatchCreateRumMetricDefinitions operations are not valid,\n those metric definitions fail and return errors, but all valid metric definitions in the same operation still succeed.

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

Specifies the extended metrics and custom metrics that you want a CloudWatch RUM app monitor to send to a destination. Valid\n destinations include CloudWatch and Evidently.

\n

By default, RUM app monitors send some metrics to CloudWatch. These default metrics\n are listed in CloudWatch metrics that you can collect \n with CloudWatch RUM.

\n

In addition to these default metrics, you can choose to send extended metrics, custom\n metrics, or both.

\n \n

The maximum number of metric definitions that you can specify in one \n BatchCreateRumMetricDefinitions operation is 200.

\n

The maximum number of metric definitions that one destination can contain is 2000.

\n

Extended metrics sent to CloudWatch and RUM custom metrics are charged as CloudWatch custom metrics. Each combination of additional dimension name and dimension\n value counts as a custom metric. For more information, see \n Amazon CloudWatch Pricing.

\n

You must have\n already created a destination for the metrics before you send them. For more information, see \n PutRumMetricsDestination.

\n

If some metric definitions specified in a BatchCreateRumMetricDefinitions operations are not valid,\n those metric definitions fail and return errors, but all valid metric definitions in the same operation still succeed.

", "smithy.api#externalDocumentation": { "API Reference": "https://docs.aws.amazon.com/rum/latest/developerguide/BatchCreateRumMetricDefinitions.html" }, @@ -402,7 +402,7 @@ "Destination": { "target": "com.amazonaws.rum#MetricDestination", "traits": { - "smithy.api#documentation": "

The destination to send the metrics to. Valid values are CloudWatch and Evidently. If\n you specify Evidently, you must also specify the ARN of the CloudWatchEvidently experiment \n that will receive\n the metrics and an IAM role that has permission to write to the experiment.

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

The destination to send the metrics to. Valid values are CloudWatch and\n Evidently. If you specify Evidently, you must also specify the\n Amazon Resource Name (ARN) of the CloudWatchEvidently experiment that will receive\n the metrics and an IAM role that has permission to write to the\n experiment.

", "smithy.api#required": {} } }, @@ -770,7 +770,7 @@ "AppMonitorConfiguration": { "target": "com.amazonaws.rum#AppMonitorConfiguration", "traits": { - "smithy.api#documentation": "

A structure that contains much of the configuration data for the app monitor. If you are using \n Amazon Cognito for authorization, you must include this structure in your request, and it must include the ID of the \n Amazon Cognito identity pool to use for authorization. If you don't include AppMonitorConfiguration, you must set up your own \n authorization method. For more information, see \n Authorize your application\n to send data to Amazon Web Services.

\n

If you omit this argument, the sample rate used for RUM is set to 10% of the user sessions.

" + "smithy.api#documentation": "

A structure that contains much of the configuration data for the app monitor. If you are using \n Amazon Cognito for authorization, you must include this structure in your request, and it must include the ID of the \n Amazon Cognito identity pool to use for authorization. If you don't include AppMonitorConfiguration, you must set up your own \n authorization method. For more information, see \n Authorize your application\n to send data to Amazon Web Services.

\n

If you omit this argument, the sample rate used for RUM is set to 10% of the user sessions.

" } }, "CwLogEnabled": { @@ -1588,7 +1588,7 @@ "ValueKey": { "target": "com.amazonaws.rum#ValueKey", "traits": { - "smithy.api#documentation": "

The field within the event object that the metric value is sourced from.

\n

If you omit this field, a hardcoded value of 1 is pushed as the metric value. This is useful if you\n just want to count the number of events that the filter catches.

\n

If this metric is sent to CloudWatch Evidently, this field will be passed to Evidently raw and Evidently \n will handle data extraction from the event.

" + "smithy.api#documentation": "

The field within the event object that the metric value is sourced from.

\n

If you omit this field, a hardcoded value of 1 is pushed as the metric value. This is\n useful if you want to count the number of events that the filter catches.

\n

If this metric is sent to CloudWatch Evidently, this field will be passed to\n Evidently raw. Evidently will handle data extraction from the event.

" } }, "UnitLabel": { @@ -1606,7 +1606,7 @@ "EventPattern": { "target": "com.amazonaws.rum#EventPattern", "traits": { - "smithy.api#documentation": "

The pattern that defines the metric, specified as a JSON object. RUM checks events that happen in a user's session\n against the pattern, and events that match the pattern are sent to the metric destination.

\n

When you define extended metrics, the metric definition is not valid if EventPattern\n is omitted.

\n

Example event patterns:

\n \n

If the metrics destination'\n is CloudWatch and the event\n also matches a value in DimensionKeys, then the metric is published with the specified dimensions.

" + "smithy.api#documentation": "

The pattern that defines the metric, specified as a JSON object. RUM checks events that happen in a user's session\n against the pattern, and events that match the pattern are sent to the metric destination.

\n

When you define extended metrics, the metric definition is not valid if EventPattern\n is omitted.

\n

Example event patterns:

\n \n

If the metrics destination is CloudWatch and the event also matches a value\n in DimensionKeys, then the metric is published with the specified dimensions.

" } }, "Namespace": { @@ -1617,7 +1617,7 @@ } }, "traits": { - "smithy.api#documentation": "

Use this structure to define one extended metric or custom metric that RUM will send\n to CloudWatch or CloudWatch Evidently. For more information, see \n \n Additional metrics that you can send to CloudWatch and CloudWatch Evidently.

\n

This structure is validated differently for extended metrics and custom metrics. For extended metrics\n that are sent to the AWS/RUM namespace, the following validations apply:

\n \n

For custom metrics, the following validation rules apply:

\n \n

Valid key values for first-level keys in the ValueKey, EventPattern, and \n DimensionKeys fields:

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

Use this structure to define one extended metric or custom metric that RUM will send\n to CloudWatch or CloudWatch Evidently. For more information, see \n \n Custom metrics and extended metrics that you can send to CloudWatch and CloudWatch Evidently.

\n

This structure is validated differently for extended metrics and custom metrics. For extended metrics\n that are sent to the AWS/RUM namespace, the following validations apply:

\n \n

For custom metrics, the following validation rules apply:

\n \n

Valid key values for first-level keys in the ValueKey, EventPattern, and \n DimensionKeys fields:

\n " } }, "com.amazonaws.rum#MetricDefinitions": { @@ -1871,7 +1871,7 @@ "IamRoleArn": { "target": "com.amazonaws.rum#IamRoleArn", "traits": { - "smithy.api#documentation": "

This parameter is required if Destination is Evidently. If Destination is \n CloudWatch, do not use this parameter.

\n

This parameter specifies\n the ARN of an IAM role that RUM will assume to write to the Evidently \n experiment that you are sending metrics to. This role must have permission to write to that experiment.

" + "smithy.api#documentation": "

This parameter is required if Destination is Evidently. If Destination is \n CloudWatch, don't use this parameter.

\n

This parameter specifies\n the ARN of an IAM role that RUM will assume to write to the Evidently \n experiment that you are sending metrics to. This role must have permission to write to that experiment.

\n

If you specify this parameter, you must be signed on to a role that has PassRole permissions attached to it, to allow\n the role to be passed. The \n CloudWatchAmazonCloudWatchRUMFullAccess\n policy doesn't include PassRole\n permissions.

" } } } @@ -2023,7 +2023,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -2066,7 +2065,8 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -2079,7 +2079,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -2093,7 +2092,6 @@ "assign": "PartitionResult" } ], - "type": "tree", "rules": [ { "conditions": [ @@ -2116,7 +2114,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -2151,7 +2148,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -2162,14 +2158,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS and DualStack are enabled, but this partition does not support one or both", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -2183,14 +2181,12 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ { "fn": "booleanEquals", "argv": [ - true, { "fn": "getAttr", "argv": [ @@ -2199,11 +2195,11 @@ }, "supportsFIPS" ] - } + }, + true ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -2214,14 +2210,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "FIPS is enabled but this partition does not support FIPS", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [ @@ -2235,7 +2233,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [ @@ -2255,7 +2252,6 @@ ] } ], - "type": "tree", "rules": [ { "conditions": [], @@ -2266,14 +2262,16 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" }, { "conditions": [], "error": "DualStack is enabled but this partition does not support DualStack", "type": "error" } - ] + ], + "type": "tree" }, { "conditions": [], @@ -2284,9 +2282,11 @@ }, "type": "endpoint" } - ] + ], + "type": "tree" } - ] + ], + "type": "tree" }, { "conditions": [], @@ -3159,7 +3159,7 @@ "AppMonitorConfiguration": { "target": "com.amazonaws.rum#AppMonitorConfiguration", "traits": { - "smithy.api#documentation": "

A structure that contains much of the configuration data for the app monitor. If you are using \n Amazon Cognito for authorization, you must include this structure in your request, and it must include the ID of the \n Amazon Cognito identity pool to use for authorization. If you don't include AppMonitorConfiguration, you must set up your own \n authorization method. For more information, see \n Authorize your application\n to send data to Amazon Web Services.

" + "smithy.api#documentation": "

A structure that contains much of the configuration data for the app monitor. If you are using \n Amazon Cognito for authorization, you must include this structure in your request, and it must include the ID of the \n Amazon Cognito identity pool to use for authorization. If you don't include AppMonitorConfiguration, you must set up your own \n authorization method. For more information, see \n Authorize your application\n to send data to Amazon Web Services.

" } }, "CwLogEnabled": {