costexplorer_update_anomaly_subscription: Updates an existing cost anomaly subscription
In paws.cost.management: 'Amazon Web Services' Cost Management Services

View source: R/costexplorer_operations.R

costexplorer_update_anomaly_subscription

R Documentation

Updates an existing cost anomaly subscription

Description

Updates an existing cost anomaly subscription. Specify the fields that you want to update. Omitted fields are unchanged.

See https://www.paws-r-sdk.com/docs/costexplorer_update_anomaly_subscription/ for full documentation.

Usage

costexplorer_update_anomaly_subscription(
  SubscriptionArn,
  Threshold = NULL,
  Frequency = NULL,
  MonitorArnList = NULL,
  Subscribers = NULL,
  SubscriptionName = NULL,
  ThresholdExpression = NULL
)

Arguments

`SubscriptionArn`	[required] A cost anomaly subscription Amazon Resource Name (ARN).
`Threshold`	(deprecated) The update to the threshold value for receiving notifications. This field has been deprecated. To update a threshold, use ThresholdExpression. Continued use of Threshold will be treated as shorthand syntax for a ThresholdExpression. You can specify either Threshold or ThresholdExpression, but not both.
`Frequency`	The update to the frequency value that subscribers receive notifications.
`MonitorArnList`	A list of cost anomaly monitor ARNs.
`Subscribers`	The update to the subscriber list.
`SubscriptionName`	The new name of the subscription.
`ThresholdExpression`	The update to the Expression object used to specify the anomalies that you want to generate alerts for. This supports dimensions and nested expressions. The supported dimensions are `ANOMALY_TOTAL_IMPACT_ABSOLUTE` and `ANOMALY_TOTAL_IMPACT_PERCENTAGE`, corresponding to an anomaly’s TotalImpact and TotalImpactPercentage, respectively (see Impact for more details). The supported nested expression types are `AND` and `OR`. The match option `GREATER_THAN_OR_EQUAL` is required. Values must be numbers between 0 and 10,000,000,000 in string format. You can specify either Threshold or ThresholdExpression, but not both. The following are examples of valid ThresholdExpressions: Absolute threshold: `⁠{ "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }⁠` Percentage threshold: `⁠{ "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }⁠` `AND` two thresholds together: `⁠{ "And": [ { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } } ] }⁠` `OR` two thresholds together: `⁠{ "Or": [ { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_ABSOLUTE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } }, { "Dimensions": { "Key": "ANOMALY_TOTAL_IMPACT_PERCENTAGE", "MatchOptions": [ "GREATER_THAN_OR_EQUAL" ], "Values": [ "100" ] } } ] }⁠`