npm - @aws-sdk/client-cost-explorer - Versions diffs - 3.229.0 → 3.231.0 - Mend

@aws-sdk/client-cost-explorer 3.229.0 → 3.231.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (10) hide show

package/dist-cjs/models/models_0.js +23 -20
package/dist-cjs/protocols/Aws_json1_1.js +12 -0
package/dist-es/models/models_0.js +15 -12
package/dist-es/protocols/Aws_json1_1.js +12 -0
package/dist-types/CostExplorer.d.ts +5 -4
package/dist-types/commands/CreateAnomalySubscriptionCommand.d.ts +3 -3
package/dist-types/commands/GetAnomaliesCommand.d.ts +2 -1
package/dist-types/models/models_0.d.ts +994 -398
package/dist-types/ts3.4/models/models_0.d.ts +45 -37
package/package.json +5 -5

package/dist-types/models/models_0.d.ts CHANGED Viewed

@@ -27,13 +27,31 @@ export declare enum AnomalyFeedbackType {
  */
 export interface Impact {
     /**
-     * <p>The maximum dollar value that's observed for an anomaly. </p>
+     * <p>The maximum dollar value that's observed for an anomaly.</p>
      */
     MaxImpact: number | undefined;
     /**
-     * <p>The cumulative dollar value that's observed for an anomaly. </p>
+     * <p>The cumulative dollar difference between the total actual spend and total expected
+     *             spend. It is calculated as <code>TotalActualSpend - TotalExpectedSpend</code>.</p>
      */
     TotalImpact?: number;
+    /**
+     * <p>The cumulative dollar amount that was actually spent during the anomaly.</p>
+     */
+    TotalActualSpend?: number;
+    /**
+     * <p>The cumulative dollar amount that was expected to be spent during the anomaly. It is
+     *             calculated using advanced machine learning models to determine the typical spending
+     *             pattern based on historical data for a customer.</p>
+     */
+    TotalExpectedSpend?: number;
+    /**
+     * <p>The cumulative percentage difference between the total actual spend and total expected
+     *             spend. It is calculated as <code>(TotalImpact / TotalExpectedSpend) * 100</code>. When
+     *                 <code>TotalExpectedSpend</code> is zero, this field is omitted. Expected spend can
+     *             be zero in situations such as when you start to use a service for the first time.</p>
+     */
+    TotalImpactPercentage?: number;
 }
 /**
  * <p>The combination of Amazon Web Service, linked account, linked account name,
@@ -129,6 +147,7 @@ export declare enum MatchOption {
     CONTAINS = "CONTAINS",
     ENDS_WITH = "ENDS_WITH",
     EQUALS = "EQUALS",
+    GREATER_THAN_OR_EQUAL = "GREATER_THAN_OR_EQUAL",
     STARTS_WITH = "STARTS_WITH"
 }
 /**
@@ -161,6 +180,8 @@ export interface CostCategoryValues {
 export declare enum Dimension {
     AGREEMENT_END_DATE_TIME_AFTER = "AGREEMENT_END_DATE_TIME_AFTER",
     AGREEMENT_END_DATE_TIME_BEFORE = "AGREEMENT_END_DATE_TIME_BEFORE",
+    ANOMALY_TOTAL_IMPACT_ABSOLUTE = "ANOMALY_TOTAL_IMPACT_ABSOLUTE",
+    ANOMALY_TOTAL_IMPACT_PERCENTAGE = "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
     AZ = "AZ",
     BILLING_ENTITY = "BILLING_ENTITY",
     CACHE_ENGINE = "CACHE_ENGINE",
@@ -199,9 +220,15 @@ export declare enum Dimension {
 export interface DimensionValues {
     /**
      * <p>The names of the metadata types that you can use to filter and group your results. For
-     *             example, <code>AZ</code> returns a list of Availability Zones.
-     *                 <code>LINK_ACCOUNT_NAME</code> and <code>SERVICE_CODE</code> can only be used in
-     *                 <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/AAPI_CostCategoryRule.html">CostCategoryRule</a>.</p>
+     *             example, <code>AZ</code> returns a list of Availability Zones.</p>
+     *          <p>Not all dimensions are supported in each API. Refer to the documentation for each
+     *             specific API to see what is supported.</p>
+     *          <p>
+     *             <code>LINK_ACCOUNT_NAME</code> and <code>SERVICE_CODE</code> can only be used in
+     *                 <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_CostCategoryRule.html">CostCategoryRule</a>.</p>
+     *          <p>
+     *             <code>ANOMALY_TOTAL_IMPACT_ABSOLUTE</code> and
+     *                 <code>ANOMALY_TOTAL_IMPACT_PERCENTAGE</code> can only be used in <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_AnomalySubscription.html">AnomalySubscriptions</a>.</p>
      */
     Key?: Dimension | string;
     /**
@@ -210,10 +237,13 @@ export interface DimensionValues {
      */
     Values?: string[];
     /**
-     * <p>The match options that you can use to filter your results. <code>MatchOptions</code>
-     *             is only applicable for actions related to Cost Category. The default values for
-     *                 <code>MatchOptions</code> are <code>EQUALS</code> and
-     *             <code>CASE_SENSITIVE</code>.</p>
+     * <p>The match options that you can use to filter your results.</p>
+     *          <p>
+     *             <code>MatchOptions</code> is only applicable for actions related to Cost Category and
+     *             Anomaly Subscriptions. Refer to the documentation for each specific API to see what is
+     *             supported.</p>
+     *          <p>The default values for <code>MatchOptions</code> are <code>EQUALS</code> and
+     *                 <code>CASE_SENSITIVE</code>.</p>
      */
     MatchOptions?: (MatchOption | string)[];
 }
@@ -279,42 +309,6 @@ export interface Subscriber {
      */
     Status?: SubscriberStatus | string;
 }
-/**
- * <p>The association between a monitor, threshold, and list of subscribers used to deliver
- *             notifications about anomalies detected by a monitor that exceeds a threshold. The
- *             content consists of the detailed metadata and the current status of the
- *                 <code>AnomalySubscription</code> object. </p>
- */
-export interface AnomalySubscription {
-    /**
-     * <p>The <code>AnomalySubscription</code> Amazon Resource Name (ARN). </p>
-     */
-    SubscriptionArn?: string;
-    /**
-     * <p>Your unique account identifier. </p>
-     */
-    AccountId?: string;
-    /**
-     * <p>A list of cost anomaly monitors. </p>
-     */
-    MonitorArnList: string[] | undefined;
-    /**
-     * <p>A list of subscribers to notify. </p>
-     */
-    Subscribers: Subscriber[] | undefined;
-    /**
-     * <p>The dollar value that triggers a notification if the threshold is exceeded. </p>
-     */
-    Threshold: number | undefined;
-    /**
-     * <p>The frequency that anomaly reports are sent over email. </p>
-     */
-    Frequency: AnomalySubscriptionFrequency | string | undefined;
-    /**
-     * <p>The name for the subscription. </p>
-     */
-    SubscriptionName: string | undefined;
-}
 /**
  * <p>The tag structure that contains a tag key and value. </p>
  *          <note>
@@ -356,48 +350,6 @@ export declare class LimitExceededException extends __BaseException {
      */
     constructor(opts: __ExceptionOptionType<LimitExceededException, __BaseException>);
 }
-export interface CreateAnomalySubscriptionRequest {
-    /**
-     * <p>The cost anomaly subscription object that you want to create. </p>
-     */
-    AnomalySubscription: AnomalySubscription | undefined;
-    /**
-     * <p>An optional list of tags to associate with the specified <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_AnomalySubscription.html">
-     *                <code>AnomalySubscription</code>
-     *             </a>. You can use resource tags to control access to
-     *       your <code>subscription</code> using IAM policies.</p>
-     *          <p>Each tag consists of a key and a value, and each key must be unique for the resource. The
-     *       following restrictions apply to resource tags:</p>
-     *          <ul>
-     *             <li>
-     *                <p>Although the maximum number of array members is 200, you can assign a maximum of 50
-     *           user-tags to one resource. The remaining are reserved for Amazon Web Services use</p>
-     *             </li>
-     *             <li>
-     *                <p>The maximum length of a key is 128 characters</p>
-     *             </li>
-     *             <li>
-     *                <p>The maximum length of a value is 256 characters</p>
-     *             </li>
-     *             <li>
-     *                <p>Keys and values can only contain alphanumeric characters, spaces, and any of the
-     *           following: <code>_.:/=+@-</code>
-     *                </p>
-     *             </li>
-     *             <li>
-     *                <p>Keys and values are case sensitive</p>
-     *             </li>
-     *             <li>
-     *                <p>Keys and values are trimmed for any leading or trailing whitespaces</p>
-     *             </li>
-     *             <li>
-     *                <p>Don’t use <code>aws:</code> as a prefix for your keys. This prefix is reserved for
-     *             Amazon Web Services use</p>
-     *             </li>
-     *          </ul>
-     */
-    ResourceTags?: ResourceTag[];
-}
 export interface CreateAnomalySubscriptionResponse {
     /**
      * <p>The unique identifier of your newly created cost anomaly subscription. </p>
@@ -729,18 +681,6 @@ export interface GetAnomalySubscriptionsRequest {
      */
     MaxResults?: number;
 }
-export interface GetAnomalySubscriptionsResponse {
-    /**
-     * <p>A list of cost anomaly subscriptions that includes the detailed metadata for each one.
-     *     </p>
-     */
-    AnomalySubscriptions: AnomalySubscription[] | undefined;
-    /**
-     * <p>The token to retrieve the next set of results. Amazon Web Services provides the token when
-     *       the response from a previous call has more results than the maximum page size. </p>
-     */
-    NextPageToken?: string;
-}
 /**
  * <p>The requested report expired. Update the date interval and try again.</p>
  */
@@ -3128,32 +3068,6 @@ export interface UpdateAnomalyMonitorResponse {
      */
     MonitorArn: string | undefined;
 }
-export interface UpdateAnomalySubscriptionRequest {
-    /**
-     * <p>A cost anomaly subscription Amazon Resource Name (ARN). </p>
-     */
-    SubscriptionArn: string | undefined;
-    /**
-     * <p>The update to the threshold value for receiving notifications. </p>
-     */
-    Threshold?: number;
-    /**
-     * <p>The update to the frequency value that subscribers receive notifications. </p>
-     */
-    Frequency?: AnomalySubscriptionFrequency | string;
-    /**
-     * <p>A list of cost anomaly monitor ARNs. </p>
-     */
-    MonitorArnList?: string[];
-    /**
-     * <p>The update to the subscriber list. </p>
-     */
-    Subscribers?: Subscriber[];
-    /**
-     * <p>The new name of the subscription. </p>
-     */
-    SubscriptionName?: string;
-}
 export interface UpdateAnomalySubscriptionResponse {
     /**
      * <p>A cost anomaly subscription ARN. </p>
@@ -3218,49 +3132,116 @@ export interface UpdateCostCategoryDefinitionResponse {
     EffectiveStart?: string;
 }
 /**
- * <p>Use <code>Expression</code> to filter by cost or by usage. There are two patterns: </p>
+ * <p>Use <code>Expression</code> to filter in various Cost Explorer APIs.</p>
+ *          <p>Not all <code>Expression</code> types are supported in each API. Refer to the
+ *             documentation for each specific API to see what is supported.</p>
+ *          <p>There are two patterns:</p>
  *          <ul>
  *             <li>
- *                <p>Simple dimension values - You can set the dimension name and values for the
- *                     filters that you plan to use. For example, you can filter for
- *                         <code>REGION==us-east-1 OR REGION==us-west-1</code>. For
- *                         <code>GetRightsizingRecommendation</code>, the Region is a full name (for
- *                     example, <code>REGION==US East (N. Virginia)</code>. The <code>Expression</code>
- *                     example is as follows:</p>
- *                <p>
- *                   <code>{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", “us-west-1” ]
- *                         } }</code>
- *                </p>
- *                <p>The list of dimension values are OR'd together to retrieve cost or usage data.
- *                     You can create <code>Expression</code> and <code>DimensionValues</code> objects
- *                     using either <code>with*</code> methods or <code>set*</code> methods in multiple
- *                     lines. </p>
+ *                <p>Simple dimension values.</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>There are three types of simple dimension values:
+ *                                 <code>CostCategories</code>, <code>Tags</code>, and
+ *                                 <code>Dimensions</code>.</p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>Specify the <code>CostCategories</code> field to define a
+ *                                     filter that acts on Cost Categories.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>Specify the <code>Tags</code> field to define a filter that
+ *                                     acts on Cost Allocation Tags.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>Specify the <code>Dimensions</code> field to define a filter
+ *                                     that acts on the <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DimensionValues.html">
+ *                                  <code>DimensionValues</code>
+ *                               </a>.</p>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                   <li>
+ *                      <p>For each filter type, you can set the dimension name and values for
+ *                             the filters that you plan to use.</p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>For example, you can filter for <code>REGION==us-east-1 OR
+ *                                         REGION==us-west-1</code>. For
+ *                                         <code>GetRightsizingRecommendation</code>, the Region is a
+ *                                     full name (for example, <code>REGION==US East (N.
+ *                                         Virginia)</code>.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>The corresponding <code>Expression</code> for this example is
+ *                                     as follows: <code>{ "Dimensions": { "Key": "REGION", "Values": [
+ *                                         "us-east-1", “us-west-1” ] } }</code>
+ *                            </p>
+ *                         </li>
+ *                         <li>
+ *                            <p>As shown in the previous example, lists of dimension values
+ *                                     are combined with <code>OR</code> when applying the
+ *                                     filter.</p>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                   <li>
+ *                      <p>You can also set different match options to further control how the
+ *                             filter behaves. Not all APIs support match options. Refer to the
+ *                             documentation for each specific API to see what is supported.</p>
+ *                      <ul>
+ *                         <li>
+ *                            <p>For example, you can filter for linked account names that
+ *                                     start with “a”.</p>
+ *                         </li>
+ *                         <li>
+ *                            <p>The corresponding <code>Expression</code> for this example is
+ *                                     as follows: <code>{ "Dimensions": { "Key":
+ *                                         "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ],
+ *                                         "Values": [ "a" ] } }</code>
+ *                            </p>
+ *                         </li>
+ *                      </ul>
+ *                   </li>
+ *                </ul>
  *             </li>
  *             <li>
- *                <p>Compound dimension values with logical operations - You can use multiple
- *                         <code>Expression</code> types and the logical operators
- *                         <code>AND/OR/NOT</code> to create a list of one or more
- *                         <code>Expression</code> objects. By doing this, you can filter on more
- *                     advanced options. For example, you can filter on <code>((REGION == us-east-1 OR
- *                         REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
- *                         DataTransfer)</code>. The <code>Expression</code> for that is as
- *                     follows:</p>
- *                <p>
- *                   <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
- *                         "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values":
- *                         ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values":
- *                         ["DataTransfer"] }}} ] } </code>
- *                </p>
+ *                <p>Compound <code>Expression</code> types with logical operations.</p>
+ *                <ul>
+ *                   <li>
+ *                      <p>You can use multiple <code>Expression</code> types and the logical
+ *                             operators <code>AND/OR/NOT</code> to create a list of one or more
+ *                                 <code>Expression</code> objects. By doing this, you can filter by
+ *                             more advanced options.</p>
+ *                   </li>
+ *                   <li>
+ *                      <p>For example, you can filter by <code>((REGION == us-east-1 OR REGION
+ *                                 == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
+ *                                 DataTransfer)</code>.</p>
+ *                   </li>
+ *                   <li>
+ *                      <p>The corresponding <code>Expression</code> for this example is as
+ *                             follows: <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION",
+ *                                 "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key":
+ *                                 "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": {
+ *                                 "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
+ *                             </code>
+ *                      </p>
+ *                   </li>
+ *                </ul>
  *                <note>
  *                   <p>Because each <code>Expression</code> can have only one operator, the
  *                         service returns an error if more than one is specified. The following
- *                         example shows an <code>Expression</code> object that creates an
- *                         error.</p>
+ *                         example shows an <code>Expression</code> object that creates an error:
+ *                             <code> { "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values":
+ *                             [ "DataTransfer" ] } } </code>
+ *                   </p>
+ *                   <p>The following is an example of the corresponding error message:
+ *                             <code>"Expression has more than one roots. Only one root operator is
+ *                             allowed for each expression: And, Or, Not, Dimensions, Tags,
+ *                             CostCategories"</code>
+ *                   </p>
  *                </note>
- *                <p>
- *                   <code> { "And": [ ... ], "DimensionValues": { "Dimension": "USAGE_TYPE",
- *                         "Values": [ "DataTransfer" ] } } </code>
- *                </p>
  *             </li>
  *          </ul>
  *          <note>
@@ -3335,49 +3316,116 @@ export interface AnomalyMonitor {
      */
     MonitorDimension?: MonitorDimension | string;
     /**
-     * <p>Use <code>Expression</code> to filter by cost or by usage. There are two patterns: </p>
+     * <p>Use <code>Expression</code> to filter in various Cost Explorer APIs.</p>
+     *          <p>Not all <code>Expression</code> types are supported in each API. Refer to the
+     *             documentation for each specific API to see what is supported.</p>
+     *          <p>There are two patterns:</p>
      *          <ul>
      *             <li>
-     *                <p>Simple dimension values - You can set the dimension name and values for the
-     *                     filters that you plan to use. For example, you can filter for
-     *                         <code>REGION==us-east-1 OR REGION==us-west-1</code>. For
-     *                         <code>GetRightsizingRecommendation</code>, the Region is a full name (for
-     *                     example, <code>REGION==US East (N. Virginia)</code>. The <code>Expression</code>
-     *                     example is as follows:</p>
-     *                <p>
-     *                   <code>{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", “us-west-1” ]
-     *                         } }</code>
-     *                </p>
-     *                <p>The list of dimension values are OR'd together to retrieve cost or usage data.
-     *                     You can create <code>Expression</code> and <code>DimensionValues</code> objects
-     *                     using either <code>with*</code> methods or <code>set*</code> methods in multiple
-     *                     lines. </p>
-     *             </li>
-     *             <li>
-     *                <p>Compound dimension values with logical operations - You can use multiple
-     *                         <code>Expression</code> types and the logical operators
-     *                         <code>AND/OR/NOT</code> to create a list of one or more
-     *                         <code>Expression</code> objects. By doing this, you can filter on more
-     *                     advanced options. For example, you can filter on <code>((REGION == us-east-1 OR
-     *                         REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
-     *                         DataTransfer)</code>. The <code>Expression</code> for that is as
-     *                     follows:</p>
-     *                <p>
-     *                   <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
-     *                         "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values":
-     *                         ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values":
-     *                         ["DataTransfer"] }}} ] } </code>
-     *                </p>
+     *                <p>Simple dimension values.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>There are three types of simple dimension values:
+     *                                 <code>CostCategories</code>, <code>Tags</code>, and
+     *                                 <code>Dimensions</code>.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>Specify the <code>CostCategories</code> field to define a
+     *                                     filter that acts on Cost Categories.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Tags</code> field to define a filter that
+     *                                     acts on Cost Allocation Tags.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Dimensions</code> field to define a filter
+     *                                     that acts on the <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DimensionValues.html">
+     *                                  <code>DimensionValues</code>
+     *                               </a>.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>For each filter type, you can set the dimension name and values for
+     *                             the filters that you plan to use.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for <code>REGION==us-east-1 OR
+     *                                         REGION==us-west-1</code>. For
+     *                                         <code>GetRightsizingRecommendation</code>, the Region is a
+     *                                     full name (for example, <code>REGION==US East (N.
+     *                                         Virginia)</code>.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key": "REGION", "Values": [
+     *                                         "us-east-1", “us-west-1” ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                         <li>
+     *                            <p>As shown in the previous example, lists of dimension values
+     *                                     are combined with <code>OR</code> when applying the
+     *                                     filter.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>You can also set different match options to further control how the
+     *                             filter behaves. Not all APIs support match options. Refer to the
+     *                             documentation for each specific API to see what is supported.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for linked account names that
+     *                                     start with “a”.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key":
+     *                                         "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ],
+     *                                         "Values": [ "a" ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                </ul>
+     *             </li>
+     *             <li>
+     *                <p>Compound <code>Expression</code> types with logical operations.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>You can use multiple <code>Expression</code> types and the logical
+     *                             operators <code>AND/OR/NOT</code> to create a list of one or more
+     *                                 <code>Expression</code> objects. By doing this, you can filter by
+     *                             more advanced options.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>For example, you can filter by <code>((REGION == us-east-1 OR REGION
+     *                                 == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
+     *                                 DataTransfer)</code>.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>The corresponding <code>Expression</code> for this example is as
+     *                             follows: <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION",
+     *                                 "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key":
+     *                                 "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": {
+     *                                 "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
+     *                             </code>
+     *                      </p>
+     *                   </li>
+     *                </ul>
      *                <note>
      *                   <p>Because each <code>Expression</code> can have only one operator, the
      *                         service returns an error if more than one is specified. The following
-     *                         example shows an <code>Expression</code> object that creates an
-     *                         error.</p>
+     *                         example shows an <code>Expression</code> object that creates an error:
+     *                             <code> { "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values":
+     *                             [ "DataTransfer" ] } } </code>
+     *                   </p>
+     *                   <p>The following is an example of the corresponding error message:
+     *                             <code>"Expression has more than one roots. Only one root operator is
+     *                             allowed for each expression: And, Or, Not, Dimensions, Tags,
+     *                             CostCategories"</code>
+     *                   </p>
      *                </note>
-     *                <p>
-     *                   <code> { "And": [ ... ], "DimensionValues": { "Dimension": "USAGE_TYPE",
-     *                         "Values": [ "DataTransfer" ] } } </code>
-     *                </p>
      *             </li>
      *          </ul>
      *          <note>
@@ -3397,6 +3445,94 @@ export interface AnomalyMonitor {
      */
     DimensionalValueCount?: number;
 }
+/**
+ * <p>The association between a monitor, threshold, and list of subscribers used to deliver
+ *             notifications about anomalies detected by a monitor that exceeds a threshold. The
+ *             content consists of the detailed metadata and the current status of the
+ *                 <code>AnomalySubscription</code> object. </p>
+ */
+export interface AnomalySubscription {
+    /**
+     * <p>The <code>AnomalySubscription</code> Amazon Resource Name (ARN). </p>
+     */
+    SubscriptionArn?: string;
+    /**
+     * <p>Your unique account identifier. </p>
+     */
+    AccountId?: string;
+    /**
+     * <p>A list of cost anomaly monitors. </p>
+     */
+    MonitorArnList: string[] | undefined;
+    /**
+     * <p>A list of subscribers to notify. </p>
+     */
+    Subscribers: Subscriber[] | undefined;
+    /**
+     * @deprecated
+     *
+     * <p>(deprecated)</p>
+     *          <p>The dollar value that triggers a notification if the threshold is exceeded. </p>
+     *          <p>This field has been deprecated. To specify a threshold, use ThresholdExpression.
+     *             Continued use of Threshold will be treated as shorthand syntax for a
+     *             ThresholdExpression.</p>
+     *          <p>One of Threshold or ThresholdExpression is required for this resource.</p>
+     */
+    Threshold?: number;
+    /**
+     * <p>The frequency that anomaly reports are sent over email. </p>
+     */
+    Frequency: AnomalySubscriptionFrequency | string | undefined;
+    /**
+     * <p>The name for the subscription. </p>
+     */
+    SubscriptionName: string | undefined;
+    /**
+     * <p>An <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_Expression.html">Expression</a>
+     *             object used to specify the anomalies that you want to generate alerts for. This supports
+     *             dimensions and nested expressions. The supported dimensions are
+     *                 <code>ANOMALY_TOTAL_IMPACT_ABSOLUTE</code> and
+     *                 <code>ANOMALY_TOTAL_IMPACT_PERCENTAGE</code>. The supported nested expression types
+     *             are <code>AND</code> and <code>OR</code>. The match option
+     *                 <code>GREATER_THAN_OR_EQUAL</code> is required. Values must be numbers between 0 and
+     *             10,000,000,000.</p>
+     *          <p>One of Threshold or ThresholdExpression is required for this resource.</p>
+     *          <p>The following are examples of valid ThresholdExpressions:</p>
+     *          <ul>
+     *             <li>
+     *                <p>Absolute threshold: <code>{ "Dimensions": { "Key":
+     *                         "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL"
+     *                         ], "Values": [ "100" ] } }</code>
+     *                </p>
+     *             </li>
+     *             <li>
+     *                <p>Percentage threshold: <code>{ "Dimensions": { "Key":
+     *                         "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL"
+     *                         ], "Values": [ "100" ] } }</code>
+     *                </p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>AND</code> two thresholds together: <code>{ "And": [ { "Dimensions": {
+     *                         "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
+     *                         "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, { "Dimensions": { "Key":
+     *                         "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL"
+     *                         ], "Values": [ "100" ] } } ] }</code>
+     *                </p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>OR</code> two thresholds together: <code>{ "Or": [ { "Dimensions": {
+     *                         "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
+     *                         "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, { "Dimensions": { "Key":
+     *                         "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL"
+     *                         ], "Values": [ "100" ] } } ] }</code>
+     *                </p>
+     *             </li>
+     *          </ul>
+     */
+    ThresholdExpression?: Expression;
+}
 /**
  * <p>Rules are processed in order. If there are multiple rules that match the line item,
  *             then the first rule to match is used to determine that Cost Category value.</p>
@@ -3590,49 +3726,116 @@ export interface GetCostCategoriesRequest {
      */
     CostCategoryName?: string;
     /**
-     * <p>Use <code>Expression</code> to filter by cost or by usage. There are two patterns: </p>
+     * <p>Use <code>Expression</code> to filter in various Cost Explorer APIs.</p>
+     *          <p>Not all <code>Expression</code> types are supported in each API. Refer to the
+     *             documentation for each specific API to see what is supported.</p>
+     *          <p>There are two patterns:</p>
      *          <ul>
      *             <li>
-     *                <p>Simple dimension values - You can set the dimension name and values for the
-     *                     filters that you plan to use. For example, you can filter for
-     *                         <code>REGION==us-east-1 OR REGION==us-west-1</code>. For
-     *                         <code>GetRightsizingRecommendation</code>, the Region is a full name (for
-     *                     example, <code>REGION==US East (N. Virginia)</code>. The <code>Expression</code>
-     *                     example is as follows:</p>
-     *                <p>
-     *                   <code>{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", “us-west-1” ]
-     *                         } }</code>
-     *                </p>
-     *                <p>The list of dimension values are OR'd together to retrieve cost or usage data.
-     *                     You can create <code>Expression</code> and <code>DimensionValues</code> objects
-     *                     using either <code>with*</code> methods or <code>set*</code> methods in multiple
-     *                     lines. </p>
-     *             </li>
-     *             <li>
-     *                <p>Compound dimension values with logical operations - You can use multiple
-     *                         <code>Expression</code> types and the logical operators
-     *                         <code>AND/OR/NOT</code> to create a list of one or more
-     *                         <code>Expression</code> objects. By doing this, you can filter on more
-     *                     advanced options. For example, you can filter on <code>((REGION == us-east-1 OR
-     *                         REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
-     *                         DataTransfer)</code>. The <code>Expression</code> for that is as
-     *                     follows:</p>
-     *                <p>
-     *                   <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
-     *                         "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values":
-     *                         ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values":
-     *                         ["DataTransfer"] }}} ] } </code>
-     *                </p>
+     *                <p>Simple dimension values.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>There are three types of simple dimension values:
+     *                                 <code>CostCategories</code>, <code>Tags</code>, and
+     *                                 <code>Dimensions</code>.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>Specify the <code>CostCategories</code> field to define a
+     *                                     filter that acts on Cost Categories.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Tags</code> field to define a filter that
+     *                                     acts on Cost Allocation Tags.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Dimensions</code> field to define a filter
+     *                                     that acts on the <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DimensionValues.html">
+     *                                  <code>DimensionValues</code>
+     *                               </a>.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>For each filter type, you can set the dimension name and values for
+     *                             the filters that you plan to use.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for <code>REGION==us-east-1 OR
+     *                                         REGION==us-west-1</code>. For
+     *                                         <code>GetRightsizingRecommendation</code>, the Region is a
+     *                                     full name (for example, <code>REGION==US East (N.
+     *                                         Virginia)</code>.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key": "REGION", "Values": [
+     *                                         "us-east-1", “us-west-1” ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                         <li>
+     *                            <p>As shown in the previous example, lists of dimension values
+     *                                     are combined with <code>OR</code> when applying the
+     *                                     filter.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>You can also set different match options to further control how the
+     *                             filter behaves. Not all APIs support match options. Refer to the
+     *                             documentation for each specific API to see what is supported.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for linked account names that
+     *                                     start with “a”.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key":
+     *                                         "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ],
+     *                                         "Values": [ "a" ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                </ul>
+     *             </li>
+     *             <li>
+     *                <p>Compound <code>Expression</code> types with logical operations.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>You can use multiple <code>Expression</code> types and the logical
+     *                             operators <code>AND/OR/NOT</code> to create a list of one or more
+     *                                 <code>Expression</code> objects. By doing this, you can filter by
+     *                             more advanced options.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>For example, you can filter by <code>((REGION == us-east-1 OR REGION
+     *                                 == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
+     *                                 DataTransfer)</code>.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>The corresponding <code>Expression</code> for this example is as
+     *                             follows: <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION",
+     *                                 "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key":
+     *                                 "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": {
+     *                                 "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
+     *                             </code>
+     *                      </p>
+     *                   </li>
+     *                </ul>
      *                <note>
      *                   <p>Because each <code>Expression</code> can have only one operator, the
      *                         service returns an error if more than one is specified. The following
-     *                         example shows an <code>Expression</code> object that creates an
-     *                         error.</p>
+     *                         example shows an <code>Expression</code> object that creates an error:
+     *                             <code> { "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values":
+     *                             [ "DataTransfer" ] } } </code>
+     *                   </p>
+     *                   <p>The following is an example of the corresponding error message:
+     *                             <code>"Expression has more than one roots. Only one root operator is
+     *                             allowed for each expression: And, Or, Not, Dimensions, Tags,
+     *                             CostCategories"</code>
+     *                   </p>
      *                </note>
-     *                <p>
-     *                   <code> { "And": [ ... ], "DimensionValues": { "Dimension": "USAGE_TYPE",
-     *                         "Values": [ "DataTransfer" ] } } </code>
-     *                </p>
      *             </li>
      *          </ul>
      *          <note>
@@ -4075,49 +4278,116 @@ export interface GetDimensionValuesRequest {
      */
     Context?: Context | string;
     /**
-     * <p>Use <code>Expression</code> to filter by cost or by usage. There are two patterns: </p>
+     * <p>Use <code>Expression</code> to filter in various Cost Explorer APIs.</p>
+     *          <p>Not all <code>Expression</code> types are supported in each API. Refer to the
+     *             documentation for each specific API to see what is supported.</p>
+     *          <p>There are two patterns:</p>
      *          <ul>
      *             <li>
-     *                <p>Simple dimension values - You can set the dimension name and values for the
-     *                     filters that you plan to use. For example, you can filter for
-     *                         <code>REGION==us-east-1 OR REGION==us-west-1</code>. For
-     *                         <code>GetRightsizingRecommendation</code>, the Region is a full name (for
-     *                     example, <code>REGION==US East (N. Virginia)</code>. The <code>Expression</code>
-     *                     example is as follows:</p>
-     *                <p>
-     *                   <code>{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", “us-west-1” ]
-     *                         } }</code>
-     *                </p>
-     *                <p>The list of dimension values are OR'd together to retrieve cost or usage data.
-     *                     You can create <code>Expression</code> and <code>DimensionValues</code> objects
-     *                     using either <code>with*</code> methods or <code>set*</code> methods in multiple
-     *                     lines. </p>
-     *             </li>
-     *             <li>
-     *                <p>Compound dimension values with logical operations - You can use multiple
-     *                         <code>Expression</code> types and the logical operators
-     *                         <code>AND/OR/NOT</code> to create a list of one or more
-     *                         <code>Expression</code> objects. By doing this, you can filter on more
-     *                     advanced options. For example, you can filter on <code>((REGION == us-east-1 OR
-     *                         REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
-     *                         DataTransfer)</code>. The <code>Expression</code> for that is as
-     *                     follows:</p>
-     *                <p>
-     *                   <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
-     *                         "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values":
-     *                         ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values":
-     *                         ["DataTransfer"] }}} ] } </code>
-     *                </p>
+     *                <p>Simple dimension values.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>There are three types of simple dimension values:
+     *                                 <code>CostCategories</code>, <code>Tags</code>, and
+     *                                 <code>Dimensions</code>.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>Specify the <code>CostCategories</code> field to define a
+     *                                     filter that acts on Cost Categories.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Tags</code> field to define a filter that
+     *                                     acts on Cost Allocation Tags.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Dimensions</code> field to define a filter
+     *                                     that acts on the <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DimensionValues.html">
+     *                                  <code>DimensionValues</code>
+     *                               </a>.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>For each filter type, you can set the dimension name and values for
+     *                             the filters that you plan to use.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for <code>REGION==us-east-1 OR
+     *                                         REGION==us-west-1</code>. For
+     *                                         <code>GetRightsizingRecommendation</code>, the Region is a
+     *                                     full name (for example, <code>REGION==US East (N.
+     *                                         Virginia)</code>.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key": "REGION", "Values": [
+     *                                         "us-east-1", “us-west-1” ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                         <li>
+     *                            <p>As shown in the previous example, lists of dimension values
+     *                                     are combined with <code>OR</code> when applying the
+     *                                     filter.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>You can also set different match options to further control how the
+     *                             filter behaves. Not all APIs support match options. Refer to the
+     *                             documentation for each specific API to see what is supported.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for linked account names that
+     *                                     start with “a”.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key":
+     *                                         "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ],
+     *                                         "Values": [ "a" ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                </ul>
+     *             </li>
+     *             <li>
+     *                <p>Compound <code>Expression</code> types with logical operations.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>You can use multiple <code>Expression</code> types and the logical
+     *                             operators <code>AND/OR/NOT</code> to create a list of one or more
+     *                                 <code>Expression</code> objects. By doing this, you can filter by
+     *                             more advanced options.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>For example, you can filter by <code>((REGION == us-east-1 OR REGION
+     *                                 == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
+     *                                 DataTransfer)</code>.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>The corresponding <code>Expression</code> for this example is as
+     *                             follows: <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION",
+     *                                 "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key":
+     *                                 "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": {
+     *                                 "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
+     *                             </code>
+     *                      </p>
+     *                   </li>
+     *                </ul>
      *                <note>
      *                   <p>Because each <code>Expression</code> can have only one operator, the
      *                         service returns an error if more than one is specified. The following
-     *                         example shows an <code>Expression</code> object that creates an
-     *                         error.</p>
+     *                         example shows an <code>Expression</code> object that creates an error:
+     *                             <code> { "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values":
+     *                             [ "DataTransfer" ] } } </code>
+     *                   </p>
+     *                   <p>The following is an example of the corresponding error message:
+     *                             <code>"Expression has more than one roots. Only one root operator is
+     *                             allowed for each expression: And, Or, Not, Dimensions, Tags,
+     *                             CostCategories"</code>
+     *                   </p>
      *                </note>
-     *                <p>
-     *                   <code> { "And": [ ... ], "DimensionValues": { "Dimension": "USAGE_TYPE",
-     *                         "Values": [ "DataTransfer" ] } } </code>
-     *                </p>
      *             </li>
      *          </ul>
      *          <note>
@@ -4394,49 +4664,116 @@ export interface GetReservationPurchaseRecommendationRequest {
      */
     Service: string | undefined;
     /**
-     * <p>Use <code>Expression</code> to filter by cost or by usage. There are two patterns: </p>
+     * <p>Use <code>Expression</code> to filter in various Cost Explorer APIs.</p>
+     *          <p>Not all <code>Expression</code> types are supported in each API. Refer to the
+     *             documentation for each specific API to see what is supported.</p>
+     *          <p>There are two patterns:</p>
      *          <ul>
      *             <li>
-     *                <p>Simple dimension values - You can set the dimension name and values for the
-     *                     filters that you plan to use. For example, you can filter for
-     *                         <code>REGION==us-east-1 OR REGION==us-west-1</code>. For
-     *                         <code>GetRightsizingRecommendation</code>, the Region is a full name (for
-     *                     example, <code>REGION==US East (N. Virginia)</code>. The <code>Expression</code>
-     *                     example is as follows:</p>
-     *                <p>
-     *                   <code>{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", “us-west-1” ]
-     *                         } }</code>
-     *                </p>
-     *                <p>The list of dimension values are OR'd together to retrieve cost or usage data.
-     *                     You can create <code>Expression</code> and <code>DimensionValues</code> objects
-     *                     using either <code>with*</code> methods or <code>set*</code> methods in multiple
-     *                     lines. </p>
-     *             </li>
-     *             <li>
-     *                <p>Compound dimension values with logical operations - You can use multiple
-     *                         <code>Expression</code> types and the logical operators
-     *                         <code>AND/OR/NOT</code> to create a list of one or more
-     *                         <code>Expression</code> objects. By doing this, you can filter on more
-     *                     advanced options. For example, you can filter on <code>((REGION == us-east-1 OR
-     *                         REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
-     *                         DataTransfer)</code>. The <code>Expression</code> for that is as
-     *                     follows:</p>
-     *                <p>
-     *                   <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
-     *                         "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values":
-     *                         ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values":
-     *                         ["DataTransfer"] }}} ] } </code>
-     *                </p>
+     *                <p>Simple dimension values.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>There are three types of simple dimension values:
+     *                                 <code>CostCategories</code>, <code>Tags</code>, and
+     *                                 <code>Dimensions</code>.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>Specify the <code>CostCategories</code> field to define a
+     *                                     filter that acts on Cost Categories.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Tags</code> field to define a filter that
+     *                                     acts on Cost Allocation Tags.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Dimensions</code> field to define a filter
+     *                                     that acts on the <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DimensionValues.html">
+     *                                  <code>DimensionValues</code>
+     *                               </a>.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>For each filter type, you can set the dimension name and values for
+     *                             the filters that you plan to use.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for <code>REGION==us-east-1 OR
+     *                                         REGION==us-west-1</code>. For
+     *                                         <code>GetRightsizingRecommendation</code>, the Region is a
+     *                                     full name (for example, <code>REGION==US East (N.
+     *                                         Virginia)</code>.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key": "REGION", "Values": [
+     *                                         "us-east-1", “us-west-1” ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                         <li>
+     *                            <p>As shown in the previous example, lists of dimension values
+     *                                     are combined with <code>OR</code> when applying the
+     *                                     filter.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>You can also set different match options to further control how the
+     *                             filter behaves. Not all APIs support match options. Refer to the
+     *                             documentation for each specific API to see what is supported.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for linked account names that
+     *                                     start with “a”.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key":
+     *                                         "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ],
+     *                                         "Values": [ "a" ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                </ul>
+     *             </li>
+     *             <li>
+     *                <p>Compound <code>Expression</code> types with logical operations.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>You can use multiple <code>Expression</code> types and the logical
+     *                             operators <code>AND/OR/NOT</code> to create a list of one or more
+     *                                 <code>Expression</code> objects. By doing this, you can filter by
+     *                             more advanced options.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>For example, you can filter by <code>((REGION == us-east-1 OR REGION
+     *                                 == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
+     *                                 DataTransfer)</code>.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>The corresponding <code>Expression</code> for this example is as
+     *                             follows: <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION",
+     *                                 "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key":
+     *                                 "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": {
+     *                                 "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
+     *                             </code>
+     *                      </p>
+     *                   </li>
+     *                </ul>
      *                <note>
      *                   <p>Because each <code>Expression</code> can have only one operator, the
      *                         service returns an error if more than one is specified. The following
-     *                         example shows an <code>Expression</code> object that creates an
-     *                         error.</p>
+     *                         example shows an <code>Expression</code> object that creates an error:
+     *                             <code> { "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values":
+     *                             [ "DataTransfer" ] } } </code>
+     *                   </p>
+     *                   <p>The following is an example of the corresponding error message:
+     *                             <code>"Expression has more than one roots. Only one root operator is
+     *                             allowed for each expression: And, Or, Not, Dimensions, Tags,
+     *                             CostCategories"</code>
+     *                   </p>
      *                </note>
-     *                <p>
-     *                   <code> { "And": [ ... ], "DimensionValues": { "Dimension": "USAGE_TYPE",
-     *                         "Values": [ "DataTransfer" ] } } </code>
-     *                </p>
      *             </li>
      *          </ul>
      *          <note>
@@ -4663,49 +5000,116 @@ export interface GetReservationUtilizationRequest {
 }
 export interface GetRightsizingRecommendationRequest {
     /**
-     * <p>Use <code>Expression</code> to filter by cost or by usage. There are two patterns: </p>
+     * <p>Use <code>Expression</code> to filter in various Cost Explorer APIs.</p>
+     *          <p>Not all <code>Expression</code> types are supported in each API. Refer to the
+     *             documentation for each specific API to see what is supported.</p>
+     *          <p>There are two patterns:</p>
      *          <ul>
      *             <li>
-     *                <p>Simple dimension values - You can set the dimension name and values for the
-     *                     filters that you plan to use. For example, you can filter for
-     *                         <code>REGION==us-east-1 OR REGION==us-west-1</code>. For
-     *                         <code>GetRightsizingRecommendation</code>, the Region is a full name (for
-     *                     example, <code>REGION==US East (N. Virginia)</code>. The <code>Expression</code>
-     *                     example is as follows:</p>
-     *                <p>
-     *                   <code>{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", “us-west-1” ]
-     *                         } }</code>
-     *                </p>
-     *                <p>The list of dimension values are OR'd together to retrieve cost or usage data.
-     *                     You can create <code>Expression</code> and <code>DimensionValues</code> objects
-     *                     using either <code>with*</code> methods or <code>set*</code> methods in multiple
-     *                     lines. </p>
-     *             </li>
-     *             <li>
-     *                <p>Compound dimension values with logical operations - You can use multiple
-     *                         <code>Expression</code> types and the logical operators
-     *                         <code>AND/OR/NOT</code> to create a list of one or more
-     *                         <code>Expression</code> objects. By doing this, you can filter on more
-     *                     advanced options. For example, you can filter on <code>((REGION == us-east-1 OR
-     *                         REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
-     *                         DataTransfer)</code>. The <code>Expression</code> for that is as
-     *                     follows:</p>
-     *                <p>
-     *                   <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
-     *                         "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values":
-     *                         ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values":
-     *                         ["DataTransfer"] }}} ] } </code>
-     *                </p>
+     *                <p>Simple dimension values.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>There are three types of simple dimension values:
+     *                                 <code>CostCategories</code>, <code>Tags</code>, and
+     *                                 <code>Dimensions</code>.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>Specify the <code>CostCategories</code> field to define a
+     *                                     filter that acts on Cost Categories.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Tags</code> field to define a filter that
+     *                                     acts on Cost Allocation Tags.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Dimensions</code> field to define a filter
+     *                                     that acts on the <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DimensionValues.html">
+     *                                  <code>DimensionValues</code>
+     *                               </a>.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>For each filter type, you can set the dimension name and values for
+     *                             the filters that you plan to use.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for <code>REGION==us-east-1 OR
+     *                                         REGION==us-west-1</code>. For
+     *                                         <code>GetRightsizingRecommendation</code>, the Region is a
+     *                                     full name (for example, <code>REGION==US East (N.
+     *                                         Virginia)</code>.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key": "REGION", "Values": [
+     *                                         "us-east-1", “us-west-1” ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                         <li>
+     *                            <p>As shown in the previous example, lists of dimension values
+     *                                     are combined with <code>OR</code> when applying the
+     *                                     filter.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>You can also set different match options to further control how the
+     *                             filter behaves. Not all APIs support match options. Refer to the
+     *                             documentation for each specific API to see what is supported.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for linked account names that
+     *                                     start with “a”.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key":
+     *                                         "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ],
+     *                                         "Values": [ "a" ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                </ul>
+     *             </li>
+     *             <li>
+     *                <p>Compound <code>Expression</code> types with logical operations.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>You can use multiple <code>Expression</code> types and the logical
+     *                             operators <code>AND/OR/NOT</code> to create a list of one or more
+     *                                 <code>Expression</code> objects. By doing this, you can filter by
+     *                             more advanced options.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>For example, you can filter by <code>((REGION == us-east-1 OR REGION
+     *                                 == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
+     *                                 DataTransfer)</code>.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>The corresponding <code>Expression</code> for this example is as
+     *                             follows: <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION",
+     *                                 "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key":
+     *                                 "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": {
+     *                                 "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
+     *                             </code>
+     *                      </p>
+     *                   </li>
+     *                </ul>
      *                <note>
      *                   <p>Because each <code>Expression</code> can have only one operator, the
      *                         service returns an error if more than one is specified. The following
-     *                         example shows an <code>Expression</code> object that creates an
-     *                         error.</p>
+     *                         example shows an <code>Expression</code> object that creates an error:
+     *                             <code> { "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values":
+     *                             [ "DataTransfer" ] } } </code>
+     *                   </p>
+     *                   <p>The following is an example of the corresponding error message:
+     *                             <code>"Expression has more than one roots. Only one root operator is
+     *                             allowed for each expression: And, Or, Not, Dimensions, Tags,
+     *                             CostCategories"</code>
+     *                   </p>
      *                </note>
-     *                <p>
-     *                   <code> { "And": [ ... ], "DimensionValues": { "Dimension": "USAGE_TYPE",
-     *                         "Values": [ "DataTransfer" ] } } </code>
-     *                </p>
      *             </li>
      *          </ul>
      *          <note>
@@ -5109,49 +5513,116 @@ export interface GetTagsRequest {
      */
     TagKey?: string;
     /**
-     * <p>Use <code>Expression</code> to filter by cost or by usage. There are two patterns: </p>
+     * <p>Use <code>Expression</code> to filter in various Cost Explorer APIs.</p>
+     *          <p>Not all <code>Expression</code> types are supported in each API. Refer to the
+     *             documentation for each specific API to see what is supported.</p>
+     *          <p>There are two patterns:</p>
      *          <ul>
      *             <li>
-     *                <p>Simple dimension values - You can set the dimension name and values for the
-     *                     filters that you plan to use. For example, you can filter for
-     *                         <code>REGION==us-east-1 OR REGION==us-west-1</code>. For
-     *                         <code>GetRightsizingRecommendation</code>, the Region is a full name (for
-     *                     example, <code>REGION==US East (N. Virginia)</code>. The <code>Expression</code>
-     *                     example is as follows:</p>
-     *                <p>
-     *                   <code>{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1", “us-west-1” ]
-     *                         } }</code>
-     *                </p>
-     *                <p>The list of dimension values are OR'd together to retrieve cost or usage data.
-     *                     You can create <code>Expression</code> and <code>DimensionValues</code> objects
-     *                     using either <code>with*</code> methods or <code>set*</code> methods in multiple
-     *                     lines. </p>
-     *             </li>
-     *             <li>
-     *                <p>Compound dimension values with logical operations - You can use multiple
-     *                         <code>Expression</code> types and the logical operators
-     *                         <code>AND/OR/NOT</code> to create a list of one or more
-     *                         <code>Expression</code> objects. By doing this, you can filter on more
-     *                     advanced options. For example, you can filter on <code>((REGION == us-east-1 OR
-     *                         REGION == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
-     *                         DataTransfer)</code>. The <code>Expression</code> for that is as
-     *                     follows:</p>
-     *                <p>
-     *                   <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
-     *                         "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName", "Values":
-     *                         ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key": "USAGE_TYPE", "Values":
-     *                         ["DataTransfer"] }}} ] } </code>
-     *                </p>
+     *                <p>Simple dimension values.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>There are three types of simple dimension values:
+     *                                 <code>CostCategories</code>, <code>Tags</code>, and
+     *                                 <code>Dimensions</code>.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>Specify the <code>CostCategories</code> field to define a
+     *                                     filter that acts on Cost Categories.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Tags</code> field to define a filter that
+     *                                     acts on Cost Allocation Tags.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>Specify the <code>Dimensions</code> field to define a filter
+     *                                     that acts on the <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DimensionValues.html">
+     *                                  <code>DimensionValues</code>
+     *                               </a>.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>For each filter type, you can set the dimension name and values for
+     *                             the filters that you plan to use.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for <code>REGION==us-east-1 OR
+     *                                         REGION==us-west-1</code>. For
+     *                                         <code>GetRightsizingRecommendation</code>, the Region is a
+     *                                     full name (for example, <code>REGION==US East (N.
+     *                                         Virginia)</code>.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key": "REGION", "Values": [
+     *                                         "us-east-1", “us-west-1” ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                         <li>
+     *                            <p>As shown in the previous example, lists of dimension values
+     *                                     are combined with <code>OR</code> when applying the
+     *                                     filter.</p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                   <li>
+     *                      <p>You can also set different match options to further control how the
+     *                             filter behaves. Not all APIs support match options. Refer to the
+     *                             documentation for each specific API to see what is supported.</p>
+     *                      <ul>
+     *                         <li>
+     *                            <p>For example, you can filter for linked account names that
+     *                                     start with “a”.</p>
+     *                         </li>
+     *                         <li>
+     *                            <p>The corresponding <code>Expression</code> for this example is
+     *                                     as follows: <code>{ "Dimensions": { "Key":
+     *                                         "LINKED_ACCOUNT_NAME", "MatchOptions": [ "STARTS_WITH" ],
+     *                                         "Values": [ "a" ] } }</code>
+     *                            </p>
+     *                         </li>
+     *                      </ul>
+     *                   </li>
+     *                </ul>
+     *             </li>
+     *             <li>
+     *                <p>Compound <code>Expression</code> types with logical operations.</p>
+     *                <ul>
+     *                   <li>
+     *                      <p>You can use multiple <code>Expression</code> types and the logical
+     *                             operators <code>AND/OR/NOT</code> to create a list of one or more
+     *                                 <code>Expression</code> objects. By doing this, you can filter by
+     *                             more advanced options.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>For example, you can filter by <code>((REGION == us-east-1 OR REGION
+     *                                 == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
+     *                                 DataTransfer)</code>.</p>
+     *                   </li>
+     *                   <li>
+     *                      <p>The corresponding <code>Expression</code> for this example is as
+     *                             follows: <code>{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION",
+     *                                 "Values": [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key":
+     *                                 "TagName", "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": {
+     *                                 "Key": "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] }
+     *                             </code>
+     *                      </p>
+     *                   </li>
+     *                </ul>
      *                <note>
      *                   <p>Because each <code>Expression</code> can have only one operator, the
      *                         service returns an error if more than one is specified. The following
-     *                         example shows an <code>Expression</code> object that creates an
-     *                         error.</p>
+     *                         example shows an <code>Expression</code> object that creates an error:
+     *                             <code> { "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values":
+     *                             [ "DataTransfer" ] } } </code>
+     *                   </p>
+     *                   <p>The following is an example of the corresponding error message:
+     *                             <code>"Expression has more than one roots. Only one root operator is
+     *                             allowed for each expression: And, Or, Not, Dimensions, Tags,
+     *                             CostCategories"</code>
+     *                   </p>
      *                </note>
-     *                <p>
-     *                   <code> { "And": [ ... ], "DimensionValues": { "Dimension": "USAGE_TYPE",
-     *                         "Values": [ "DataTransfer" ] } } </code>
-     *                </p>
      *             </li>
      *          </ul>
      *          <note>
@@ -5387,6 +5858,77 @@ export interface GetUsageForecastRequest {
      */
     PredictionIntervalLevel?: number;
 }
+export interface UpdateAnomalySubscriptionRequest {
+    /**
+     * <p>A cost anomaly subscription Amazon Resource Name (ARN). </p>
+     */
+    SubscriptionArn: string | undefined;
+    /**
+     * @deprecated
+     *
+     * <p>(deprecated)</p>
+     *          <p>The update to the threshold value for receiving notifications. </p>
+     *          <p>This field has been deprecated. To update a threshold, use ThresholdExpression. Continued
+     *       use of Threshold will be treated as shorthand syntax for a ThresholdExpression.</p>
+     */
+    Threshold?: number;
+    /**
+     * <p>The update to the frequency value that subscribers receive notifications. </p>
+     */
+    Frequency?: AnomalySubscriptionFrequency | string;
+    /**
+     * <p>A list of cost anomaly monitor ARNs. </p>
+     */
+    MonitorArnList?: string[];
+    /**
+     * <p>The update to the subscriber list. </p>
+     */
+    Subscribers?: Subscriber[];
+    /**
+     * <p>The new name of the subscription. </p>
+     */
+    SubscriptionName?: string;
+    /**
+     * <p>The update to the <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_Expression.html">Expression</a> object
+     *       used to specify the anomalies that you want to generate alerts for. This supports dimensions
+     *       and nested expressions. The supported dimensions are
+     *         <code>ANOMALY_TOTAL_IMPACT_ABSOLUTE</code> and <code>ANOMALY_TOTAL_IMPACT_PERCENTAGE</code>.
+     *       The supported nested expression types are <code>AND</code> and <code>OR</code>. The match
+     *       option <code>GREATER_THAN_OR_EQUAL</code> is required. Values must be numbers between 0 and
+     *       10,000,000,000.</p>
+     *          <p>The following are examples of valid ThresholdExpressions:</p>
+     *          <ul>
+     *             <li>
+     *                <p>Absolute threshold: <code>{ "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE",
+     *             "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }</code>
+     *                </p>
+     *             </li>
+     *             <li>
+     *                <p>Percentage threshold: <code>{ "Dimensions": { "Key":
+     *             "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ],
+     *             "Values": [ "100" ] } }</code>
+     *                </p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>AND</code> two thresholds together: <code>{ "And": [ { "Dimensions": { "Key":
+     *             "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values":
+     *             [ "100" ] } }, { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
+     *             "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } } ] }</code>
+     *                </p>
+     *             </li>
+     *             <li>
+     *                <p>
+     *                   <code>OR</code> two thresholds together: <code>{ "Or": [ { "Dimensions": { "Key":
+     *             "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values":
+     *             [ "100" ] } }, { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
+     *             "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } } ] }</code>
+     *                </p>
+     *             </li>
+     *          </ul>
+     */
+    ThresholdExpression?: Expression;
+}
 export interface CreateAnomalyMonitorRequest {
     /**
      * <p>The cost anomaly detection monitor object that you want to create.</p>
@@ -5429,6 +5971,48 @@ export interface CreateAnomalyMonitorRequest {
      */
     ResourceTags?: ResourceTag[];
 }
+export interface CreateAnomalySubscriptionRequest {
+    /**
+     * <p>The cost anomaly subscription object that you want to create. </p>
+     */
+    AnomalySubscription: AnomalySubscription | undefined;
+    /**
+     * <p>An optional list of tags to associate with the specified <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_AnomalySubscription.html">
+     *                <code>AnomalySubscription</code>
+     *             </a>. You can use resource tags to control access to
+     *       your <code>subscription</code> using IAM policies.</p>
+     *          <p>Each tag consists of a key and a value, and each key must be unique for the resource. The
+     *       following restrictions apply to resource tags:</p>
+     *          <ul>
+     *             <li>
+     *                <p>Although the maximum number of array members is 200, you can assign a maximum of 50
+     *           user-tags to one resource. The remaining are reserved for Amazon Web Services use</p>
+     *             </li>
+     *             <li>
+     *                <p>The maximum length of a key is 128 characters</p>
+     *             </li>
+     *             <li>
+     *                <p>The maximum length of a value is 256 characters</p>
+     *             </li>
+     *             <li>
+     *                <p>Keys and values can only contain alphanumeric characters, spaces, and any of the
+     *           following: <code>_.:/=+@-</code>
+     *                </p>
+     *             </li>
+     *             <li>
+     *                <p>Keys and values are case sensitive</p>
+     *             </li>
+     *             <li>
+     *                <p>Keys and values are trimmed for any leading or trailing whitespaces</p>
+     *             </li>
+     *             <li>
+     *                <p>Don’t use <code>aws:</code> as a prefix for your keys. This prefix is reserved for
+     *             Amazon Web Services use</p>
+     *             </li>
+     *          </ul>
+     */
+    ResourceTags?: ResourceTag[];
+}
 /**
  * <p>The structure of Cost Categories. This includes detailed metadata and the set of rules
  *             for the <code>CostCategory</code> object.</p>
@@ -5552,6 +6136,18 @@ export interface GetAnomalyMonitorsResponse {
      */
     NextPageToken?: string;
 }
+export interface GetAnomalySubscriptionsResponse {
+    /**
+     * <p>A list of cost anomaly subscriptions that includes the detailed metadata for each one.
+     *     </p>
+     */
+    AnomalySubscriptions: AnomalySubscription[] | undefined;
+    /**
+     * <p>The token to retrieve the next set of results. Amazon Web Services provides the token when
+     *       the response from a previous call has more results than the maximum page size. </p>
+     */
+    NextPageToken?: string;
+}
 export interface UpdateCostCategoryDefinitionRequest {
     /**
      * <p>The unique identifier for your Cost Category.</p>
@@ -5625,10 +6221,6 @@ export declare const TagValuesFilterSensitiveLog: (obj: TagValues) => any;
  * @internal
  */
 export declare const SubscriberFilterSensitiveLog: (obj: Subscriber) => any;
-/**
- * @internal
- */
-export declare const AnomalySubscriptionFilterSensitiveLog: (obj: AnomalySubscription) => any;
 /**
  * @internal
  */
@@ -5637,10 +6229,6 @@ export declare const ResourceTagFilterSensitiveLog: (obj: ResourceTag) => any;
  * @internal
  */
 export declare const CreateAnomalyMonitorResponseFilterSensitiveLog: (obj: CreateAnomalyMonitorResponse) => any;
-/**
- * @internal
- */
-export declare const CreateAnomalySubscriptionRequestFilterSensitiveLog: (obj: CreateAnomalySubscriptionRequest) => any;
 /**
  * @internal
  */
@@ -5713,10 +6301,6 @@ export declare const GetAnomalyMonitorsRequestFilterSensitiveLog: (obj: GetAnoma
  * @internal
  */
 export declare const GetAnomalySubscriptionsRequestFilterSensitiveLog: (obj: GetAnomalySubscriptionsRequest) => any;
-/**
- * @internal
- */
-export declare const GetAnomalySubscriptionsResponseFilterSensitiveLog: (obj: GetAnomalySubscriptionsResponse) => any;
 /**
  * @internal
  */
@@ -6089,10 +6673,6 @@ export declare const UpdateAnomalyMonitorRequestFilterSensitiveLog: (obj: Update
  * @internal
  */
 export declare const UpdateAnomalyMonitorResponseFilterSensitiveLog: (obj: UpdateAnomalyMonitorResponse) => any;
-/**
- * @internal
- */
-export declare const UpdateAnomalySubscriptionRequestFilterSensitiveLog: (obj: UpdateAnomalySubscriptionRequest) => any;
 /**
  * @internal
  */
@@ -6125,6 +6705,10 @@ export declare const ExpressionFilterSensitiveLog: (obj: Expression) => any;
  * @internal
  */
 export declare const AnomalyMonitorFilterSensitiveLog: (obj: AnomalyMonitor) => any;
+/**
+ * @internal
+ */
+export declare const AnomalySubscriptionFilterSensitiveLog: (obj: AnomalySubscription) => any;
 /**
  * @internal
  */
@@ -6189,10 +6773,18 @@ export declare const GetTagsRequestFilterSensitiveLog: (obj: GetTagsRequest) =>
  * @internal
  */
 export declare const GetUsageForecastRequestFilterSensitiveLog: (obj: GetUsageForecastRequest) => any;
+/**
+ * @internal
+ */
+export declare const UpdateAnomalySubscriptionRequestFilterSensitiveLog: (obj: UpdateAnomalySubscriptionRequest) => any;
 /**
  * @internal
  */
 export declare const CreateAnomalyMonitorRequestFilterSensitiveLog: (obj: CreateAnomalyMonitorRequest) => any;
+/**
+ * @internal
+ */
+export declare const CreateAnomalySubscriptionRequestFilterSensitiveLog: (obj: CreateAnomalySubscriptionRequest) => any;
 /**
  * @internal
  */
@@ -6205,6 +6797,10 @@ export declare const CreateCostCategoryDefinitionRequestFilterSensitiveLog: (obj
  * @internal
  */
 export declare const GetAnomalyMonitorsResponseFilterSensitiveLog: (obj: GetAnomalyMonitorsResponse) => any;
+/**
+ * @internal
+ */
+export declare const GetAnomalySubscriptionsResponseFilterSensitiveLog: (obj: GetAnomalySubscriptionsResponse) => any;
 /**
  * @internal
  */