@aws-sdk/client-cloudwatch 3.692.0 → 3.694.0

package/dist-types/commands/ListMetricsCommand.d.ts

@@ -29,17 +29,15 @@ declare const ListMetricsCommand_base: {
 /**
  * <p>List the specified metrics. You can use the returned metrics with <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a> to get statistical data.</p>
  *          <p>Up to 500 results are returned for any one call. To retrieve additional results,
- * 			use the returned token with subsequent calls.</p>
- *          <p>After you create a metric, allow up to 15 minutes for the metric to appear. To see metric
- * 			statistics sooner, use <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a>.</p>
- *          <p>If you are using CloudWatch cross-account observability, you can use this operation in a monitoring account and
- * 			view metrics from the linked source accounts. For more information, see
- * 			<a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account.html">CloudWatch cross-account observability</a>.</p>
+ *             use the returned token with subsequent calls.</p>
+ *          <p>After you create a metric, allow up to 15 minutes for the metric to appear. To see
+ *             metric statistics sooner, use <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a>.</p>
+ *          <p>If you are using CloudWatch cross-account observability, you can use this
+ *             operation in a monitoring account and view metrics from the linked source accounts. For
+ *             more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Unified-Cross-Account.html">CloudWatch cross-account observability</a>.</p>
  *          <p>
- *             <code>ListMetrics</code> doesn't return information about metrics if those metrics haven't
- * 	reported data in the past two weeks. To retrieve those metrics, use
- * 		<a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or
- * 		<a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a>.</p>
+ *             <code>ListMetrics</code> doesn't return information about metrics if those metrics
+ *             haven't reported data in the past two weeks. To retrieve those metrics, use <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -90,7 +88,8 @@ declare const ListMetricsCommand_base: {
  * @see {@link CloudWatchClientResolvedConfig | config} for CloudWatchClient's `config` shape.
  *
  * @throws {@link InternalServiceFault} (server fault)
- *  <p>Request processing has failed due to some unknown error, exception, or failure.</p>
+ *  <p>Request processing has failed due to some unknown error, exception, or
+ *             failure.</p>
  *
  * @throws {@link InvalidParameterValueException} (client fault)
  *  <p>The value of an input parameter is bad or out-of-range.</p>

package/dist-types/commands/ListTagsForResourceCommand.d.ts

@@ -27,8 +27,8 @@ declare const ListTagsForResourceCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Displays the tags associated with a CloudWatch resource. Currently, alarms
- * 			and Contributor Insights rules support tagging.</p>
+ * <p>Displays the tags associated with a CloudWatch resource. Currently, alarms and
+ *             Contributor Insights rules support tagging.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -58,7 +58,8 @@ declare const ListTagsForResourceCommand_base: {
  * @see {@link CloudWatchClientResolvedConfig | config} for CloudWatchClient's `config` shape.
  *
  * @throws {@link InternalServiceFault} (server fault)
- *  <p>Request processing has failed due to some unknown error, exception, or failure.</p>
+ *  <p>Request processing has failed due to some unknown error, exception, or
+ *             failure.</p>
  *
  * @throws {@link InvalidParameterValueException} (client fault)
  *  <p>The value of an input parameter is bad or out-of-range.</p>

package/dist-types/commands/PutAnomalyDetectorCommand.d.ts

@@ -27,11 +27,12 @@ declare const PutAnomalyDetectorCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates an anomaly detection model for a CloudWatch metric. You can use the model
- * 			to display a band of expected normal values when the metric is graphed.</p>
- *          <p>If you have enabled unified cross-account observability, and this account is a monitoring
- * 			account, the metric can be in the same account or a source account. You can specify the account ID
- * 			in the object you specify in the <code>SingleMetricAnomalyDetector</code> parameter.</p>
+ * <p>Creates an anomaly detection model for a CloudWatch metric. You can use the model to
+ *             display a band of expected normal values when the metric is graphed.</p>
+ *          <p>If you have enabled unified cross-account observability, and this account is a
+ *             monitoring account, the metric can be in the same account or a source account. You can
+ *             specify the account ID in the object you specify in the
+ *             <code>SingleMetricAnomalyDetector</code> parameter.</p>
  *          <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Anomaly_Detection.html">CloudWatch Anomaly Detection</a>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
@@ -109,7 +110,8 @@ declare const PutAnomalyDetectorCommand_base: {
  * @see {@link CloudWatchClientResolvedConfig | config} for CloudWatchClient's `config` shape.
  *
  * @throws {@link InternalServiceFault} (server fault)
- *  <p>Request processing has failed due to some unknown error, exception, or failure.</p>
+ *  <p>Request processing has failed due to some unknown error, exception, or
+ *             failure.</p>
  *
  * @throws {@link InvalidParameterCombinationException} (client fault)
  *  <p>Parameters were used together that cannot be used together.</p>

package/dist-types/commands/PutCompositeAlarmCommand.d.ts

@@ -28,19 +28,17 @@ declare const PutCompositeAlarmCommand_base: {
 };
 /**
  * <p>Creates or updates a <i>composite alarm</i>. When you create a composite
- * 			alarm, you specify a rule expression for the alarm that takes into account the alarm
- * 			states of other alarms that you have created. The composite alarm goes into ALARM state
- * 			only if all conditions of the rule are met.</p>
+ *             alarm, you specify a rule expression for the alarm that takes into account the alarm
+ *             states of other alarms that you have created. The composite alarm goes into ALARM state
+ *             only if all conditions of the rule are met.</p>
  *          <p>The alarms specified in a composite alarm's rule expression can include metric alarms
- * 			and other composite alarms. The rule expression of a composite alarm can include as many as 100 underlying alarms.
- * 			Any single alarm can be included in the rule expressions of as many as 150 composite alarms.</p>
- *          <p>Using composite alarms can reduce
- * 			alarm noise. You can create multiple metric alarms,
- * 			and also create a composite alarm and
- * 			set up alerts only
- * 			for the composite alarm. For example, you could create a composite
- * 			alarm that goes into ALARM state only when more than one of the underlying metric alarms
- * 			are in ALARM state.</p>
+ *             and other composite alarms. The rule expression of a composite alarm can include as many
+ *             as 100 underlying alarms. Any single alarm can be included in the rule expressions of as
+ *             many as 150 composite alarms.</p>
+ *          <p>Using composite alarms can reduce alarm noise. You can create multiple metric alarms,
+ *             and also create a composite alarm and set up alerts only for the composite alarm. For
+ *             example, you could create a composite alarm that goes into ALARM state only when more
+ *             than one of the underlying metric alarms are in ALARM state.</p>
  *          <p>Composite alarms can take the following actions:</p>
  *          <ul>
  *             <li>
@@ -57,28 +55,32 @@ declare const PutCompositeAlarmCommand_base: {
  *             </li>
  *          </ul>
  *          <note>
- *             <p>It is possible to create a loop or cycle of composite alarms, where composite alarm A depends on composite alarm B, and
- * 			composite alarm B also depends on composite alarm A. In this scenario, you can't delete any composite alarm that is part of the cycle
- * 			because there is always still a composite alarm that depends on that alarm that you want to delete.</p>
- *             <p>To get out of such a situation, you must
- * 			break 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
- * 			change to make to break a cycle is to change the <code>AlarmRule</code> of one of the alarms to <code>false</code>. </p>
- *             <p>Additionally, the evaluation of composite alarms stops if CloudWatch detects a cycle in the evaluation path.
- * 		</p>
+ *             <p>It is possible to create a loop or cycle of composite alarms, where composite
+ *                 alarm A depends on composite alarm B, and composite alarm B also depends on
+ *                 composite alarm A. In this scenario, you can't delete any composite alarm that is
+ *                 part of the cycle because there is always still a composite alarm that depends on
+ *                 that alarm that you want to delete.</p>
+ *             <p>To get out of such a situation, you must break 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 change to make to break a cycle is to change the
+ *                 <code>AlarmRule</code> of one of the alarms to <code>false</code>. </p>
+ *             <p>Additionally, the evaluation of composite alarms stops if CloudWatch detects a
+ *                 cycle in the evaluation path. </p>
  *          </note>
  *          <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. For a
- * 			composite alarm, this initial time after creation is the only time that
- * 			the
- * 			alarm can be in <code>INSUFFICIENT_DATA</code> state.</p>
+ *             <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. For a
+ *             composite alarm, this initial time after creation is the only time that the alarm can be
+ *             in <code>INSUFFICIENT_DATA</code> state.</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>To use this operation, you must be signed on with
- * 			the <code>cloudwatch:PutCompositeAlarm</code> permission that is scoped to <code>*</code>. You can't create a
- * 			composite alarms if your <code>cloudwatch:PutCompositeAlarm</code> permission has a narrower scope.</p>
- *          <p>If you are an IAM user, you must have <code>iam:CreateServiceLinkedRole</code> to create
- * 			a composite alarm that has Systems Manager OpsItem actions.</p>
+ *             completely overwrites the previous configuration of the alarm.</p>
+ *          <p>To use this operation, you must be signed on with the
+ *             <code>cloudwatch:PutCompositeAlarm</code> permission that is scoped to
+ *             <code>*</code>. You can't create a composite alarms if your
+ *             <code>cloudwatch:PutCompositeAlarm</code> permission has a narrower scope.</p>
+ *          <p>If you are an IAM user, you must have
+ *             <code>iam:CreateServiceLinkedRole</code> to create a composite alarm that has
+ *             Systems Manager OpsItem actions.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/PutDashboardCommand.d.ts

@@ -27,20 +27,22 @@ declare const PutDashboardCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a dashboard if it does not already exist, or updates an existing dashboard. If you update a dashboard,
- * 		the entire contents are replaced with what you specify here.</p>
+ * <p>Creates a dashboard if it does not already exist, or updates an existing dashboard.
+ *             If you update a dashboard, the entire contents are replaced with what you specify
+ *             here.</p>
  *          <p>All dashboards in your account are global, not region-specific.</p>
  *          <p>A simple way to create a dashboard using <code>PutDashboard</code> is to copy an
- * 			existing dashboard. To copy an existing dashboard using the console, you can load the dashboard
- * 			and then use the View/edit source command in the Actions menu to display the JSON  block
- * 			for that dashboard. Another way to copy a dashboard is to
- * 			use <code>GetDashboard</code>, and then use the data returned
- * 			within <code>DashboardBody</code> as the template for the new dashboard when you call <code>PutDashboard</code>.</p>
+ *             existing dashboard. To copy an existing dashboard using the console, you can load the
+ *             dashboard and then use the View/edit source command in the Actions menu to display the
+ *             JSON block for that dashboard. Another way to copy a dashboard is to use
+ *                 <code>GetDashboard</code>, and then use the data returned within
+ *                 <code>DashboardBody</code> as the template for the new dashboard when you call
+ *                 <code>PutDashboard</code>.</p>
  *          <p>When you create a dashboard with <code>PutDashboard</code>, a good practice is to
- * 			add a text widget at the top of the dashboard with a message that the dashboard was created by script and should
- * 		not be changed in the console. This message could also point console users to the location
- * 		of the <code>DashboardBody</code> script or the CloudFormation template used to create the
- * 		dashboard.</p>
+ *             add a text widget at the top of the dashboard with a message that the dashboard was
+ *             created by script and should not be changed in the console. This message could also
+ *             point console users to the location of the <code>DashboardBody</code> script or the
+ *             CloudFormation template used to create the dashboard.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -74,7 +76,8 @@ declare const PutDashboardCommand_base: {
  *  <p>Some part of the dashboard data is invalid.</p>
  *
  * @throws {@link InternalServiceFault} (server fault)
- *  <p>Request processing has failed due to some unknown error, exception, or failure.</p>
+ *  <p>Request processing has failed due to some unknown error, exception, or
+ *             failure.</p>
  *
  * @throws {@link CloudWatchServiceException}
  * <p>Base exception class for all service exceptions from CloudWatch service.</p>

package/dist-types/commands/PutInsightRuleCommand.d.ts

@@ -27,11 +27,12 @@ declare const PutInsightRuleCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates a Contributor Insights rule. Rules evaluate log events in a
- * 		CloudWatch Logs log group, enabling you to find contributor data for the log events in that log group. For more information,
- * 		see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContributorInsights.html">Using Contributor Insights to Analyze High-Cardinality Data</a>.</p>
- *          <p>If you create a rule, delete it, and then re-create it with the same name, historical data from the first time
- * 			the rule was created might not be available.</p>
+ * <p>Creates a Contributor Insights rule. Rules evaluate log events in a CloudWatch Logs
+ *             log group, enabling you to find contributor data for the log events in that log group.
+ *             For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/ContributorInsights.html">Using Contributor
+ *                 Insights to Analyze High-Cardinality Data</a>.</p>
+ *          <p>If you create a rule, delete it, and then re-create it with the same name, historical
+ *             data from the first time the rule was created might not be available.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/PutManagedInsightRulesCommand.d.ts

@@ -27,23 +27,16 @@ declare const PutManagedInsightRulesCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>
- * 			Creates a managed Contributor Insights rule
- * 			for a specified Amazon Web Services resource.
- * 			When you enable a managed rule,
- * 			you create a Contributor Insights rule
- * 			that collects data
- * 			from Amazon Web Services services.
- * 			You cannot edit these rules
- * 			with <code>PutInsightRule</code>.
- * 			The rules can be enabled, disabled, and deleted using <code>EnableInsightRules</code>, <code>DisableInsightRules</code>, and <code>DeleteInsightRules</code>.
- * 			If a previously created managed rule is currently disabled,
- * 			a subsequent call
- * 			to this API will re-enable it.
- * 			Use <code>ListManagedInsightRules</code>
- * 			to describe all available rules.
+ * <p> Creates a managed Contributor Insights rule for a specified Amazon Web Services
+ *             resource. When you enable a managed rule, you create a Contributor Insights rule that
+ *             collects data from Amazon Web Services services. You cannot edit these rules with
+ *             <code>PutInsightRule</code>. The rules can be enabled, disabled, and deleted using
+ *             <code>EnableInsightRules</code>, <code>DisableInsightRules</code>, and
+ *             <code>DeleteInsightRules</code>. If a previously created managed rule is currently
+ *             disabled, a subsequent call to this API will re-enable it. Use
+ *             <code>ListManagedInsightRules</code> to describe all available rules.
  *
- * 		</p>
+ *         </p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/PutMetricAlarmCommand.d.ts

@@ -27,57 +27,54 @@ declare const PutMetricAlarmCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <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>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>
+ *             <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> permission for all alarms with EC2 actions</p>
+ *                <p>The <code>iam:CreateServiceLinkedRole</code> permission for all alarms with
+ *                     EC2 actions</p>
  *             </li>
  *             <li>
  *                <p>The <code>iam:CreateServiceLinkedRole</code> permissions to create an alarm
- * 					with Systems Manager OpsItem or response plan actions.</p>
+ *                     with Systems Manager OpsItem or response plan 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>Each <code>PutMetricAlarm</code> action has a maximum uncompressed payload of 120 KB.</p>
+ *          <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>Each <code>PutMetricAlarm</code> action has a maximum uncompressed payload of 120
+ *             KB.</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>
+ *          <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>
+ *                <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>
+ *                <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>
  * @example

package/dist-types/commands/PutMetricDataCommand.d.ts

@@ -27,47 +27,53 @@ declare const PutMetricDataCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Publishes metric data points to Amazon CloudWatch. CloudWatch associates
- * 			the data points with the specified metric. If the specified metric does not exist,
- * 			CloudWatch creates the metric. When CloudWatch creates a metric, it can
- * 			take up to fifteen minutes for the metric to appear in calls to <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_ListMetrics.html">ListMetrics</a>.</p>
- *          <p>You can publish either individual data points in the <code>Value</code> field, or
- * 		arrays of values and the number of times each value occurred during the period by using the
- * 		<code>Values</code> and <code>Counts</code> fields in the <code>MetricData</code> structure. Using
- * 		the <code>Values</code> and <code>Counts</code> method enables you to publish up to 150 values per metric
- * 			with one <code>PutMetricData</code> request, and
- * 		supports retrieving percentile statistics on this data.</p>
- *          <p>Each <code>PutMetricData</code> request is limited to 1 MB in size for HTTP POST requests. You can
- * 			send a payload compressed by gzip. Each request
- * 		is also limited to no more than 1000 different metrics.</p>
- *          <p>Although the <code>Value</code> parameter accepts numbers of type
- * 			<code>Double</code>, CloudWatch rejects values that are either too small
- * 			or too large. Values must be in the range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,
- * 			-Infinity) are not supported.</p>
- *          <p>You can use up to 30 dimensions per metric to further clarify what data the metric collects. Each dimension
- * 			consists of a Name and Value pair. For more information about specifying dimensions, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html">Publishing Metrics</a> in the
- * 			<i>Amazon CloudWatch User Guide</i>.</p>
- *          <p>You specify the time stamp to be associated with each data point. You can specify
- * 		time stamps that are as much as two weeks before the current date, and as much as 2 hours after
- * 		the current day and time.</p>
- *          <p>Data points with time stamps from 24 hours ago or longer can take at least 48
- * 			hours to become available for <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or
- * 			<a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a> from the time they
- * 			are submitted. Data points with time stamps between 3 and 24 hours ago can take as much as 2 hours to become available
- * 			for for <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or
- * 			<a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a>.</p>
+ * <p>Publishes metric data to Amazon CloudWatch. CloudWatch associates the data with the
+ *             specified metric. If the specified metric does not exist, CloudWatch creates the metric.
+ *             When CloudWatch creates a metric, it can take up to fifteen minutes for the metric to
+ *             appear in calls to <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_ListMetrics.html">ListMetrics</a>.</p>
+ *          <p>You can publish metrics with associated entity data (so that related telemetry can be
+ *             found and viewed together), or publish metric data by itself. To send entity data with
+ *             your metrics, use the <code>EntityMetricData</code> parameter. To send metrics without
+ *             entity data, use the <code>MetricData</code> parameter. The
+ *             <code>EntityMetricData</code> structure includes <code>MetricData</code> structures
+ *             for the metric data.</p>
+ *          <p>You can publish either individual values in the <code>Value</code> field, or arrays of
+ *             values and the number of times each value occurred during the period by using the
+ *                 <code>Values</code> and <code>Counts</code> fields in the <code>MetricData</code>
+ *             structure. Using the <code>Values</code> and <code>Counts</code> method enables you to
+ *             publish up to 150 values per metric with one <code>PutMetricData</code> request, and
+ *             supports retrieving percentile statistics on this data.</p>
+ *          <p>Each <code>PutMetricData</code> request is limited to 1 MB in size for HTTP POST
+ *             requests. You can send a payload compressed by gzip. Each request is also limited to no
+ *             more than 1000 different metrics (across both the <code>MetricData</code> and
+ *             <code>EntityMetricData</code> properties).</p>
+ *          <p>Although the <code>Value</code> parameter accepts numbers of type <code>Double</code>,
+ *             CloudWatch rejects values that are either too small or too large. Values must be in the
+ *             range of -2^360 to 2^360. In addition, special values (for example, NaN, +Infinity,
+ *             -Infinity) are not supported.</p>
+ *          <p>You can use up to 30 dimensions per metric to further clarify what data the metric
+ *             collects. Each dimension consists of a Name and Value pair. For more information about
+ *             specifying dimensions, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html">Publishing
+ *                 Metrics</a> in the <i>Amazon CloudWatch User Guide</i>.</p>
+ *          <p>You specify the time stamp to be associated with each data point. You can specify time
+ *             stamps that are as much as two weeks before the current date, and as much as 2 hours
+ *             after the current day and time.</p>
+ *          <p>Data points with time stamps from 24 hours ago or longer can take at least 48 hours to
+ *             become available for <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a> from the time they are submitted. Data points with time
+ *             stamps between 3 and 24 hours ago can take as much as 2 hours to become available for
+ *                 <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricData.html">GetMetricData</a> or <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/APIReference/API_GetMetricStatistics.html">GetMetricStatistics</a>.</p>
  *          <p>CloudWatch needs raw data points to calculate percentile statistics. If you publish
- * 			data using a statistic set instead, you can only retrieve
- * 			percentile statistics for this data if one of the following conditions is true:</p>
+ *             data using a statistic set instead, you can only retrieve percentile statistics for this
+ *             data if one of the following conditions is true:</p>
  *          <ul>
  *             <li>
- *                <p>The <code>SampleCount</code> value of the statistic set is 1 and <code>Min</code>,
- * 					<code>Max</code>, and <code>Sum</code> are all equal.</p>
+ *                <p>The <code>SampleCount</code> value of the statistic set is 1 and
+ *                         <code>Min</code>, <code>Max</code>, and <code>Sum</code> are all
+ *                     equal.</p>
  *             </li>
  *             <li>
- *                <p>The <code>Min</code> and
- * 					<code>Max</code> are equal, and <code>Sum</code> is equal to <code>Min</code>
- * 					multiplied by <code>SampleCount</code>.</p>
+ *                <p>The <code>Min</code> and <code>Max</code> are equal, and <code>Sum</code>
+ *                     is equal to <code>Min</code> multiplied by <code>SampleCount</code>.</p>
  *             </li>
  *          </ul>
  * @example
@@ -78,7 +84,7 @@ declare const PutMetricDataCommand_base: {
  * const client = new CloudWatchClient(config);
  * const input = { // PutMetricDataInput
  *   Namespace: "STRING_VALUE", // required
- *   MetricData: [ // MetricData // required
+ *   MetricData: [ // MetricData
  *     { // MetricDatum
  *       MetricName: "STRING_VALUE", // required
  *       Dimensions: [ // Dimensions
@@ -105,6 +111,46 @@ declare const PutMetricDataCommand_base: {
  *       StorageResolution: Number("int"),
  *     },
  *   ],
+ *   EntityMetricData: [ // EntityMetricDataList
+ *     { // EntityMetricData
+ *       Entity: { // Entity
+ *         KeyAttributes: { // EntityKeyAttributesMap
+ *           "<keys>": "STRING_VALUE",
+ *         },
+ *         Attributes: { // EntityAttributesMap
+ *           "<keys>": "STRING_VALUE",
+ *         },
+ *       },
+ *       MetricData: [
+ *         {
+ *           MetricName: "STRING_VALUE", // required
+ *           Dimensions: [
+ *             {
+ *               Name: "STRING_VALUE", // required
+ *               Value: "STRING_VALUE", // required
+ *             },
+ *           ],
+ *           Timestamp: new Date("TIMESTAMP"),
+ *           Value: Number("double"),
+ *           StatisticValues: {
+ *             SampleCount: Number("double"), // required
+ *             Sum: Number("double"), // required
+ *             Minimum: Number("double"), // required
+ *             Maximum: Number("double"), // required
+ *           },
+ *           Values: [
+ *             Number("double"),
+ *           ],
+ *           Counts: [
+ *             Number("double"),
+ *           ],
+ *           Unit: "Seconds" || "Microseconds" || "Milliseconds" || "Bytes" || "Kilobytes" || "Megabytes" || "Gigabytes" || "Terabytes" || "Bits" || "Kilobits" || "Megabits" || "Gigabits" || "Terabits" || "Percent" || "Count" || "Bytes/Second" || "Kilobytes/Second" || "Megabytes/Second" || "Gigabytes/Second" || "Terabytes/Second" || "Bits/Second" || "Kilobits/Second" || "Megabits/Second" || "Gigabits/Second" || "Terabits/Second" || "Count/Second" || "None",
+ *           StorageResolution: Number("int"),
+ *         },
+ *       ],
+ *     },
+ *   ],
+ *   StrictEntityValidation: true || false,
  * };
  * const command = new PutMetricDataCommand(input);
  * const response = await client.send(command);
@@ -119,7 +165,8 @@ declare const PutMetricDataCommand_base: {
  * @see {@link CloudWatchClientResolvedConfig | config} for CloudWatchClient's `config` shape.
  *
  * @throws {@link InternalServiceFault} (server fault)
- *  <p>Request processing has failed due to some unknown error, exception, or failure.</p>
+ *  <p>Request processing has failed due to some unknown error, exception, or
+ *             failure.</p>
  *
  * @throws {@link InvalidParameterCombinationException} (client fault)
  *  <p>Parameters were used together that cannot be used together.</p>