aws-sdk-costexplorer 1.138.0 → 1.139.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: aa87cd6d7b78e234257eac5b043424e56828455a4e7260d78bcc4a28fa810bd0
4
- data.tar.gz: 9c16d2e8bc1678a4cbec2560583458c69c0aa5eeb819cb29dde05860f4505c1a
3
+ metadata.gz: 685e08cda0f4b9e145c988b1f261dee8e9f9638c9519b6ac96f9ae5b6e931990
4
+ data.tar.gz: afe9231d1f9621e64a0cec66ef4af3eb5e3124a736073c563e4f82086ed9960f
5
5
  SHA512:
6
- metadata.gz: 73920a0ae9942f137b003cd1567e1bdc6b4407d8b4cc4b878153e7ece04c2a0150986a88cf1034bbbbe0799951016303b02b775396781370b218e4d4acf35db0
7
- data.tar.gz: a2762d72a06aff723a467c768b7084c7f94c7971957e1c5ab2c246927c57f63ebc2ebae79395287a2f79bf4888e629dc06821198a20d043106b0fdc1f63426e2
6
+ metadata.gz: 3029a8e6ff66176782a3326bd6ff3cf503664172f8393d4a25fcc28dd828fba0ebf909195a22e92704438424a3998a130523794480574acc9793d6fa7af02a62
7
+ data.tar.gz: 833d37df54f4ab45d6630e624206ced1195589c7bd2031c428f6bb4dc1c8a0b749140055c4e56fe02cc2c7b071d2a32b4c89141a4e792ff35abda90552578c53
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.139.0 (2025-11-19)
5
+ ------------------
6
+
7
+ * Feature - Add support for COST_CATEGORY, TAG, and LINKED_ACCOUNT AWS managed cost anomaly detection monitors
8
+
4
9
  1.138.0 (2025-10-27)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.138.0
1
+ 1.139.0
@@ -533,7 +533,7 @@ module Aws::CostExplorer
533
533
  # last_updated_date: "YearMonthDay",
534
534
  # last_evaluated_date: "YearMonthDay",
535
535
  # monitor_type: "DIMENSIONAL", # required, accepts DIMENSIONAL, CUSTOM
536
- # monitor_dimension: "SERVICE", # accepts SERVICE
536
+ # monitor_dimension: "SERVICE", # accepts SERVICE, LINKED_ACCOUNT, TAG, COST_CATEGORY
537
537
  # monitor_specification: {
538
538
  # or: [
539
539
  # {
@@ -1129,7 +1129,7 @@ module Aws::CostExplorer
1129
1129
  # resp.anomaly_monitors[0].last_updated_date #=> String
1130
1130
  # resp.anomaly_monitors[0].last_evaluated_date #=> String
1131
1131
  # resp.anomaly_monitors[0].monitor_type #=> String, one of "DIMENSIONAL", "CUSTOM"
1132
- # resp.anomaly_monitors[0].monitor_dimension #=> String, one of "SERVICE"
1132
+ # resp.anomaly_monitors[0].monitor_dimension #=> String, one of "SERVICE", "LINKED_ACCOUNT", "TAG", "COST_CATEGORY"
1133
1133
  # resp.anomaly_monitors[0].monitor_specification.or #=> Array
1134
1134
  # resp.anomaly_monitors[0].monitor_specification.or[0] #=> Types::Expression
1135
1135
  # resp.anomaly_monitors[0].monitor_specification.and #=> Array
@@ -6113,7 +6113,7 @@ module Aws::CostExplorer
6113
6113
  tracer: tracer
6114
6114
  )
6115
6115
  context[:gem_name] = 'aws-sdk-costexplorer'
6116
- context[:gem_version] = '1.138.0'
6116
+ context[:gem_version] = '1.139.0'
6117
6117
  Seahorse::Client::Request.new(handlers, context)
6118
6118
  end
6119
6119
 
@@ -184,103 +184,69 @@ module Aws::CostExplorer
184
184
  # @return [String]
185
185
  #
186
186
  # @!attribute [rw] monitor_type
187
- # The possible type values.
188
- # @return [String]
189
- #
190
- # @!attribute [rw] monitor_dimension
191
- # The dimensions to evaluate.
192
- # @return [String]
193
- #
194
- # @!attribute [rw] monitor_specification
195
- # Use `Expression` to filter in various Cost Explorer APIs.
196
- #
197
- # Not all `Expression` types are supported in each API. Refer to the
198
- # documentation for each specific API to see what is supported.
187
+ # The type of the monitor.
199
188
  #
200
- # There are two patterns:
201
- #
202
- # * Simple dimension values.
203
- #
204
- # * There are three types of simple dimension values:
205
- # `CostCategories`, `Tags`, and `Dimensions`.
189
+ # Set this to `DIMENSIONAL` for an Amazon Web Services managed
190
+ # monitor. Amazon Web Services managed monitors automatically track up
191
+ # to the top 5,000 values by cost within a dimension of your choosing.
192
+ # Each dimension value is evaluated independently. If you start
193
+ # incurring cost in a new value of your chosen dimension, it will
194
+ # automatically be analyzed by an Amazon Web Services managed monitor.
206
195
  #
207
- # * Specify the `CostCategories` field to define a filter that
208
- # acts on Cost Categories.
196
+ # Set this to `CUSTOM` for a customer managed monitor. Customer
197
+ # managed monitors let you select specific dimension values that get
198
+ # monitored in aggregate.
209
199
  #
210
- # * Specify the `Tags` field to define a filter that acts on Cost
211
- # Allocation Tags.
200
+ # For more information about monitor types, see [Monitor types][1] in
201
+ # the *Billing and Cost Management User Guide*.
212
202
  #
213
- # * Specify the `Dimensions` field to define a filter that acts on
214
- # the [ `DimensionValues` ][1].
215
- # * For each filter type, you can set the dimension name and values
216
- # for the filters that you plan to use.
217
203
  #
218
- # * For example, you can filter for `REGION==us-east-1 OR
219
- # REGION==us-west-1`. For `GetRightsizingRecommendation`, the
220
- # Region is a full name (for example, `REGION==US East (N.
221
- # Virginia)`.
222
204
  #
223
- # * The corresponding `Expression` for this example is as follows:
224
- # `{ "Dimensions": { "Key": "REGION", "Values": [ "us-east-1",
225
- # "us-west-1" ] } }`
205
+ # [1]: https://docs.aws.amazon.com/cost-management/latest/userguide/getting-started-ad.html#monitor-type-def
206
+ # @return [String]
226
207
  #
227
- # * As shown in the previous example, lists of dimension values
228
- # are combined with `OR` when applying the filter.
229
- # * You can also set different match options to further control how
230
- # the filter behaves. Not all APIs support match options. Refer to
231
- # the documentation for each specific API to see what is
232
- # supported.
208
+ # @!attribute [rw] monitor_dimension
209
+ # For customer managed monitors, do not specify this field.
233
210
  #
234
- # * For example, you can filter for linked account names that
235
- # start with "a".
211
+ # For Amazon Web Services managed monitors, this field controls which
212
+ # cost dimension is automatically analyzed by the monitor. For `TAG`
213
+ # and `COST_CATEGORY ` dimensions, you must also specify
214
+ # MonitorSpecification to configure the specific tag or cost category
215
+ # key to analyze.
216
+ # @return [String]
236
217
  #
237
- # * The corresponding `Expression` for this example is as follows:
238
- # `{ "Dimensions": { "Key": "LINKED_ACCOUNT_NAME",
239
- # "MatchOptions": [ "STARTS_WITH" ], "Values": [ "a" ] } }`
240
- # * Compound `Expression` types with logical operations.
218
+ # @!attribute [rw] monitor_specification
219
+ # An [Expression][1] object used to control what costs the monitor
220
+ # analyzes for anomalies.
241
221
  #
242
- # * You can use multiple `Expression` types and the logical
243
- # operators `AND/OR/NOT` to create a list of one or more
244
- # `Expression` objects. By doing this, you can filter by more
245
- # advanced options.
222
+ # For Amazon Web Services managed monitors:
246
223
  #
247
- # * For example, you can filter by `((REGION == us-east-1 OR REGION
248
- # == us-west-1) OR (TAG.Type == Type1)) AND (USAGE_TYPE !=
249
- # DataTransfer)`.
224
+ # * If MonitorDimension is `SERVICE` or `LINKED_ACCOUNT`, do not
225
+ # specify this field
250
226
  #
251
- # * The corresponding `Expression` for this example is as follows:
252
- # `{ "And": [ {"Or": [ {"Dimensions": { "Key": "REGION", "Values":
253
- # [ "us-east-1", "us-west-1" ] }}, {"Tags": { "Key": "TagName",
254
- # "Values": ["Value1"] } } ]}, {"Not": {"Dimensions": { "Key":
255
- # "USAGE_TYPE", "Values": ["DataTransfer"] }}} ] } `
256
- # <note markdown="1"> Because each `Expression` can have only one operator, the service
257
- # returns an error if more than one is specified. The following
258
- # example shows an `Expression` object that creates an error: ` {
259
- # "And": [ ... ], "Dimensions": { "Key": "USAGE_TYPE", "Values": [
260
- # "DataTransfer" ] } } `
227
+ # * If MonitorDimension is `TAG`, set this field to `{ "Tags": {
228
+ # "Key": "your tag key" } }`
261
229
  #
262
- # The following is an example of the corresponding error message:
263
- # `"Expression has more than one roots. Only one root operator is
264
- # allowed for each expression: And, Or, Not, Dimensions, Tags,
265
- # CostCategories"`
230
+ # * If MonitorDimension is `COST_CATEGORY`, set this field to `{
231
+ # "CostCategories": { "Key": "your cost category key" } }`
266
232
  #
267
- # </note>
233
+ # For customer managed monitors:
268
234
  #
269
- # <note markdown="1"> For the `GetRightsizingRecommendation` action, a combination of OR
270
- # and NOT isn't supported. OR isn't supported between different
271
- # dimensions, or dimensions and tags. NOT operators aren't supported.
272
- # Dimensions are also limited to `LINKED_ACCOUNT`, `REGION`, or
273
- # `RIGHTSIZING_TYPE`.
235
+ # * To track linked accounts, set this field to `{ "Dimensions": {
236
+ # "Key": "LINKED_ACCOUNT", "Values": [ "your list of up to 10
237
+ # account IDs" ] } } `
274
238
  #
275
- # For the `GetReservationPurchaseRecommendation` action, only NOT is
276
- # supported. AND and OR aren't supported. Dimensions are limited to
277
- # `LINKED_ACCOUNT`.
239
+ # * To track cost allocation tags, set this field to `{ "Tags": {
240
+ # "Key": "your tag key", "Values": [ "your list of up to 10 tag
241
+ # values" ] } } `
278
242
  #
279
- # </note>
243
+ # * To track cost categories, set this field to`{ "CostCategories": {
244
+ # "Key": "your cost category key", "Values": [ "your cost category
245
+ # value" ] } } `
280
246
  #
281
247
  #
282
248
  #
283
- # [1]: https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DimensionValues.html
249
+ # [1]: https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_Expression.html
284
250
  # @return [Types::Expression]
285
251
  #
286
252
  # @!attribute [rw] dimensional_value_count
@@ -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.138.0'
57
+ GEM_VERSION = '1.139.0'
58
58
 
59
59
  end
60
60
 
data/sig/client.rbs CHANGED
@@ -92,7 +92,7 @@ module Aws
92
92
  last_updated_date: ::String?,
93
93
  last_evaluated_date: ::String?,
94
94
  monitor_type: ("DIMENSIONAL" | "CUSTOM"),
95
- monitor_dimension: ("SERVICE")?,
95
+ monitor_dimension: ("SERVICE" | "LINKED_ACCOUNT" | "TAG" | "COST_CATEGORY")?,
96
96
  monitor_specification: {
97
97
  or: Array[
98
98
  untyped,
data/sig/types.rbs CHANGED
@@ -55,7 +55,7 @@ module Aws::CostExplorer
55
55
  attr_accessor last_updated_date: ::String
56
56
  attr_accessor last_evaluated_date: ::String
57
57
  attr_accessor monitor_type: ("DIMENSIONAL" | "CUSTOM")
58
- attr_accessor monitor_dimension: ("SERVICE")
58
+ attr_accessor monitor_dimension: ("SERVICE" | "LINKED_ACCOUNT" | "TAG" | "COST_CATEGORY")
59
59
  attr_accessor monitor_specification: Types::Expression
60
60
  attr_accessor dimensional_value_count: ::Integer
61
61
  SENSITIVE: []
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-costexplorer
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.138.0
4
+ version: 1.139.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services