@aws-sdk/client-cloudwatch-logs 3.845.0 → 3.847.0

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

@@ -27,44 +27,43 @@ declare const PutDeliveryDestinationCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates or updates a logical <i>delivery destination</i>. A delivery destination is an Amazon Web Services resource that represents an
- *        Amazon Web Services service that logs can be sent to. CloudWatch Logs, Amazon S3, and
- *        Firehose are supported as logs delivery destinations.</p>
- *          <p>To configure logs delivery between a supported Amazon Web Services service and a destination, you must do the following:</p>
+ * <p>Creates or updates a logical <i>delivery destination</i>. A delivery
+ *       destination is an Amazon Web Services resource that represents an Amazon Web Services service
+ *       that logs can be sent to. CloudWatch Logs, Amazon S3, and Firehose are
+ *       supported as logs delivery destinations  and X-Ray as the trace delivery destination.</p>
+ *          <p>To configure logs delivery between a supported Amazon Web Services service and a
+ *       destination, you must do the following:</p>
  *          <ul>
  *             <li>
- *                <p>Create a delivery source, which is a logical object that represents the resource that is actually
- *          sending the logs. For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliverySource.html">PutDeliverySource</a>.</p>
+ *                <p>Create a delivery source, which is a logical object that represents the resource that
+ *           is actually sending the logs. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliverySource.html">PutDeliverySource</a>.</p>
  *             </li>
  *             <li>
- *                <p>Use <code>PutDeliveryDestination</code> to create a <i>delivery destination</i> in the same account of the actual delivery destination.
- *          The delivery destination that you create is a logical object that represents the actual
- *          delivery destination.  </p>
+ *                <p>Use <code>PutDeliveryDestination</code> to create a <i>delivery
+ *             destination</i> in the same account of the actual delivery destination. The
+ *           delivery destination that you create is a logical object that represents the actual
+ *           delivery destination. </p>
  *             </li>
  *             <li>
- *                <p>If you are delivering logs cross-account, you must use
- *          <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestinationPolicy.html">PutDeliveryDestinationPolicy</a>
- *          in the destination account to assign an IAM policy to the
- *          destination. This policy allows delivery to that destination.
- *        </p>
+ *                <p>If you are delivering logs cross-account, you must use <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestinationPolicy.html">PutDeliveryDestinationPolicy</a> in the destination account to assign an IAM policy to the destination. This policy allows delivery to that destination.
+ *         </p>
  *             </li>
  *             <li>
- *                <p>Use <code>CreateDelivery</code> to create a <i>delivery</i> by pairing exactly
- *          one delivery source and one delivery destination. For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html">CreateDelivery</a>.
- *        </p>
+ *                <p>Use <code>CreateDelivery</code> to create a <i>delivery</i> by pairing
+ *           exactly one delivery source and one delivery destination. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html">CreateDelivery</a>. </p>
  *             </li>
  *          </ul>
- *          <p>You can configure a single delivery source to send logs to multiple destinations by creating multiple deliveries. You
- *        can also create multiple deliveries to configure multiple delivery sources to send logs to the same delivery destination.</p>
- *          <p>Only some Amazon Web Services services support being configured as a delivery source. These services are listed
- *        as <b>Supported [V2 Permissions]</b> in the table at
- *        <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html">Enabling
- *          logging from Amazon Web Services services.</a>
+ *          <p>You can configure a single delivery source to send logs to multiple destinations by
+ *       creating multiple deliveries. You can also create multiple deliveries to configure multiple
+ *       delivery sources to send logs to the same delivery destination.</p>
+ *          <p>Only some Amazon Web Services services support being configured as a delivery source. These
+ *       services are listed as <b>Supported [V2 Permissions]</b> in the
+ *       table at <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html">Enabling logging from
+ *           Amazon Web Services services.</a>
  *          </p>
- *          <p>If you use this operation to update an existing delivery destination, all the current delivery destination parameters are overwritten
- *        with the new parameter values that you specify.</p>
+ *          <p>If you use this operation to update an existing delivery destination, all the current
+ *       delivery destination parameters are overwritten with the new parameter values that you
+ *       specify.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -77,6 +76,7 @@ declare const PutDeliveryDestinationCommand_base: {
  *   deliveryDestinationConfiguration: { // DeliveryDestinationConfiguration
  *     destinationResourceArn: "STRING_VALUE", // required
  *   },
+ *   deliveryDestinationType: "S3" || "CWL" || "FH" || "XRAY",
  *   tags: { // Tags
  *     "<keys>": "STRING_VALUE",
  *   },
@@ -87,7 +87,7 @@ declare const PutDeliveryDestinationCommand_base: {
  * //   deliveryDestination: { // DeliveryDestination
  * //     name: "STRING_VALUE",
  * //     arn: "STRING_VALUE",
- * //     deliveryDestinationType: "S3" || "CWL" || "FH",
+ * //     deliveryDestinationType: "S3" || "CWL" || "FH" || "XRAY",
  * //     outputFormat: "json" || "plain" || "w3c" || "raw" || "parquet",
  * //     deliveryDestinationConfiguration: { // DeliveryDestinationConfiguration
  * //       destinationResourceArn: "STRING_VALUE", // required

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

@@ -27,37 +27,35 @@ declare const PutDeliveryDestinationPolicyCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates and assigns an IAM policy that grants permissions to CloudWatch Logs to deliver
- *        logs cross-account to a specified destination in this account. To configure the delivery of logs from an
- *      Amazon Web Services service in another account to a logs delivery destination in the current account, you must do the following:</p>
+ * <p>Creates and assigns an IAM policy that grants permissions to CloudWatch Logs to deliver logs cross-account to a specified destination in this account. To
+ *       configure the delivery of logs from an Amazon Web Services service in another account to a logs
+ *       delivery destination in the current account, you must do the following:</p>
  *          <ul>
  *             <li>
- *                <p>Create a delivery source, which is a logical object that represents the resource that is actually
- *          sending the logs. For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliverySource.html">PutDeliverySource</a>.</p>
+ *                <p>Create a delivery source, which is a logical object that represents the resource that
+ *           is actually sending the logs. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliverySource.html">PutDeliverySource</a>.</p>
  *             </li>
  *             <li>
- *                <p>Create a <i>delivery destination</i>, which is a logical object that represents the actual
- *          delivery destination.  For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestination.html">PutDeliveryDestination</a>.</p>
+ *                <p>Create a <i>delivery destination</i>, which is a logical object that
+ *           represents the actual delivery destination. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestination.html">PutDeliveryDestination</a>.</p>
  *             </li>
  *             <li>
- *                <p>Use this operation in the destination account to assign an IAM policy to the
- *          destination. This policy allows delivery to that destination.
- *         </p>
+ *                <p>Use this operation in the destination account to assign an IAM policy
+ *           to the destination. This policy allows delivery to that destination. </p>
  *             </li>
  *             <li>
- *                <p>Create a <i>delivery</i> by pairing exactly one delivery source and one delivery destination.
- *          For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html">CreateDelivery</a>.</p>
+ *                <p>Create a <i>delivery</i> by pairing exactly one delivery source and one
+ *           delivery destination. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html">CreateDelivery</a>.</p>
  *             </li>
  *          </ul>
- *          <p>Only some Amazon Web Services services support being configured as a delivery source. These services are listed
- *        as <b>Supported [V2 Permissions]</b> in the table at
- *        <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html">Enabling
- *          logging from Amazon Web Services services.</a>
+ *          <p>Only some Amazon Web Services services support being configured as a delivery source. These
+ *       services are listed as <b>Supported [V2 Permissions]</b> in the
+ *       table at <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html">Enabling logging from
+ *           Amazon Web Services services.</a>
  *          </p>
- *          <p>The contents of the policy must include two statements. One statement enables general logs delivery, and the other
- *     allows delivery to the chosen destination. See the examples for the needed policies.</p>
+ *          <p>The contents of the policy must include two statements. One statement enables general logs
+ *       delivery, and the other allows delivery to the chosen destination. See the examples for the
+ *       needed policies.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -27,42 +27,40 @@ declare const PutDeliverySourceCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates or updates a logical <i>delivery source</i>. A delivery source represents an Amazon Web Services resource that sends logs to an
- *        logs delivery destination. The destination can be CloudWatch Logs, Amazon S3, or Firehose.</p>
- *          <p>To configure logs delivery between a delivery destination and an Amazon Web Services service that is supported as a delivery source, you must do the following:</p>
+ * <p>Creates or updates a logical <i>delivery source</i>. A delivery source
+ *       represents an Amazon Web Services resource that sends logs to an logs delivery destination. The
+ *       destination can be CloudWatch Logs, Amazon S3, Firehose or X-Ray for sending traces.</p>
+ *          <p>To configure logs delivery between a delivery destination and an Amazon Web Services
+ *       service that is supported as a delivery source, you must do the following:</p>
  *          <ul>
  *             <li>
- *                <p>Use <code>PutDeliverySource</code> to create a delivery source, which is a logical object that represents the resource that is actually
- *          sending the logs. </p>
+ *                <p>Use <code>PutDeliverySource</code> to create a delivery source, which is a logical
+ *           object that represents the resource that is actually sending the logs. </p>
  *             </li>
  *             <li>
- *                <p>Use <code>PutDeliveryDestination</code> to create a <i>delivery destination</i>, which is a logical object that represents the actual
- *          delivery destination. For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestination.html">PutDeliveryDestination</a>.</p>
+ *                <p>Use <code>PutDeliveryDestination</code> to create a <i>delivery
+ *             destination</i>, which is a logical object that represents the actual delivery
+ *           destination. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestination.html">PutDeliveryDestination</a>.</p>
  *             </li>
  *             <li>
- *                <p>If you are delivering logs cross-account, you must use
- *          <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestinationPolicy.html">PutDeliveryDestinationPolicy</a>
- *          in the destination account to assign an IAM policy to the
- *          destination. This policy allows delivery to that destination.
- *        </p>
+ *                <p>If you are delivering logs cross-account, you must use <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDeliveryDestinationPolicy.html">PutDeliveryDestinationPolicy</a> in the destination account to assign an IAM policy to the destination. This policy allows delivery to that destination.
+ *         </p>
  *             </li>
  *             <li>
- *                <p>Use <code>CreateDelivery</code> to create a <i>delivery</i> by pairing exactly
- *          one delivery source and one delivery destination. For more
- *          information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html">CreateDelivery</a>.
- *        </p>
+ *                <p>Use <code>CreateDelivery</code> to create a <i>delivery</i> by pairing
+ *           exactly one delivery source and one delivery destination. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_CreateDelivery.html">CreateDelivery</a>. </p>
  *             </li>
  *          </ul>
- *          <p>You can configure a single delivery source to send logs to multiple destinations by creating multiple deliveries. You
- *        can also create multiple deliveries to configure multiple delivery sources to send logs to the same delivery destination.</p>
- *          <p>Only some Amazon Web Services services support being configured as a delivery source. These services are listed
- *        as <b>Supported [V2 Permissions]</b> in the table at
- *        <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html">Enabling
- *        logging from Amazon Web Services services.</a>
+ *          <p>You can configure a single delivery source to send logs to multiple destinations by
+ *       creating multiple deliveries. You can also create multiple deliveries to configure multiple
+ *       delivery sources to send logs to the same delivery destination.</p>
+ *          <p>Only some Amazon Web Services services support being configured as a delivery source. These
+ *       services are listed as <b>Supported [V2 Permissions]</b> in the
+ *       table at <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html">Enabling logging from
+ *           Amazon Web Services services.</a>
  *          </p>
- *          <p>If you use this operation to update an existing delivery source, all the current delivery source parameters are overwritten
- *      with the new parameter values that you specify.</p>
+ *          <p>If you use this operation to update an existing delivery source, all the current delivery
+ *       source parameters are overwritten with the new parameter values that you specify.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -27,16 +27,17 @@ declare const PutDestinationCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates or updates a destination. This operation is used only to create destinations for cross-account subscriptions.</p>
+ * <p>Creates or updates a destination. This operation is used only to create destinations
+ *       for cross-account subscriptions.</p>
  *          <p>A destination encapsulates a physical resource (such as an Amazon Kinesis stream). With
  *       a destination, you can subscribe to a real-time stream of log events for a different account,
  *       ingested using <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutLogEvents.html">PutLogEvents</a>.</p>
- *          <p>Through an access policy, a destination controls what is written to it.
- *       By default, <code>PutDestination</code> does not set any access policy with the destination,
- *       which means a cross-account user cannot call <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutSubscriptionFilter.html">PutSubscriptionFilter</a> against
- *       this destination. To enable this, the destination owner must call <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDestinationPolicy.html">PutDestinationPolicy</a> after <code>PutDestination</code>.</p>
+ *          <p>Through an access policy, a destination controls what is written to it. By default,
+ *         <code>PutDestination</code> does not set any access policy with the destination, which means
+ *       a cross-account user cannot call <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutSubscriptionFilter.html">PutSubscriptionFilter</a> against this destination. To enable this, the destination
+ *       owner must call <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutDestinationPolicy.html">PutDestinationPolicy</a> after <code>PutDestination</code>.</p>
  *          <p>To perform a <code>PutDestination</code> operation, you must also have the
- *     <code>iam:PassRole</code> permission.</p>
+ *         <code>iam:PassRole</code> permission.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -27,9 +27,10 @@ declare const PutDestinationPolicyCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates or updates an access policy associated with an existing
- *       destination. An access policy is an <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/policies_overview.html">IAM policy document</a> that is used
- *       to authorize claims to register a subscription filter against a given destination.</p>
+ * <p>Creates or updates an access policy associated with an existing destination. An access
+ *       policy is an <a href="https://docs.aws.amazon.com/IAM/latest/UserGuide/policies_overview.html">IAM
+ *         policy document</a> that is used to authorize claims to register a subscription filter
+ *       against a given destination.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -27,23 +27,24 @@ declare const PutIndexPolicyCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates or updates a <i>field index policy</i> for the specified log group. Only log groups
- *     in the Standard log class support field index policies. For more information about log classes, see
- *       <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch_Logs_Log_Classes.html">Log classes</a>.</p>
- *          <p>You can use field index policies to create <i>field indexes</i> on fields found in
- *       log events in the log group. Creating field indexes speeds up and lowers the costs for CloudWatch Logs Insights queries that reference
- *       those field indexes, because these queries attempt to skip the processing of log events that are known to not match the indexed field.
- *       Good fields to index are fields that you often need to query for and fields or values that match only a small fraction of the total log events.
- *       Common examples of indexes
- *       include request ID, session ID, userID, and instance IDs. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.html">Create field indexes to improve query performance and reduce costs</a>.</p>
- *          <p>To find the fields that are in your log group events, use the
- *       <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_GetLogGroupFields.html">GetLogGroupFields</a>
- *     operation.</p>
+ * <p>Creates or updates a <i>field index policy</i> for the specified log group.
+ *       Only log groups in the Standard log class support field index policies. For more information
+ *       about log classes, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatch_Logs_Log_Classes.html">Log
+ *       classes</a>.</p>
+ *          <p>You can use field index policies to create <i>field indexes</i> on fields
+ *       found in log events in the log group. Creating field indexes speeds up and lowers the costs
+ *       for CloudWatch Logs Insights queries that reference those field indexes, because these
+ *       queries attempt to skip the processing of log events that are known to not match the indexed
+ *       field. Good fields to index are fields that you often need to query for and fields or values
+ *       that match only a small fraction of the total log events. Common examples of indexes include
+ *       request ID, session ID, userID, and instance IDs. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-Field-Indexing.html">Create field indexes to improve query performance and reduce costs</a>.</p>
+ *          <p>To find the fields that are in your log group events, use the <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_GetLogGroupFields.html">GetLogGroupFields</a> operation.</p>
  *          <p>For example, suppose you have created a field index for <code>requestId</code>. Then, any
- *       CloudWatch Logs Insights query on that log group that includes <code>requestId = <i>value</i>
- *             </code>
- *       or <code>requestId IN [<i>value</i>, <i>value</i>, ...]</code> will process fewer log events
- *       to reduce costs, and have improved performance.</p>
+ *         CloudWatch Logs Insights query on that log group that includes <code>requestId =
+ *           <i>value</i>
+ *             </code> or <code>requestId IN [<i>value</i>,
+ *           <i>value</i>, ...]</code> will process fewer log events to reduce costs, and
+ *       have improved performance.</p>
  *          <p>Each index policy has the following quotas and restrictions:</p>
  *          <ul>
  *             <li>
@@ -53,13 +54,13 @@ declare const PutIndexPolicyCommand_base: {
  *                <p>Each field name can include as many as 100 characters.</p>
  *             </li>
  *          </ul>
- *          <p>Matches of log events to the names of indexed fields are case-sensitive. For example, a field index
- *     of <code>RequestId</code> won't match a log event containing <code>requestId</code>.</p>
- *          <p>Log group-level field index policies created with <code>PutIndexPolicy</code> override account-level field
- *       index policies created with <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutAccountPolicy.html">PutAccountPolicy</a>. If you use
- *       <code>PutIndexPolicy</code> to create a field
- *     index policy for a log group, that log group uses only that policy. The log group ignores any account-wide
- *     field index policy that you might have created.</p>
+ *          <p>Matches of log events to the names of indexed fields are case-sensitive. For example, a
+ *       field index of <code>RequestId</code> won't match a log event containing
+ *         <code>requestId</code>.</p>
+ *          <p>Log group-level field index policies created with <code>PutIndexPolicy</code> override
+ *       account-level field index policies created with <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutAccountPolicy.html">PutAccountPolicy</a>. If you use <code>PutIndexPolicy</code> to create a field index
+ *       policy for a log group, that log group uses only that policy. The log group ignores any
+ *       account-wide field index policy that you might have created.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -27,12 +27,14 @@ declare const PutIntegrationCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates an integration between CloudWatch Logs and another service in this account. Currently, only integrations with
- *        OpenSearch Service are supported, and currently you can have only one integration in your account.</p>
- *          <p>Integrating with OpenSearch Service makes it possible for you to create curated vended logs dashboards, powered
- *        by OpenSearch Service analytics. For more information, see
- *        <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-OpenSearch-Dashboards.html">Vended log dashboards powered by Amazon OpenSearch Service</a>.</p>
- *          <p>You can use this operation only to create a new integration. You can't modify an existing integration.</p>
+ * <p>Creates an integration between CloudWatch Logs and another service in this account.
+ *       Currently, only integrations with OpenSearch Service are supported, and currently you can have
+ *       only one integration in your account.</p>
+ *          <p>Integrating with OpenSearch Service makes it possible for you to create curated vended
+ *       logs dashboards, powered by OpenSearch Service analytics. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/CloudWatchLogs-OpenSearch-Dashboards.html">Vended log
+ *         dashboards powered by Amazon OpenSearch Service</a>.</p>
+ *          <p>You can use this operation only to create a new integration. You can't modify an existing
+ *       integration.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -29,11 +29,11 @@ declare const PutLogEventsCommand_base: {
 /**
  * <p>Uploads a batch of log events to the specified log stream.</p>
  *          <important>
- *             <p>The sequence token is now ignored in <code>PutLogEvents</code>
- *       actions. <code>PutLogEvents</code>
- *       actions are always accepted and never return <code>InvalidSequenceTokenException</code> or
- *       <code>DataAlreadyAcceptedException</code> even if the sequence token is not valid. You can use
- *       parallel <code>PutLogEvents</code> actions on the same log stream. </p>
+ *             <p>The sequence token is now ignored in <code>PutLogEvents</code> actions.
+ *           <code>PutLogEvents</code> actions are always accepted and never return
+ *           <code>InvalidSequenceTokenException</code> or <code>DataAlreadyAcceptedException</code>
+ *         even if the sequence token is not valid. You can use parallel <code>PutLogEvents</code>
+ *         actions on the same log stream. </p>
  *          </important>
  *          <p>The batch of events must satisfy the following constraints:</p>
  *          <ul>
@@ -42,20 +42,24 @@ declare const PutLogEventsCommand_base: {
  *           all event messages in UTF-8, plus 26 bytes for each log event.</p>
  *             </li>
  *             <li>
- *                <p>Events more than 2 hours in the future are rejected while processing remaining valid events.</p>
+ *                <p>Events more than 2 hours in the future are rejected while processing remaining
+ *           valid events.</p>
  *             </li>
  *             <li>
- *                <p>Events older than 14 days or preceding the log group's retention period are rejected while processing remaining valid events.</p>
+ *                <p>Events older than 14 days or preceding the log group's retention period are
+ *           rejected while processing remaining valid events.</p>
  *             </li>
  *             <li>
  *                <p>The log events in the batch must be in chronological order by their timestamp. The
  *           timestamp is the time that the event occurred, expressed as the number of milliseconds
  *           after <code>Jan 1, 1970 00:00:00 UTC</code>. (In Amazon Web Services Tools for PowerShell
  *           and the Amazon Web Services SDK for .NET, the timestamp is specified in .NET format:
- *             <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2017-09-15T13:45:30</code>.) </p>
+ *             <code>yyyy-mm-ddThh:mm:ss</code>. For example, <code>2017-09-15T13:45:30</code>.)
+ *         </p>
  *             </li>
  *             <li>
- *                <p> A batch of log events in a single request must be in a chronological order. Otherwise, the operation fails.</p>
+ *                <p> A batch of log events in a single request must be in a chronological order.
+ *           Otherwise, the operation fails.</p>
  *             </li>
  *             <li>
  *                <p>Each log event can be no larger than 1 MB.</p>
@@ -64,14 +68,14 @@ declare const PutLogEventsCommand_base: {
  *                <p>The maximum number of log events in a batch is 10,000.</p>
  *             </li>
  *             <li>
- *                <p>For valid events (within 14 days in the past to 2 hours in future), the time span in a single batch cannot exceed 24 hours. Otherwise, the operation fails.</p>
+ *                <p>For valid events (within 14 days in the past to 2 hours in future), the time span
+ *           in a single batch cannot exceed 24 hours. Otherwise, the operation fails.</p>
  *             </li>
  *          </ul>
  *          <important>
- *             <p>The quota of five requests per second per log stream
- *       has been removed. Instead, <code>PutLogEvents</code> actions are throttled based on a
- *       per-second per-account quota. You can request an increase to the per-second throttling
- *       quota by using the Service Quotas service.</p>
+ *             <p>The quota of five requests per second per log stream has been removed. Instead,
+ *           <code>PutLogEvents</code> actions are throttled based on a per-second per-account quota.
+ *         You can request an increase to the per-second throttling quota by using the Service Quotas service.</p>
  *          </important>
  *          <p>If a call to <code>PutLogEvents</code> returns "UnrecognizedClientException" the most
  *       likely cause is a non-valid Amazon Web Services access key ID or secret key. </p>
@@ -126,24 +130,23 @@ declare const PutLogEventsCommand_base: {
  *  <p>The event was already logged.</p>
  *          <important>
  *             <p>
- *                <code>PutLogEvents</code>
- *       actions are now always accepted and never return
- *       <code>DataAlreadyAcceptedException</code> regardless of whether a given batch of log events
- *       has already been accepted. </p>
+ *                <code>PutLogEvents</code> actions are now always accepted and never return
+ *           <code>DataAlreadyAcceptedException</code> regardless of whether a given batch of log
+ *         events has already been accepted. </p>
  *          </important>
  *
  * @throws {@link InvalidParameterException} (client fault)
  *  <p>A parameter is specified incorrectly.</p>
  *
  * @throws {@link InvalidSequenceTokenException} (client fault)
- *  <p>The sequence token is not valid. You can get the correct sequence token in
- *       the <code>expectedSequenceToken</code> field in the <code>InvalidSequenceTokenException</code>
- *     message. </p>
+ *  <p>The sequence token is not valid. You can get the correct sequence token in the
+ *         <code>expectedSequenceToken</code> field in the <code>InvalidSequenceTokenException</code>
+ *       message. </p>
  *          <important>
  *             <p>
- *                <code>PutLogEvents</code>
- *       actions are now always accepted and never return
- *       <code>InvalidSequenceTokenException</code> regardless of receiving an invalid sequence token. </p>
+ *                <code>PutLogEvents</code> actions are now always accepted and never return
+ *           <code>InvalidSequenceTokenException</code> regardless of receiving an invalid sequence
+ *         token. </p>
  *          </important>
  *
  * @throws {@link ResourceNotFoundException} (client fault)

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

@@ -32,26 +32,22 @@ declare const PutMetricFilterCommand_base: {
  *       through <a href="https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutLogEvents.html">PutLogEvents</a>.</p>
  *          <p>The maximum number of metric filters that can be associated with a log group is
  *       100.</p>
- *          <p>Using regular expressions in filter patterns is supported. For these filters,
- *       there is a quota of two regular expression patterns within a single filter pattern. There
- *       is also a quota of five regular expression patterns per log group.
- *     For more information about using regular expressions in filter patterns,
- *     see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/FilterAndPatternSyntax.html">
- *       Filter pattern syntax for metric filters, subscription filters, filter log events, and Live Tail</a>.</p>
- *          <p>When you create a metric filter, you can also optionally assign a unit and dimensions
- *     to the metric that is created.</p>
+ *          <p>Using regular expressions in filter patterns is supported. For these filters, there is a
+ *       quota of two regular expression patterns within a single filter pattern. There is also a quota
+ *       of five regular expression patterns per log group. For more information about using regular
+ *       expressions in filter patterns, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/FilterAndPatternSyntax.html"> Filter pattern syntax for
+ *         metric filters, subscription filters, filter log events, and Live Tail</a>.</p>
+ *          <p>When you create a metric filter, you can also optionally assign a unit and dimensions to
+ *       the metric that is created.</p>
  *          <important>
- *             <p>Metrics extracted from log events are charged as custom metrics.
- *       To prevent unexpected high charges, do not specify high-cardinality fields such as
- *       <code>IPAddress</code> or <code>requestID</code> as dimensions. Each different value
- *       found for
- *       a dimension is treated as a separate metric and accrues charges as a separate custom metric.
- *     </p>
- *             <p>CloudWatch Logs might disable a metric filter if it generates 1,000 different name/value pairs for
- *         your specified dimensions within one hour.</p>
+ *             <p>Metrics extracted from log events are charged as custom metrics. To prevent unexpected
+ *         high charges, do not specify high-cardinality fields such as <code>IPAddress</code> or
+ *           <code>requestID</code> as dimensions. Each different value found for a dimension is
+ *         treated as a separate metric and accrues charges as a separate custom metric. </p>
+ *             <p>CloudWatch Logs might disable a metric filter if it generates 1,000 different
+ *         name/value pairs for your specified dimensions within one hour.</p>
  *             <p>You can also set up a billing alarm to alert you if your charges are higher than
- *         expected. For more information,
- *         see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/monitor_estimated_charges_with_cloudwatch.html">
+ *         expected. For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/monitor_estimated_charges_with_cloudwatch.html">
  *           Creating a Billing Alarm to Monitor Your Estimated Amazon Web Services Charges</a>.
  *       </p>
  *          </important>

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

@@ -27,8 +27,8 @@ declare const PutQueryDefinitionCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates or updates a query definition for CloudWatch Logs Insights. For
- *       more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AnalyzingLogData.html">Analyzing Log Data with CloudWatch Logs Insights</a>.</p>
+ * <p>Creates or updates a query definition for CloudWatch Logs Insights. For more information,
+ *       see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AnalyzingLogData.html">Analyzing Log Data with CloudWatch Logs Insights</a>.</p>
  *          <p>To update a query definition, specify its <code>queryDefinitionId</code> in your request.
  *       The values of <code>name</code>, <code>queryString</code>, and <code>logGroupNames</code> are
  *       changed to the values that you specify in your update operation. No current values are
@@ -37,7 +37,7 @@ declare const PutQueryDefinitionCommand_base: {
  *       parameter in your update operation, the query definition changes to contain no log
  *       groups.</p>
  *          <p>You must have the <code>logs:PutQueryDefinition</code> permission to be able to perform
- *     this operation.</p>
+ *       this operation.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -27,9 +27,9 @@ declare const PutResourcePolicyCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Creates or updates a resource policy allowing other Amazon Web Services services to put log events to
- *       this account, such as Amazon Route 53. An account can have up to 10 resource policies per Amazon Web Services
- *       Region.</p>
+ * <p>Creates or updates a resource policy allowing other Amazon Web Services services to put
+ *       log events to this account, such as Amazon Route 53. An account can have up to 10 resource
+ *       policies per Amazon Web Services Region.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript
@@ -39,6 +39,8 @@ declare const PutResourcePolicyCommand_base: {
  * const input = { // PutResourcePolicyRequest
  *   policyName: "STRING_VALUE",
  *   policyDocument: "STRING_VALUE",
+ *   resourceArn: "STRING_VALUE",
+ *   expectedRevisionId: "STRING_VALUE",
  * };
  * const command = new PutResourcePolicyCommand(input);
  * const response = await client.send(command);
@@ -47,7 +49,11 @@ declare const PutResourcePolicyCommand_base: {
  * //     policyName: "STRING_VALUE",
  * //     policyDocument: "STRING_VALUE",
  * //     lastUpdatedTime: Number("long"),
+ * //     policyScope: "ACCOUNT" || "RESOURCE",
+ * //     resourceArn: "STRING_VALUE",
+ * //     revisionId: "STRING_VALUE",
  * //   },
+ * //   revisionId: "STRING_VALUE",
  * // };
  *
  * ```
@@ -64,6 +70,12 @@ declare const PutResourcePolicyCommand_base: {
  * @throws {@link LimitExceededException} (client fault)
  *  <p>You have reached the maximum number of resources that can be created.</p>
  *
+ * @throws {@link OperationAbortedException} (client fault)
+ *  <p>Multiple concurrent requests to update the same resource were in conflict.</p>
+ *
+ * @throws {@link ResourceNotFoundException} (client fault)
+ *  <p>The specified resource does not exist.</p>
+ *
  * @throws {@link ServiceUnavailableException} (server fault)
  *  <p>The service cannot complete the request.</p>
  *

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

@@ -41,10 +41,11 @@ declare const PutRetentionPolicyCommand_base: {
  *         retention setting until 72 hours after the previous retention period ends. Alternatively,
  *         wait to change the retention setting until you confirm that the earlier log events are
  *         deleted. </p>
- *             <p>When log events reach their retention setting they are marked for deletion. After
- *         they are marked for deletion, they do not add to your archival storage costs anymore, even if
+ *             <p>When log events reach their retention setting they are marked for deletion. After they
+ *         are marked for deletion, they do not add to your archival storage costs anymore, even if
  *         they are not actually deleted until later. These log events marked for deletion are also not
- *         included when you use an API to retrieve the <code>storedBytes</code> value to see how many bytes a log group is storing.</p>
+ *         included when you use an API to retrieve the <code>storedBytes</code> value to see how many
+ *         bytes a log group is storing.</p>
  *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.