aws-sdk-costexplorer 1.113.0 → 1.115.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (7) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG.md +10 -0
  3. data/VERSION +1 -1
  4. data/lib/aws-sdk-costexplorer/client.rb +74 -96
  5. data/lib/aws-sdk-costexplorer/types.rb +108 -142
  6. data/lib/aws-sdk-costexplorer.rb +1 -1
  7. metadata +2 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: fd39c8bae42de08c72756b4e0ed087d81cc4bc129fd770a25983bc21fddf90da
4
- data.tar.gz: c2f43457b8a6ac9aadbe7c7c04bb36a5530a04f90d86dc42ec14d65b19c4c2ad
3
+ metadata.gz: 0dbea5b3bd8cd3e7760d1887f05abec59afcf5f4b58a555e61e7ddddca22ac60
4
+ data.tar.gz: dd73334488e38185a68e8e5aae8fc42505ee45e5ca789aefe5274d8cd9574cc5
5
5
  SHA512:
6
- metadata.gz: 2ad334de51ad951f6dad266f75497807a4ea3b31e211ea674e69b1b392e486bde140f15e02040fb273a3e931fe3544d790968d940757228b3139249813b10160
7
- data.tar.gz: b634a6648f1c4aa3f09ca738c8fd148558622658408c59cd1ea44c06badc96a1467d9720ecedf8153bbfbe0c7772d9dc4d6c69097ab9df304c5a3be1e38655a6
6
+ metadata.gz: d6b1981333575697ac13a4a6bf1ac6934df4a7264147f6b374fb555aecae6f8296b39b953fa0883e58fe710895fea1445087aba146c716d95e512c5cc4783cda
7
+ data.tar.gz: beb804457ed418f0af7e31f8c2e7805a6fc341960223e12637e70ba8215907fb22e001f50c36004a027857901ef46d5d01eca43e51267d75258d15740874cb2b
data/CHANGELOG.md CHANGED
@@ -1,6 +1,16 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.115.0 (2024-11-18)
5
+ ------------------
6
+
7
+ * Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
8
+
9
+ 1.114.0 (2024-11-06)
10
+ ------------------
11
+
12
+ * Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
13
+
4
14
  1.113.0 (2024-10-18)
5
15
  ------------------
6
16
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.113.0
1
+ 1.115.0
data/lib/aws-sdk-costexplorer/client.rb CHANGED
@@ -1655,7 +1655,6 @@ module Aws::CostExplorer
1655
1655
  #
1656
1656
  # * Specify the `Dimensions` field to define a filter that acts on
1657
1657
  # the [ `DimensionValues` ][1].
1658
- #
1659
1658
  # * For each filter type, you can set the dimension name and values
1660
1659
  # for the filters that you plan to use.
1661
1660
  #
@@ -1665,12 +1664,11 @@ module Aws::CostExplorer
1665
1664
  # Virginia)`.
1666
1665
  #
1667
1666
  # * The corresponding `Expression` for this example is as follows:
1668
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
1669
- # "us-west-1" ] \} \}`
1667
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
1668
+ # "us-west-1" ] } }`
1670
1669
  #
1671
1670
  # * As shown in the previous example, lists of dimension values are
1672
1671
  # combined with `OR` when applying the filter.
1673
- #
1674
1672
  # * You can also set different match options to further control how
1675
1673
  # the filter behaves. Not all APIs support match options. Refer to
1676
1674
  # the documentation for each specific API to see what is supported.
@@ -1679,9 +1677,8 @@ module Aws::CostExplorer
1679
1677
  # with "a".
1680
1678
  #
1681
1679
  # * The corresponding `Expression` for this example is as follows:
1682
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
1683
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
1684
- #
1680
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
1681
+ # [ "STARTS_WITH" ], "Values": [ "a" ] } }`
1685
1682
  # * Compound `Expression` types with logical operations.
1686
1683
  #
1687
1684
  # * You can use multiple `Expression` types and the logical operators
@@ -1692,17 +1689,16 @@ module Aws::CostExplorer
1692
1689
  # us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
1693
1690
  # DataTransfer)`.
1694
1691
  #
1695
- # * The corresponding `Expression` for this example is as follows: `\{
1696
- # "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION", "Values": [
1697
- # "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key": "TagName",
1698
- # "Values": ["Value1"] \} \} ]\}, \{"Not": \{"Dimensions": \{ "Key":
1699
- # "USAGE_TYPE", "Values": ["DataTransfer"] \}\}\} ] \} `
1700
- #
1692
+ # * The corresponding `Expression` for this example is as follows: `{
1693
+ # "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
1694
+ # "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
1695
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
1696
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
1701
1697
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
1702
1698
  # returns an error if more than one is specified. The following
1703
- # example shows an `Expression` object that creates an error: ` \{
1704
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
1705
- # "DataTransfer" ] \} \} `
1699
+ # example shows an `Expression` object that creates an error: ` {
1700
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
1701
+ # "DataTransfer" ] } } `
1706
1702
  #
1707
1703
  # The following is an example of the corresponding error message:
1708
1704
  # `"Expression has more than one roots. Only one root operator is
@@ -2201,7 +2197,6 @@ module Aws::CostExplorer
2201
2197
  #
2202
2198
  # * Specify the `Dimensions` field to define a filter that acts on
2203
2199
  # the [ `DimensionValues` ][1].
2204
- #
2205
2200
  # * For each filter type, you can set the dimension name and values
2206
2201
  # for the filters that you plan to use.
2207
2202
  #
@@ -2211,12 +2206,11 @@ module Aws::CostExplorer
2211
2206
  # Virginia)`.
2212
2207
  #
2213
2208
  # * The corresponding `Expression` for this example is as follows:
2214
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
2215
- # "us-west-1" ] \} \}`
2209
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
2210
+ # "us-west-1" ] } }`
2216
2211
  #
2217
2212
  # * As shown in the previous example, lists of dimension values are
2218
2213
  # combined with `OR` when applying the filter.
2219
- #
2220
2214
  # * You can also set different match options to further control how
2221
2215
  # the filter behaves. Not all APIs support match options. Refer to
2222
2216
  # the documentation for each specific API to see what is supported.
@@ -2225,9 +2219,8 @@ module Aws::CostExplorer
2225
2219
  # with "a".
2226
2220
  #
2227
2221
  # * The corresponding `Expression` for this example is as follows:
2228
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
2229
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
2230
- #
2222
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
2223
+ # [ "STARTS_WITH" ], "Values": [ "a" ] } }`
2231
2224
  # * Compound `Expression` types with logical operations.
2232
2225
  #
2233
2226
  # * You can use multiple `Expression` types and the logical operators
@@ -2238,17 +2231,16 @@ module Aws::CostExplorer
2238
2231
  # us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
2239
2232
  # DataTransfer)`.
2240
2233
  #
2241
- # * The corresponding `Expression` for this example is as follows: `\{
2242
- # "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION", "Values": [
2243
- # "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key": "TagName",
2244
- # "Values": ["Value1"] \} \} ]\}, \{"Not": \{"Dimensions": \{ "Key":
2245
- # "USAGE_TYPE", "Values": ["DataTransfer"] \}\}\} ] \} `
2246
- #
2234
+ # * The corresponding `Expression` for this example is as follows: `{
2235
+ # "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
2236
+ # "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
2237
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
2238
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
2247
2239
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
2248
2240
  # returns an error if more than one is specified. The following
2249
- # example shows an `Expression` object that creates an error: ` \{
2250
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
2251
- # "DataTransfer" ] \} \} `
2241
+ # example shows an `Expression` object that creates an error: ` {
2242
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
2243
+ # "DataTransfer" ] } } `
2252
2244
  #
2253
2245
  # The following is an example of the corresponding error message:
2254
2246
  # `"Expression has more than one roots. Only one root operator is
@@ -2711,7 +2703,6 @@ module Aws::CostExplorer
2711
2703
  #
2712
2704
  # * Specify the `Dimensions` field to define a filter that acts on
2713
2705
  # the [ `DimensionValues` ][1].
2714
- #
2715
2706
  # * For each filter type, you can set the dimension name and values
2716
2707
  # for the filters that you plan to use.
2717
2708
  #
@@ -2721,12 +2712,11 @@ module Aws::CostExplorer
2721
2712
  # Virginia)`.
2722
2713
  #
2723
2714
  # * The corresponding `Expression` for this example is as follows:
2724
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
2725
- # "us-west-1" ] \} \}`
2715
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
2716
+ # "us-west-1" ] } }`
2726
2717
  #
2727
2718
  # * As shown in the previous example, lists of dimension values are
2728
2719
  # combined with `OR` when applying the filter.
2729
- #
2730
2720
  # * You can also set different match options to further control how
2731
2721
  # the filter behaves. Not all APIs support match options. Refer to
2732
2722
  # the documentation for each specific API to see what is supported.
@@ -2735,9 +2725,8 @@ module Aws::CostExplorer
2735
2725
  # with "a".
2736
2726
  #
2737
2727
  # * The corresponding `Expression` for this example is as follows:
2738
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
2739
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
2740
- #
2728
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
2729
+ # [ "STARTS_WITH" ], "Values": [ "a" ] } }`
2741
2730
  # * Compound `Expression` types with logical operations.
2742
2731
  #
2743
2732
  # * You can use multiple `Expression` types and the logical operators
@@ -2748,17 +2737,16 @@ module Aws::CostExplorer
2748
2737
  # us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
2749
2738
  # DataTransfer)`.
2750
2739
  #
2751
- # * The corresponding `Expression` for this example is as follows: `\{
2752
- # "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION", "Values": [
2753
- # "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key": "TagName",
2754
- # "Values": ["Value1"] \} \} ]\}, \{"Not": \{"Dimensions": \{ "Key":
2755
- # "USAGE_TYPE", "Values": ["DataTransfer"] \}\}\} ] \} `
2756
- #
2740
+ # * The corresponding `Expression` for this example is as follows: `{
2741
+ # "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
2742
+ # "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
2743
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
2744
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
2757
2745
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
2758
2746
  # returns an error if more than one is specified. The following
2759
- # example shows an `Expression` object that creates an error: ` \{
2760
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
2761
- # "DataTransfer" ] \} \} `
2747
+ # example shows an `Expression` object that creates an error: ` {
2748
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
2749
+ # "DataTransfer" ] } } `
2762
2750
  #
2763
2751
  # The following is an example of the corresponding error message:
2764
2752
  # `"Expression has more than one roots. Only one root operator is
@@ -3232,7 +3220,6 @@ module Aws::CostExplorer
3232
3220
  #
3233
3221
  # * Specify the `Dimensions` field to define a filter that acts on
3234
3222
  # the [ `DimensionValues` ][1].
3235
- #
3236
3223
  # * For each filter type, you can set the dimension name and values
3237
3224
  # for the filters that you plan to use.
3238
3225
  #
@@ -3242,12 +3229,11 @@ module Aws::CostExplorer
3242
3229
  # Virginia)`.
3243
3230
  #
3244
3231
  # * The corresponding `Expression` for this example is as follows:
3245
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
3246
- # "us-west-1" ] \} \}`
3232
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
3233
+ # "us-west-1" ] } }`
3247
3234
  #
3248
3235
  # * As shown in the previous example, lists of dimension values are
3249
3236
  # combined with `OR` when applying the filter.
3250
- #
3251
3237
  # * You can also set different match options to further control how
3252
3238
  # the filter behaves. Not all APIs support match options. Refer to
3253
3239
  # the documentation for each specific API to see what is supported.
@@ -3256,9 +3242,8 @@ module Aws::CostExplorer
3256
3242
  # with "a".
3257
3243
  #
3258
3244
  # * The corresponding `Expression` for this example is as follows:
3259
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
3260
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
3261
- #
3245
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
3246
+ # [ "STARTS_WITH" ], "Values": [ "a" ] } }`
3262
3247
  # * Compound `Expression` types with logical operations.
3263
3248
  #
3264
3249
  # * You can use multiple `Expression` types and the logical operators
@@ -3269,17 +3254,16 @@ module Aws::CostExplorer
3269
3254
  # us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
3270
3255
  # DataTransfer)`.
3271
3256
  #
3272
- # * The corresponding `Expression` for this example is as follows: `\{
3273
- # "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION", "Values": [
3274
- # "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key": "TagName",
3275
- # "Values": ["Value1"] \} \} ]\}, \{"Not": \{"Dimensions": \{ "Key":
3276
- # "USAGE_TYPE", "Values": ["DataTransfer"] \}\}\} ] \} `
3277
- #
3257
+ # * The corresponding `Expression` for this example is as follows: `{
3258
+ # "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
3259
+ # "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
3260
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
3261
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
3278
3262
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
3279
3263
  # returns an error if more than one is specified. The following
3280
- # example shows an `Expression` object that creates an error: ` \{
3281
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
3282
- # "DataTransfer" ] \} \} `
3264
+ # example shows an `Expression` object that creates an error: ` {
3265
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
3266
+ # "DataTransfer" ] } } `
3283
3267
  #
3284
3268
  # The following is an example of the corresponding error message:
3285
3269
  # `"Expression has more than one roots. Only one root operator is
@@ -4210,7 +4194,6 @@ module Aws::CostExplorer
4210
4194
  #
4211
4195
  # * Specify the `Dimensions` field to define a filter that acts on
4212
4196
  # the [ `DimensionValues` ][1].
4213
- #
4214
4197
  # * For each filter type, you can set the dimension name and values
4215
4198
  # for the filters that you plan to use.
4216
4199
  #
@@ -4220,12 +4203,11 @@ module Aws::CostExplorer
4220
4203
  # Virginia)`.
4221
4204
  #
4222
4205
  # * The corresponding `Expression` for this example is as follows:
4223
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
4224
- # "us-west-1" ] \} \}`
4206
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
4207
+ # "us-west-1" ] } }`
4225
4208
  #
4226
4209
  # * As shown in the previous example, lists of dimension values are
4227
4210
  # combined with `OR` when applying the filter.
4228
- #
4229
4211
  # * You can also set different match options to further control how
4230
4212
  # the filter behaves. Not all APIs support match options. Refer to
4231
4213
  # the documentation for each specific API to see what is supported.
@@ -4234,9 +4216,8 @@ module Aws::CostExplorer
4234
4216
  # with "a".
4235
4217
  #
4236
4218
  # * The corresponding `Expression` for this example is as follows:
4237
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
4238
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
4239
- #
4219
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
4220
+ # [ "STARTS_WITH" ], "Values": [ "a" ] } }`
4240
4221
  # * Compound `Expression` types with logical operations.
4241
4222
  #
4242
4223
  # * You can use multiple `Expression` types and the logical operators
@@ -4247,17 +4228,16 @@ module Aws::CostExplorer
4247
4228
  # us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
4248
4229
  # DataTransfer)`.
4249
4230
  #
4250
- # * The corresponding `Expression` for this example is as follows: `\{
4251
- # "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION", "Values": [
4252
- # "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key": "TagName",
4253
- # "Values": ["Value1"] \} \} ]\}, \{"Not": \{"Dimensions": \{ "Key":
4254
- # "USAGE_TYPE", "Values": ["DataTransfer"] \}\}\} ] \} `
4255
- #
4231
+ # * The corresponding `Expression` for this example is as follows: `{
4232
+ # "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
4233
+ # "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
4234
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
4235
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
4256
4236
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
4257
4237
  # returns an error if more than one is specified. The following
4258
- # example shows an `Expression` object that creates an error: ` \{
4259
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
4260
- # "DataTransfer" ] \} \} `
4238
+ # example shows an `Expression` object that creates an error: ` {
4239
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
4240
+ # "DataTransfer" ] } } `
4261
4241
  #
4262
4242
  # The following is an example of the corresponding error message:
4263
4243
  # `"Expression has more than one roots. Only one root operator is
@@ -5095,27 +5075,25 @@ module Aws::CostExplorer
5095
5075
  #
5096
5076
  # The following are examples of valid ThresholdExpressions:
5097
5077
  #
5098
- # * Absolute threshold: `\{ "Dimensions": \{ "Key":
5078
+ # * Absolute threshold: `{ "Dimensions": { "Key":
5099
5079
  # "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
5100
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}`
5080
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }`
5101
5081
  #
5102
- # * Percentage threshold: `\{ "Dimensions": \{ "Key":
5082
+ # * Percentage threshold: `{ "Dimensions": { "Key":
5103
5083
  # "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [
5104
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}`
5084
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }`
5105
5085
  #
5106
- # * `AND` two thresholds together: `\{ "And": [ \{ "Dimensions": \{
5107
- # "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
5108
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}, \{
5109
- # "Dimensions": \{ "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
5110
- # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \}
5111
- # \} ] \}`
5086
+ # * `AND` two thresholds together: `{ "And": [ { "Dimensions": { "Key":
5087
+ # "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
5088
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, { "Dimensions":
5089
+ # { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [
5090
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } } ] }`
5112
5091
  #
5113
- # * `OR` two thresholds together: `\{ "Or": [ \{ "Dimensions": \{ "Key":
5092
+ # * `OR` two thresholds together: `{ "Or": [ { "Dimensions": { "Key":
5114
5093
  # "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
5115
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}, \{
5116
- # "Dimensions": \{ "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
5117
- # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \}
5118
- # \} ] \}`
5094
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, { "Dimensions":
5095
+ # { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [
5096
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } } ] }`
5119
5097
  #
5120
5098
  #
5121
5099
  #
@@ -5358,7 +5336,7 @@ module Aws::CostExplorer
5358
5336
  tracer: tracer
5359
5337
  )
5360
5338
  context[:gem_name] = 'aws-sdk-costexplorer'
5361
- context[:gem_version] = '1.113.0'
5339
+ context[:gem_version] = '1.115.0'
5362
5340
  Seahorse::Client::Request.new(handlers, context)
5363
5341
  end
5364
5342
 
data/lib/aws-sdk-costexplorer/types.rb CHANGED
@@ -140,7 +140,6 @@ module Aws::CostExplorer
140
140
  #
141
141
  # * Specify the `Dimensions` field to define a filter that acts on
142
142
  # the [ `DimensionValues` ][1].
143
- #
144
143
  # * For each filter type, you can set the dimension name and values
145
144
  # for the filters that you plan to use.
146
145
  #
@@ -150,12 +149,11 @@ module Aws::CostExplorer
150
149
  # Virginia)`.
151
150
  #
152
151
  # * The corresponding `Expression` for this example is as follows:
153
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
154
- # "us-west-1" ] \} \}`
152
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
153
+ # "us-west-1" ] } }`
155
154
  #
156
155
  # * As shown in the previous example, lists of dimension values
157
156
  # are combined with `OR` when applying the filter.
158
- #
159
157
  # * You can also set different match options to further control how
160
158
  # the filter behaves. Not all APIs support match options. Refer to
161
159
  # the documentation for each specific API to see what is
@@ -165,9 +163,8 @@ module Aws::CostExplorer
165
163
  # start with "a".
166
164
  #
167
165
  # * The corresponding `Expression` for this example is as follows:
168
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
169
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
170
- #
166
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
167
+ # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
171
168
  # * Compound `Expression` types with logical operations.
172
169
  #
173
170
  # * You can use multiple `Expression` types and the logical
@@ -180,17 +177,15 @@ module Aws::CostExplorer
180
177
  # DataTransfer)`.
181
178
  #
182
179
  # * The corresponding `Expression` for this example is as follows:
183
- # `\{ "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION",
184
- # "Values": [ "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key":
185
- # "TagName", "Values": ["Value1"] \} \} ]\}, \{"Not":
186
- # \{"Dimensions": \{ "Key": "USAGE_TYPE", "Values":
187
- # ["DataTransfer"] \}\}\} ] \} `
188
- #
180
+ # `{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values":
181
+ # [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
182
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
183
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
189
184
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
190
185
  # returns an error if more than one is specified. The following
191
- # example shows an `Expression` object that creates an error: ` \{
192
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
193
- # "DataTransfer" ] \} \} `
186
+ # example shows an `Expression` object that creates an error: ` {
187
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
188
+ # "DataTransfer" ] } } `
194
189
  #
195
190
  # The following is an example of the corresponding error message:
196
191
  # `"Expression has more than one roots. Only one root operator is
@@ -345,27 +340,27 @@ module Aws::CostExplorer
345
340
  #
346
341
  # The following are examples of valid ThresholdExpressions:
347
342
  #
348
- # * Absolute threshold: `\{ "Dimensions": \{ "Key":
343
+ # * Absolute threshold: `{ "Dimensions": { "Key":
349
344
  # "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
350
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}`
345
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }`
351
346
  #
352
- # * Percentage threshold: `\{ "Dimensions": \{ "Key":
347
+ # * Percentage threshold: `{ "Dimensions": { "Key":
353
348
  # "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [
354
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}`
349
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }`
355
350
  #
356
- # * `AND` two thresholds together: `\{ "And": [ \{ "Dimensions": \{
351
+ # * `AND` two thresholds together: `{ "And": [ { "Dimensions": {
357
352
  # "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
358
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}, \{
359
- # "Dimensions": \{ "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
360
- # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ]
361
- # \} \} ] \}`
353
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, {
354
+ # "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
355
+ # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] }
356
+ # } ] }`
362
357
  #
363
- # * `OR` two thresholds together: `\{ "Or": [ \{ "Dimensions": \{
364
- # "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
365
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}, \{
366
- # "Dimensions": \{ "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
367
- # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ]
368
- # \} \} ] \}`
358
+ # * `OR` two thresholds together: `{ "Or": [ { "Dimensions": { "Key":
359
+ # "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
360
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, {
361
+ # "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
362
+ # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] }
363
+ # } ] }`
369
364
  #
370
365
  #
371
366
  #
@@ -1804,7 +1799,6 @@ module Aws::CostExplorer
1804
1799
  #
1805
1800
  # * Specify the `Dimensions` field to define a filter that acts on
1806
1801
  # the [ `DimensionValues` ][1].
1807
- #
1808
1802
  # * For each filter type, you can set the dimension name and values
1809
1803
  # for the filters that you plan to use.
1810
1804
  #
@@ -1814,12 +1808,11 @@ module Aws::CostExplorer
1814
1808
  # Virginia)`.
1815
1809
  #
1816
1810
  # * The corresponding `Expression` for this example is as follows:
1817
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
1818
- # "us-west-1" ] \} \}`
1811
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
1812
+ # "us-west-1" ] } }`
1819
1813
  #
1820
1814
  # * As shown in the previous example, lists of dimension values are
1821
1815
  # combined with `OR` when applying the filter.
1822
- #
1823
1816
  # * You can also set different match options to further control how
1824
1817
  # the filter behaves. Not all APIs support match options. Refer to
1825
1818
  # the documentation for each specific API to see what is supported.
@@ -1828,9 +1821,8 @@ module Aws::CostExplorer
1828
1821
  # with "a".
1829
1822
  #
1830
1823
  # * The corresponding `Expression` for this example is as follows:
1831
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
1832
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
1833
- #
1824
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME", "MatchOptions":
1825
+ # [ "STARTS_WITH" ], "Values": [ "a" ] } }`
1834
1826
  # * Compound `Expression` types with logical operations.
1835
1827
  #
1836
1828
  # * You can use multiple `Expression` types and the logical operators
@@ -1841,17 +1833,16 @@ module Aws::CostExplorer
1841
1833
  # us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
1842
1834
  # DataTransfer)`.
1843
1835
  #
1844
- # * The corresponding `Expression` for this example is as follows: `\{
1845
- # "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION", "Values": [
1846
- # "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key": "TagName",
1847
- # "Values": ["Value1"] \} \} ]\}, \{"Not": \{"Dimensions": \{ "Key":
1848
- # "USAGE_TYPE", "Values": ["DataTransfer"] \}\}\} ] \} `
1849
- #
1836
+ # * The corresponding `Expression` for this example is as follows: `{
1837
+ # "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values": [
1838
+ # "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
1839
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
1840
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
1850
1841
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
1851
1842
  # returns an error if more than one is specified. The following
1852
- # example shows an `Expression` object that creates an error: ` \{
1853
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
1854
- # "DataTransfer" ] \} \} `
1843
+ # example shows an `Expression` object that creates an error: ` {
1844
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
1845
+ # "DataTransfer" ] } } `
1855
1846
  #
1856
1847
  # The following is an example of the corresponding error message:
1857
1848
  # `"Expression has more than one roots. Only one root operator is
@@ -2482,7 +2473,6 @@ module Aws::CostExplorer
2482
2473
  #
2483
2474
  # * Specify the `Dimensions` field to define a filter that acts on
2484
2475
  # the [ `DimensionValues` ][1].
2485
- #
2486
2476
  # * For each filter type, you can set the dimension name and values
2487
2477
  # for the filters that you plan to use.
2488
2478
  #
@@ -2492,12 +2482,11 @@ module Aws::CostExplorer
2492
2482
  # Virginia)`.
2493
2483
  #
2494
2484
  # * The corresponding `Expression` for this example is as follows:
2495
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
2496
- # "us-west-1" ] \} \}`
2485
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
2486
+ # "us-west-1" ] } }`
2497
2487
  #
2498
2488
  # * As shown in the previous example, lists of dimension values
2499
2489
  # are combined with `OR` when applying the filter.
2500
- #
2501
2490
  # * You can also set different match options to further control how
2502
2491
  # the filter behaves. Not all APIs support match options. Refer to
2503
2492
  # the documentation for each specific API to see what is
@@ -2507,9 +2496,8 @@ module Aws::CostExplorer
2507
2496
  # start with "a".
2508
2497
  #
2509
2498
  # * The corresponding `Expression` for this example is as follows:
2510
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
2511
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
2512
- #
2499
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
2500
+ # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
2513
2501
  # * Compound `Expression` types with logical operations.
2514
2502
  #
2515
2503
  # * You can use multiple `Expression` types and the logical
@@ -2522,17 +2510,15 @@ module Aws::CostExplorer
2522
2510
  # DataTransfer)`.
2523
2511
  #
2524
2512
  # * The corresponding `Expression` for this example is as follows:
2525
- # `\{ "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION",
2526
- # "Values": [ "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key":
2527
- # "TagName", "Values": ["Value1"] \} \} ]\}, \{"Not":
2528
- # \{"Dimensions": \{ "Key": "USAGE_TYPE", "Values":
2529
- # ["DataTransfer"] \}\}\} ] \} `
2530
- #
2513
+ # `{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values":
2514
+ # [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
2515
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
2516
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
2531
2517
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
2532
2518
  # returns an error if more than one is specified. The following
2533
- # example shows an `Expression` object that creates an error: ` \{
2534
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
2535
- # "DataTransfer" ] \} \} `
2519
+ # example shows an `Expression` object that creates an error: ` {
2520
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
2521
+ # "DataTransfer" ] } } `
2536
2522
  #
2537
2523
  # The following is an example of the corresponding error message:
2538
2524
  # `"Expression has more than one roots. Only one root operator is
@@ -2979,7 +2965,6 @@ module Aws::CostExplorer
2979
2965
  #
2980
2966
  # * Specify the `Dimensions` field to define a filter that acts on
2981
2967
  # the [ `DimensionValues` ][1].
2982
- #
2983
2968
  # * For each filter type, you can set the dimension name and values
2984
2969
  # for the filters that you plan to use.
2985
2970
  #
@@ -2989,12 +2974,11 @@ module Aws::CostExplorer
2989
2974
  # Virginia)`.
2990
2975
  #
2991
2976
  # * The corresponding `Expression` for this example is as follows:
2992
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
2993
- # "us-west-1" ] \} \}`
2977
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
2978
+ # "us-west-1" ] } }`
2994
2979
  #
2995
2980
  # * As shown in the previous example, lists of dimension values
2996
2981
  # are combined with `OR` when applying the filter.
2997
- #
2998
2982
  # * You can also set different match options to further control how
2999
2983
  # the filter behaves. Not all APIs support match options. Refer to
3000
2984
  # the documentation for each specific API to see what is
@@ -3004,9 +2988,8 @@ module Aws::CostExplorer
3004
2988
  # start with "a".
3005
2989
  #
3006
2990
  # * The corresponding `Expression` for this example is as follows:
3007
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
3008
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
3009
- #
2991
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
2992
+ # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
3010
2993
  # * Compound `Expression` types with logical operations.
3011
2994
  #
3012
2995
  # * You can use multiple `Expression` types and the logical
@@ -3019,17 +3002,15 @@ module Aws::CostExplorer
3019
3002
  # DataTransfer)`.
3020
3003
  #
3021
3004
  # * The corresponding `Expression` for this example is as follows:
3022
- # `\{ "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION",
3023
- # "Values": [ "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key":
3024
- # "TagName", "Values": ["Value1"] \} \} ]\}, \{"Not":
3025
- # \{"Dimensions": \{ "Key": "USAGE_TYPE", "Values":
3026
- # ["DataTransfer"] \}\}\} ] \} `
3027
- #
3005
+ # `{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values":
3006
+ # [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
3007
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
3008
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
3028
3009
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
3029
3010
  # returns an error if more than one is specified. The following
3030
- # example shows an `Expression` object that creates an error: ` \{
3031
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
3032
- # "DataTransfer" ] \} \} `
3011
+ # example shows an `Expression` object that creates an error: ` {
3012
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
3013
+ # "DataTransfer" ] } } `
3033
3014
  #
3034
3015
  # The following is an example of the corresponding error message:
3035
3016
  # `"Expression has more than one roots. Only one root operator is
@@ -3454,7 +3435,6 @@ module Aws::CostExplorer
3454
3435
  #
3455
3436
  # * Specify the `Dimensions` field to define a filter that acts on
3456
3437
  # the [ `DimensionValues` ][1].
3457
- #
3458
3438
  # * For each filter type, you can set the dimension name and values
3459
3439
  # for the filters that you plan to use.
3460
3440
  #
@@ -3464,12 +3444,11 @@ module Aws::CostExplorer
3464
3444
  # Virginia)`.
3465
3445
  #
3466
3446
  # * The corresponding `Expression` for this example is as follows:
3467
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
3468
- # "us-west-1" ] \} \}`
3447
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
3448
+ # "us-west-1" ] } }`
3469
3449
  #
3470
3450
  # * As shown in the previous example, lists of dimension values
3471
3451
  # are combined with `OR` when applying the filter.
3472
- #
3473
3452
  # * You can also set different match options to further control how
3474
3453
  # the filter behaves. Not all APIs support match options. Refer to
3475
3454
  # the documentation for each specific API to see what is
@@ -3479,9 +3458,8 @@ module Aws::CostExplorer
3479
3458
  # start with "a".
3480
3459
  #
3481
3460
  # * The corresponding `Expression` for this example is as follows:
3482
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
3483
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
3484
- #
3461
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
3462
+ # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
3485
3463
  # * Compound `Expression` types with logical operations.
3486
3464
  #
3487
3465
  # * You can use multiple `Expression` types and the logical
@@ -3494,17 +3472,15 @@ module Aws::CostExplorer
3494
3472
  # DataTransfer)`.
3495
3473
  #
3496
3474
  # * The corresponding `Expression` for this example is as follows:
3497
- # `\{ "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION",
3498
- # "Values": [ "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key":
3499
- # "TagName", "Values": ["Value1"] \} \} ]\}, \{"Not":
3500
- # \{"Dimensions": \{ "Key": "USAGE_TYPE", "Values":
3501
- # ["DataTransfer"] \}\}\} ] \} `
3502
- #
3475
+ # `{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values":
3476
+ # [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
3477
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
3478
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
3503
3479
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
3504
3480
  # returns an error if more than one is specified. The following
3505
- # example shows an `Expression` object that creates an error: ` \{
3506
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
3507
- # "DataTransfer" ] \} \} `
3481
+ # example shows an `Expression` object that creates an error: ` {
3482
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
3483
+ # "DataTransfer" ] } } `
3508
3484
  #
3509
3485
  # The following is an example of the corresponding error message:
3510
3486
  # `"Expression has more than one roots. Only one root operator is
@@ -3782,7 +3758,6 @@ module Aws::CostExplorer
3782
3758
  #
3783
3759
  # * Specify the `Dimensions` field to define a filter that acts on
3784
3760
  # the [ `DimensionValues` ][1].
3785
- #
3786
3761
  # * For each filter type, you can set the dimension name and values
3787
3762
  # for the filters that you plan to use.
3788
3763
  #
@@ -3792,12 +3767,11 @@ module Aws::CostExplorer
3792
3767
  # Virginia)`.
3793
3768
  #
3794
3769
  # * The corresponding `Expression` for this example is as follows:
3795
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
3796
- # "us-west-1" ] \} \}`
3770
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
3771
+ # "us-west-1" ] } }`
3797
3772
  #
3798
3773
  # * As shown in the previous example, lists of dimension values
3799
3774
  # are combined with `OR` when applying the filter.
3800
- #
3801
3775
  # * You can also set different match options to further control how
3802
3776
  # the filter behaves. Not all APIs support match options. Refer to
3803
3777
  # the documentation for each specific API to see what is
@@ -3807,9 +3781,8 @@ module Aws::CostExplorer
3807
3781
  # start with "a".
3808
3782
  #
3809
3783
  # * The corresponding `Expression` for this example is as follows:
3810
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
3811
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
3812
- #
3784
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
3785
+ # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
3813
3786
  # * Compound `Expression` types with logical operations.
3814
3787
  #
3815
3788
  # * You can use multiple `Expression` types and the logical
@@ -3822,17 +3795,15 @@ module Aws::CostExplorer
3822
3795
  # DataTransfer)`.
3823
3796
  #
3824
3797
  # * The corresponding `Expression` for this example is as follows:
3825
- # `\{ "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION",
3826
- # "Values": [ "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key":
3827
- # "TagName", "Values": ["Value1"] \} \} ]\}, \{"Not":
3828
- # \{"Dimensions": \{ "Key": "USAGE_TYPE", "Values":
3829
- # ["DataTransfer"] \}\}\} ] \} `
3830
- #
3798
+ # `{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values":
3799
+ # [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
3800
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
3801
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
3831
3802
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
3832
3803
  # returns an error if more than one is specified. The following
3833
- # example shows an `Expression` object that creates an error: ` \{
3834
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
3835
- # "DataTransfer" ] \} \} `
3804
+ # example shows an `Expression` object that creates an error: ` {
3805
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
3806
+ # "DataTransfer" ] } } `
3836
3807
  #
3837
3808
  # The following is an example of the corresponding error message:
3838
3809
  # `"Expression has more than one roots. Only one root operator is
@@ -4406,7 +4377,6 @@ module Aws::CostExplorer
4406
4377
  #
4407
4378
  # * Specify the `Dimensions` field to define a filter that acts on
4408
4379
  # the [ `DimensionValues` ][1].
4409
- #
4410
4380
  # * For each filter type, you can set the dimension name and values
4411
4381
  # for the filters that you plan to use.
4412
4382
  #
@@ -4416,12 +4386,11 @@ module Aws::CostExplorer
4416
4386
  # Virginia)`.
4417
4387
  #
4418
4388
  # * The corresponding `Expression` for this example is as follows:
4419
- # `\{ "Dimensions": \{ "Key": "REGION", "Values": [ "us-east-1",
4420
- # "us-west-1" ] \} \}`
4389
+ # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
4390
+ # "us-west-1" ] } }`
4421
4391
  #
4422
4392
  # * As shown in the previous example, lists of dimension values
4423
4393
  # are combined with `OR` when applying the filter.
4424
- #
4425
4394
  # * You can also set different match options to further control how
4426
4395
  # the filter behaves. Not all APIs support match options. Refer to
4427
4396
  # the documentation for each specific API to see what is
@@ -4431,9 +4400,8 @@ module Aws::CostExplorer
4431
4400
  # start with "a".
4432
4401
  #
4433
4402
  # * The corresponding `Expression` for this example is as follows:
4434
- # `\{ "Dimensions": \{ "Key": "LINKED_ACCOUNT_NAME",
4435
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] \} \}`
4436
- #
4403
+ # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
4404
+ # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
4437
4405
  # * Compound `Expression` types with logical operations.
4438
4406
  #
4439
4407
  # * You can use multiple `Expression` types and the logical
@@ -4446,17 +4414,15 @@ module Aws::CostExplorer
4446
4414
  # DataTransfer)`.
4447
4415
  #
4448
4416
  # * The corresponding `Expression` for this example is as follows:
4449
- # `\{ "And": [ \{"Or": [ \{"Dimensions": \{ "Key": "REGION",
4450
- # "Values": [ "us-east-1", "us-west-1" ] \}\}, \{"Tags": \{ "Key":
4451
- # "TagName", "Values": ["Value1"] \} \} ]\}, \{"Not":
4452
- # \{"Dimensions": \{ "Key": "USAGE_TYPE", "Values":
4453
- # ["DataTransfer"] \}\}\} ] \} `
4454
- #
4417
+ # `{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values":
4418
+ # [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
4419
+ # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
4420
+ # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
4455
4421
  # <note markdown="1"> Because each `Expression` can have only one operator, the service
4456
4422
  # returns an error if more than one is specified. The following
4457
- # example shows an `Expression` object that creates an error: ` \{
4458
- # "And": [ ... ], "Dimensions": \{ "Key": "USAGE_TYPE", "Values": [
4459
- # "DataTransfer" ] \} \} `
4423
+ # example shows an `Expression` object that creates an error: ` {
4424
+ # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
4425
+ # "DataTransfer" ] } } `
4460
4426
  #
4461
4427
  # The following is an example of the corresponding error message:
4462
4428
  # `"Expression has more than one roots. Only one root operator is
@@ -7250,27 +7216,27 @@ module Aws::CostExplorer
7250
7216
  #
7251
7217
  # The following are examples of valid ThresholdExpressions:
7252
7218
  #
7253
- # * Absolute threshold: `\{ "Dimensions": \{ "Key":
7219
+ # * Absolute threshold: `{ "Dimensions": { "Key":
7254
7220
  # "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
7255
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}`
7221
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }`
7256
7222
  #
7257
- # * Percentage threshold: `\{ "Dimensions": \{ "Key":
7223
+ # * Percentage threshold: `{ "Dimensions": { "Key":
7258
7224
  # "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [
7259
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}`
7225
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }`
7260
7226
  #
7261
- # * `AND` two thresholds together: `\{ "And": [ \{ "Dimensions": \{
7227
+ # * `AND` two thresholds together: `{ "And": [ { "Dimensions": {
7262
7228
  # "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
7263
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}, \{
7264
- # "Dimensions": \{ "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
7265
- # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ]
7266
- # \} \} ] \}`
7229
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, {
7230
+ # "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
7231
+ # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] }
7232
+ # } ] }`
7267
7233
  #
7268
- # * `OR` two thresholds together: `\{ "Or": [ \{ "Dimensions": \{
7269
- # "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
7270
- # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] \} \}, \{
7271
- # "Dimensions": \{ "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
7272
- # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ]
7273
- # \} \} ] \}`
7234
+ # * `OR` two thresholds together: `{ "Or": [ { "Dimensions": { "Key":
7235
+ # "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [
7236
+ # "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, {
7237
+ # "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE",
7238
+ # "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] }
7239
+ # } ] }`
7274
7240
  #
7275
7241
  #
7276
7242
  #
data/lib/aws-sdk-costexplorer.rb CHANGED
@@ -54,7 +54,7 @@ module Aws::CostExplorer
54
54
  autoload :EndpointProvider, 'aws-sdk-costexplorer/endpoint_provider'
55
55
  autoload :Endpoints, 'aws-sdk-costexplorer/endpoints'
56
56
 
57
- GEM_VERSION = '1.113.0'
57
+ GEM_VERSION = '1.115.0'
58
58
 
59
59
  end
60
60
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-costexplorer
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.113.0
4
+ version: 1.115.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-10-18 00:00:00.000000000 Z
11
+ date: 2024-11-18 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core