@aws-sdk/client-cost-explorer 3.817.0 → 3.821.0

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

@@ -1682,6 +1682,35 @@ export declare class RequestChangedException extends __BaseException {
      */
     constructor(opts: __ExceptionOptionType<RequestChangedException, __BaseException>);
 }
+/**
+ * <p>Contains cost or usage metric values for comparing two time periods. Each value
+ *             includes amounts for the baseline and comparison time periods, their difference, and the
+ *             unit of measurement.</p>
+ * @public
+ */
+export interface ComparisonMetricValue {
+    /**
+     * <p>The numeric value for the baseline time period measurement.</p>
+     * @public
+     */
+    BaselineTimePeriodAmount?: string | undefined;
+    /**
+     * <p>The numeric value for the comparison time period measurement.</p>
+     * @public
+     */
+    ComparisonTimePeriodAmount?: string | undefined;
+    /**
+     * <p>The calculated difference between <code>ComparisonTimePeriodAmount</code> and
+     *                 <code>BaselineTimePeriodAmount</code>.</p>
+     * @public
+     */
+    Difference?: string | undefined;
+    /**
+     * <p>The unit of measurement applicable to all numeric values in this comparison.</p>
+     * @public
+     */
+    Unit?: string | undefined;
+}
 /**
  * @public
  */
@@ -1771,6 +1800,34 @@ export interface GetCostCategoriesResponse {
      */
     TotalSize: number | undefined;
 }
+/**
+ * <p>Represents factors that contribute to cost variations between the baseline and
+ *             comparison time periods, including the type of driver, an identifier of the driver, and
+ *             associated metrics.</p>
+ * @public
+ */
+export interface CostDriver {
+    /**
+     * <p>The category or classification of the cost driver.</p>
+     *          <p>Values include: BUNDLED_DISCOUNT, CREDIT, OUT_OF_CYCLE_CHARGE, REFUND,
+     *             RECURRING_RESERVATION_FEE, RESERVATION_USAGE, RI_VOLUME_DISCOUNT, SAVINGS_PLAN_USAGE,
+     *             SAVINGS_PLAN_NEGATION, SAVINGS_PLAN_RECURRING_FEE, SUPPORT_FEE, TAX,
+     *             UPFRONT_RESERVATION_FEE, USAGE_CHANGE, COMMITMENT</p>
+     * @public
+     */
+    Type?: string | undefined;
+    /**
+     * <p>The specific identifier of the cost driver.</p>
+     * @public
+     */
+    Name?: string | undefined;
+    /**
+     * <p>A mapping of metric names to their comparison values, measuring the impact of this
+     *             cost driver.</p>
+     * @public
+     */
+    Metrics?: Record<string, ComparisonMetricValue> | undefined;
+}
 /**
  * @public
  * @enum
@@ -5554,6 +5611,143 @@ export interface AnomalySubscription {
      */
     ThresholdExpression?: Expression | undefined;
 }
+/**
+ * <p>Represents a comparison of cost and usage metrics between two time periods.</p>
+ * @public
+ */
+export interface CostAndUsageComparison {
+    /**
+     * <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.</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:
+     *                             <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>
+     *             </li>
+     *          </ul>
+     *          <note>
+     *             <p>For the <code>GetRightsizingRecommendation</code> action, a combination of OR and
+     *                 NOT isn't supported. OR isn't supported between different dimensions, or dimensions
+     *                 and tags. NOT operators aren't supported. Dimensions are also limited to
+     *                     <code>LINKED_ACCOUNT</code>, <code>REGION</code>, or
+     *                     <code>RIGHTSIZING_TYPE</code>.</p>
+     *             <p>For the <code>GetReservationPurchaseRecommendation</code> action, only NOT is
+     *                 supported. AND and OR aren't supported. Dimensions are limited to
+     *                     <code>LINKED_ACCOUNT</code>.</p>
+     *          </note>
+     * @public
+     */
+    CostAndUsageSelector?: Expression | undefined;
+    /**
+     * <p>A mapping of metric names to their comparison values.</p>
+     * @public
+     */
+    Metrics?: Record<string, ComparisonMetricValue> | undefined;
+}
 /**
  * <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>
@@ -5601,102 +5795,426 @@ export interface CostCategoryRule {
     Type?: CostCategoryRuleType | undefined;
 }
 /**
+ * <p>Represents a collection of cost drivers and their associated metrics for cost
+ *             comparison analysis.</p>
  * @public
  */
-export interface GetCostAndUsageRequest {
-    /**
-     * <p>Sets the start date and end date for retrieving Amazon Web Services costs. The start
-     *       date is inclusive, but the end date is exclusive. For example, if <code>start</code> is
-     *         <code>2017-01-01</code> and <code>end</code> is <code>2017-05-01</code>, then the cost and
-     *       usage data is retrieved from <code>2017-01-01</code> up to and including
-     *         <code>2017-04-30</code> but not including <code>2017-05-01</code>.</p>
-     * @public
-     */
-    TimePeriod: DateInterval | undefined;
-    /**
-     * <p>Sets the Amazon Web Services cost granularity to <code>MONTHLY</code> or
-     *         <code>DAILY</code>, or <code>HOURLY</code>. If <code>Granularity</code> isn't set, the
-     *       response object doesn't include the <code>Granularity</code>, either <code>MONTHLY</code> or
-     *         <code>DAILY</code>, or <code>HOURLY</code>. </p>
-     * @public
-     */
-    Granularity: Granularity | undefined;
-    /**
-     * <p>Filters Amazon Web Services costs by different dimensions. For example, you can specify
-     *         <code>SERVICE</code> and <code>LINKED_ACCOUNT</code> and get the costs that are associated
-     *       with that account's usage of that service. You can nest <code>Expression</code> objects to
-     *       define any combination of dimension filters. For more information, see <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_Expression.html">Expression</a>. </p>
-     *          <p>Valid values for <code>MatchOptions</code> for <code>Dimensions</code> are
-     *         <code>EQUALS</code> and <code>CASE_SENSITIVE</code>.</p>
-     *          <p>Valid values for <code>MatchOptions</code> for <code>CostCategories</code> and
-     *         <code>Tags</code> are <code>EQUALS</code>, <code>ABSENT</code>, and
-     *         <code>CASE_SENSITIVE</code>. Default values are <code>EQUALS</code> and
-     *         <code>CASE_SENSITIVE</code>.</p>
-     * @public
-     */
-    Filter?: Expression | undefined;
-    /**
-     * <p>Which metrics are returned in the query. For more information about blended and
-     *       unblended rates, see <a href="http://aws.amazon.com/premiumsupport/knowledge-center/blended-rates-intro/">Why does the "blended" annotation
-     *         appear on some line items in my bill?</a>. </p>
-     *          <p>Valid values are <code>AmortizedCost</code>, <code>BlendedCost</code>,
-     *         <code>NetAmortizedCost</code>, <code>NetUnblendedCost</code>,
-     *         <code>NormalizedUsageAmount</code>, <code>UnblendedCost</code>, and
-     *         <code>UsageQuantity</code>. </p>
-     *          <note>
-     *             <p>If you return the <code>UsageQuantity</code> metric, the service aggregates all usage
-     *         numbers without taking into account the units. For example, if you aggregate
-     *           <code>usageQuantity</code> across all of Amazon EC2, the results aren't meaningful because
-     *         Amazon EC2 compute hours and data transfer are measured in different units (for example,
-     *         hours and GB). To get more meaningful <code>UsageQuantity</code> metrics, filter by
-     *           <code>UsageType</code> or <code>UsageTypeGroups</code>. </p>
-     *          </note>
-     *          <p>
-     *             <code>Metrics</code> is required for <code>GetCostAndUsage</code> requests.</p>
-     * @public
-     */
-    Metrics: string[] | undefined;
-    /**
-     * <p>You can group Amazon Web Services costs using up to two different groups, either
-     *       dimensions, tag keys, cost categories, or any two group by types.</p>
-     *          <p>Valid values for the <code>DIMENSION</code> type are <code>AZ</code>,
-     *         <code>INSTANCE_TYPE</code>, <code>LEGAL_ENTITY_NAME</code>, <code>INVOICING_ENTITY</code>,
-     *         <code>LINKED_ACCOUNT</code>, <code>OPERATION</code>, <code>PLATFORM</code>,
-     *         <code>PURCHASE_TYPE</code>, <code>SERVICE</code>, <code>TENANCY</code>,
-     *         <code>RECORD_TYPE</code>, and <code>USAGE_TYPE</code>.</p>
-     *          <p>When you group by the <code>TAG</code> type and include a valid tag key, you get all
-     *       tag values, including empty strings.</p>
-     * @public
-     */
-    GroupBy?: GroupDefinition[] | undefined;
-    /**
-     * <p>The Amazon Resource Name (ARN) that uniquely identifies a specific billing view. The ARN
-     *       is used to specify which particular billing view you want to interact with or retrieve
-     *       information from when making API calls related to Amazon Web Services Billing and Cost
-     *       Management features. The BillingViewArn can be retrieved by calling the ListBillingViews
-     *       API.</p>
-     * @public
-     */
-    BillingViewArn?: string | 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>
-     * @public
-     */
-    NextPageToken?: string | undefined;
-}
-/**
- * @public
- */
-export interface GetCostAndUsageWithResourcesRequest {
+export interface CostComparisonDriver {
     /**
-     * <p>Sets the start and end dates for retrieving Amazon Web Services costs. The range must
-     *       be within the last 14 days (the start date cannot be earlier than 14 days ago). The start date
-     *       is inclusive, but the end date is exclusive. For example, if <code>start</code> is
-     *         <code>2017-01-01</code> and <code>end</code> is <code>2017-05-01</code>, then the cost and
-     *       usage data is retrieved from <code>2017-01-01</code> up to and including
-     *         <code>2017-04-30</code> but not including <code>2017-05-01</code>.</p>
-     * @public
+     * <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.</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:
+     *                             <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>
+     *             </li>
+     *          </ul>
+     *          <note>
+     *             <p>For the <code>GetRightsizingRecommendation</code> action, a combination of OR and
+     *                 NOT isn't supported. OR isn't supported between different dimensions, or dimensions
+     *                 and tags. NOT operators aren't supported. Dimensions are also limited to
+     *                     <code>LINKED_ACCOUNT</code>, <code>REGION</code>, or
+     *                     <code>RIGHTSIZING_TYPE</code>.</p>
+     *             <p>For the <code>GetReservationPurchaseRecommendation</code> action, only NOT is
+     *                 supported. AND and OR aren't supported. Dimensions are limited to
+     *                     <code>LINKED_ACCOUNT</code>.</p>
+     *          </note>
+     * @public
+     */
+    CostSelector?: Expression | undefined;
+    /**
+     * <p>A mapping of metric names to their comparison values.</p>
+     * @public
+     */
+    Metrics?: Record<string, ComparisonMetricValue> | undefined;
+    /**
+     * <p>An array of cost drivers, each representing a cost difference between the baseline and
+     *             comparison time periods. Each entry also includes a metric delta (for example, usage
+     *             change) that contributed to the cost variance, along with the identifier and type of
+     *             change.</p>
+     * @public
+     */
+    CostDrivers?: CostDriver[] | undefined;
+}
+/**
+ * @public
+ */
+export interface GetCostAndUsageComparisonsRequest {
+    /**
+     * <p>The Amazon Resource Name (ARN) that uniquely identifies a specific billing view. The ARN
+     *       is used to specify which particular billing view you want to interact with or retrieve
+     *       information from when making API calls related to Amazon Web Services Billing and Cost
+     *       Management features. The BillingViewArn can be retrieved by calling the ListBillingViews
+     *       API.</p>
+     * @public
+     */
+    BillingViewArn?: string | undefined;
+    /**
+     * <p>The reference time period for comparison. This time period serves as the baseline against
+     *       which other cost and usage data will be compared. The interval must start and end on the first
+     *       day of a month, with a duration of exactly one month.</p>
+     * @public
+     */
+    BaselineTimePeriod: DateInterval | undefined;
+    /**
+     * <p>The comparison time period for analysis. This time period's cost and usage data will be
+     *       compared against the baseline time period. The interval must start and end on the first day of
+     *       a month, with a duration of exactly one month.</p>
+     * @public
+     */
+    ComparisonTimePeriod: DateInterval | undefined;
+    /**
+     * <p>The cost and usage metric to compare. Valid values are <code>AmortizedCost</code>,
+     *         <code>BlendedCost</code>, <code>NetAmortizedCost</code>, <code>NetUnblendedCost</code>,
+     *         <code>NormalizedUsageAmount</code>, <code>UnblendedCost</code>, and
+     *         <code>UsageQuantity</code>.</p>
+     * @public
+     */
+    MetricForComparison: string | undefined;
+    /**
+     * <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.</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:
+     *                             <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>
+     *             </li>
+     *          </ul>
+     *          <note>
+     *             <p>For the <code>GetRightsizingRecommendation</code> action, a combination of OR and
+     *                 NOT isn't supported. OR isn't supported between different dimensions, or dimensions
+     *                 and tags. NOT operators aren't supported. Dimensions are also limited to
+     *                     <code>LINKED_ACCOUNT</code>, <code>REGION</code>, or
+     *                     <code>RIGHTSIZING_TYPE</code>.</p>
+     *             <p>For the <code>GetReservationPurchaseRecommendation</code> action, only NOT is
+     *                 supported. AND and OR aren't supported. Dimensions are limited to
+     *                     <code>LINKED_ACCOUNT</code>.</p>
+     *          </note>
+     * @public
+     */
+    Filter?: Expression | undefined;
+    /**
+     * <p>You can group results using the attributes <code>DIMENSION</code>, <code>TAG</code>, and
+     *         <code>COST_CATEGORY</code>. </p>
+     * @public
+     */
+    GroupBy?: GroupDefinition[] | undefined;
+    /**
+     * <p>The maximum number of results that are returned for the request.</p>
+     * @public
+     */
+    MaxResults?: number | undefined;
+    /**
+     * <p>The token to retrieve the next set of paginated results.</p>
+     * @public
+     */
+    NextPageToken?: string | undefined;
+}
+/**
+ * @public
+ */
+export interface GetCostAndUsageRequest {
+    /**
+     * <p>Sets the start date and end date for retrieving Amazon Web Services costs. The start
+     *       date is inclusive, but the end date is exclusive. For example, if <code>start</code> is
+     *         <code>2017-01-01</code> and <code>end</code> is <code>2017-05-01</code>, then the cost and
+     *       usage data is retrieved from <code>2017-01-01</code> up to and including
+     *         <code>2017-04-30</code> but not including <code>2017-05-01</code>.</p>
+     * @public
+     */
+    TimePeriod: DateInterval | undefined;
+    /**
+     * <p>Sets the Amazon Web Services cost granularity to <code>MONTHLY</code> or
+     *         <code>DAILY</code>, or <code>HOURLY</code>. If <code>Granularity</code> isn't set, the
+     *       response object doesn't include the <code>Granularity</code>, either <code>MONTHLY</code> or
+     *         <code>DAILY</code>, or <code>HOURLY</code>. </p>
+     * @public
+     */
+    Granularity: Granularity | undefined;
+    /**
+     * <p>Filters Amazon Web Services costs by different dimensions. For example, you can specify
+     *         <code>SERVICE</code> and <code>LINKED_ACCOUNT</code> and get the costs that are associated
+     *       with that account's usage of that service. You can nest <code>Expression</code> objects to
+     *       define any combination of dimension filters. For more information, see <a href="https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_Expression.html">Expression</a>. </p>
+     *          <p>Valid values for <code>MatchOptions</code> for <code>Dimensions</code> are
+     *         <code>EQUALS</code> and <code>CASE_SENSITIVE</code>.</p>
+     *          <p>Valid values for <code>MatchOptions</code> for <code>CostCategories</code> and
+     *         <code>Tags</code> are <code>EQUALS</code>, <code>ABSENT</code>, and
+     *         <code>CASE_SENSITIVE</code>. Default values are <code>EQUALS</code> and
+     *         <code>CASE_SENSITIVE</code>.</p>
+     * @public
+     */
+    Filter?: Expression | undefined;
+    /**
+     * <p>Which metrics are returned in the query. For more information about blended and
+     *       unblended rates, see <a href="http://aws.amazon.com/premiumsupport/knowledge-center/blended-rates-intro/">Why does the "blended" annotation
+     *         appear on some line items in my bill?</a>. </p>
+     *          <p>Valid values are <code>AmortizedCost</code>, <code>BlendedCost</code>,
+     *         <code>NetAmortizedCost</code>, <code>NetUnblendedCost</code>,
+     *         <code>NormalizedUsageAmount</code>, <code>UnblendedCost</code>, and
+     *         <code>UsageQuantity</code>. </p>
+     *          <note>
+     *             <p>If you return the <code>UsageQuantity</code> metric, the service aggregates all usage
+     *         numbers without taking into account the units. For example, if you aggregate
+     *           <code>usageQuantity</code> across all of Amazon EC2, the results aren't meaningful because
+     *         Amazon EC2 compute hours and data transfer are measured in different units (for example,
+     *         hours and GB). To get more meaningful <code>UsageQuantity</code> metrics, filter by
+     *           <code>UsageType</code> or <code>UsageTypeGroups</code>. </p>
+     *          </note>
+     *          <p>
+     *             <code>Metrics</code> is required for <code>GetCostAndUsage</code> requests.</p>
+     * @public
+     */
+    Metrics: string[] | undefined;
+    /**
+     * <p>You can group Amazon Web Services costs using up to two different groups, either
+     *       dimensions, tag keys, cost categories, or any two group by types.</p>
+     *          <p>Valid values for the <code>DIMENSION</code> type are <code>AZ</code>,
+     *         <code>INSTANCE_TYPE</code>, <code>LEGAL_ENTITY_NAME</code>, <code>INVOICING_ENTITY</code>,
+     *         <code>LINKED_ACCOUNT</code>, <code>OPERATION</code>, <code>PLATFORM</code>,
+     *         <code>PURCHASE_TYPE</code>, <code>SERVICE</code>, <code>TENANCY</code>,
+     *         <code>RECORD_TYPE</code>, and <code>USAGE_TYPE</code>.</p>
+     *          <p>When you group by the <code>TAG</code> type and include a valid tag key, you get all
+     *       tag values, including empty strings.</p>
+     * @public
+     */
+    GroupBy?: GroupDefinition[] | undefined;
+    /**
+     * <p>The Amazon Resource Name (ARN) that uniquely identifies a specific billing view. The ARN
+     *       is used to specify which particular billing view you want to interact with or retrieve
+     *       information from when making API calls related to Amazon Web Services Billing and Cost
+     *       Management features. The BillingViewArn can be retrieved by calling the ListBillingViews
+     *       API.</p>
+     * @public
+     */
+    BillingViewArn?: string | 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>
+     * @public
+     */
+    NextPageToken?: string | undefined;
+}
+/**
+ * @public
+ */
+export interface GetCostAndUsageWithResourcesRequest {
+    /**
+     * <p>Sets the start and end dates for retrieving Amazon Web Services costs. The range must
+     *       be within the last 14 days (the start date cannot be earlier than 14 days ago). The start date
+     *       is inclusive, but the end date is exclusive. For example, if <code>start</code> is
+     *         <code>2017-01-01</code> and <code>end</code> is <code>2017-05-01</code>, then the cost and
+     *       usage data is retrieved from <code>2017-01-01</code> up to and including
+     *         <code>2017-04-30</code> but not including <code>2017-05-01</code>.</p>
+     * @public
      */
     TimePeriod: DateInterval | undefined;
     /**
@@ -5987,6 +6505,185 @@ export interface GetCostCategoriesRequest {
      */
     NextPageToken?: string | undefined;
 }
+/**
+ * @public
+ */
+export interface GetCostComparisonDriversRequest {
+    /**
+     * <p>The Amazon Resource Name (ARN) that uniquely identifies a specific billing view. The ARN
+     *       is used to specify which particular billing view you want to interact with or retrieve
+     *       information from when making API calls related to Amazon Web Services Billing and Cost
+     *       Management features. The BillingViewArn can be retrieved by calling the ListBillingViews
+     *       API.</p>
+     * @public
+     */
+    BillingViewArn?: string | undefined;
+    /**
+     * <p>The reference time period for comparison. This time period serves as the baseline against
+     *       which other cost and usage data will be compared. The interval must start and end on the first
+     *       day of a month, with a duration of exactly one month.</p>
+     * @public
+     */
+    BaselineTimePeriod: DateInterval | undefined;
+    /**
+     * <p>The comparison time period for analysis. This time period's cost and usage data will be
+     *       compared against the baseline time period. The interval must start and end on the first day of
+     *       a month, with a duration of exactly one month.</p>
+     * @public
+     */
+    ComparisonTimePeriod: DateInterval | undefined;
+    /**
+     * <p>The cost and usage metric to compare. Valid values are <code>AmortizedCost</code>,
+     *         <code>BlendedCost</code>, <code>NetAmortizedCost</code>, <code>NetUnblendedCost</code>,
+     *         <code>NormalizedUsageAmount</code>, <code>UnblendedCost</code>, and
+     *         <code>UsageQuantity</code>.</p>
+     * @public
+     */
+    MetricForComparison: string | undefined;
+    /**
+     * <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.</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:
+     *                             <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>
+     *             </li>
+     *          </ul>
+     *          <note>
+     *             <p>For the <code>GetRightsizingRecommendation</code> action, a combination of OR and
+     *                 NOT isn't supported. OR isn't supported between different dimensions, or dimensions
+     *                 and tags. NOT operators aren't supported. Dimensions are also limited to
+     *                     <code>LINKED_ACCOUNT</code>, <code>REGION</code>, or
+     *                     <code>RIGHTSIZING_TYPE</code>.</p>
+     *             <p>For the <code>GetReservationPurchaseRecommendation</code> action, only NOT is
+     *                 supported. AND and OR aren't supported. Dimensions are limited to
+     *                     <code>LINKED_ACCOUNT</code>.</p>
+     *          </note>
+     * @public
+     */
+    Filter?: Expression | undefined;
+    /**
+     * <p>You can group results using the attributes <code>DIMENSION</code>, <code>TAG</code>, and
+     *         <code>COST_CATEGORY</code>. Note that <code>SERVICE</code> and <code>USAGE_TYPE</code>
+     *       dimensions are automatically included in the cost comparison drivers analysis.</p>
+     * @public
+     */
+    GroupBy?: GroupDefinition[] | undefined;
+    /**
+     * <p>The maximum number of results that are returned for the request.</p>
+     * @public
+     */
+    MaxResults?: number | undefined;
+    /**
+     * <p>The token to retrieve the next set of paginated results.</p>
+     * @public
+     */
+    NextPageToken?: string | undefined;
+}
 /**
  * @public
  */
@@ -8429,6 +9126,46 @@ export interface GetAnomalySubscriptionsResponse {
      */
     NextPageToken?: string | undefined;
 }
+/**
+ * @public
+ */
+export interface GetCostAndUsageComparisonsResponse {
+    /**
+     * <p>An array of comparison results showing cost and usage metrics between
+     *         <code>BaselineTimePeriod</code> and <code>ComparisonTimePeriod</code>.</p>
+     * @public
+     */
+    CostAndUsageComparisons?: CostAndUsageComparison[] | undefined;
+    /**
+     * <p>A summary of the total cost and usage, comparing amounts between
+     *         <code>BaselineTimePeriod</code> and <code>ComparisonTimePeriod</code> and their differences.
+     *       This total represents the aggregate total across all paginated results, if the response spans
+     *       multiple pages.</p>
+     * @public
+     */
+    TotalCostAndUsage?: Record<string, ComparisonMetricValue> | undefined;
+    /**
+     * <p>The token to retrieve the next set of paginated results.</p>
+     * @public
+     */
+    NextPageToken?: string | undefined;
+}
+/**
+ * @public
+ */
+export interface GetCostComparisonDriversResponse {
+    /**
+     * <p>An array of comparison results showing factors that drive significant cost differences
+     *       between <code>BaselineTimePeriod</code> and <code>ComparisonTimePeriod</code>.</p>
+     * @public
+     */
+    CostComparisonDrivers?: CostComparisonDriver[] | undefined;
+    /**
+     * <p>The token to retrieve the next set of paginated results.</p>
+     * @public
+     */
+    NextPageToken?: string | undefined;
+}
 /**
  * @public
  */