This is the new *CloudFormation Template Reference Guide*. Please update your bookmarks and links. For help getting started with CloudFormation, see the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html).

# AWS::CE::AnomalyMonitor
<a name="aws-resource-ce-anomalymonitor"></a>

 The `AWS::CE::AnomalyMonitor` resource is a Cost Explorer resource type that continuously inspects your account's cost data for anomalies, based on `MonitorType` and `MonitorSpecification`. The content consists of detailed metadata and the current status of the monitor object. 

## Syntax
<a name="aws-resource-ce-anomalymonitor-syntax"></a>

To declare this entity in your CloudFormation template, use the following syntax:

### JSON
<a name="aws-resource-ce-anomalymonitor-syntax.json"></a>

```
{
  "Type" : "AWS::CE::AnomalyMonitor",
  "Properties" : {
      "[MonitorDimension](#cfn-ce-anomalymonitor-monitordimension)" : String,
      "[MonitorName](#cfn-ce-anomalymonitor-monitorname)" : String,
      "[MonitorSpecification](#cfn-ce-anomalymonitor-monitorspecification)" : String,
      "[MonitorType](#cfn-ce-anomalymonitor-monitortype)" : String,
      "[ResourceTags](#cfn-ce-anomalymonitor-resourcetags)" : [ ResourceTag, ... ]
    }
}
```

### YAML
<a name="aws-resource-ce-anomalymonitor-syntax.yaml"></a>

```
Type: AWS::CE::AnomalyMonitor
Properties:
  [MonitorDimension](#cfn-ce-anomalymonitor-monitordimension): String
  [MonitorName](#cfn-ce-anomalymonitor-monitorname): String
  [MonitorSpecification](#cfn-ce-anomalymonitor-monitorspecification): String
  [MonitorType](#cfn-ce-anomalymonitor-monitortype): String
  [ResourceTags](#cfn-ce-anomalymonitor-resourcetags): 
    - ResourceTag
```

## Properties
<a name="aws-resource-ce-anomalymonitor-properties"></a>

`MonitorDimension`  <a name="cfn-ce-anomalymonitor-monitordimension"></a>
For customer managed monitors, do not specify this field.  
For AWS managed monitors, this field controls which cost dimension is automatically analyzed by the monitor. For `TAG` and `COST_CATEGORY ` dimensions, you must also specify MonitorSpecification to configure the specific tag or cost category key to analyze.  
*Required*: No  
*Type*: String  
*Allowed values*: `SERVICE | LINKED_ACCOUNT | TAG | COST_CATEGORY`  
*Update requires*: [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)

`MonitorName`  <a name="cfn-ce-anomalymonitor-monitorname"></a>
The name of the monitor.   
*Required*: Yes  
*Type*: String  
*Pattern*: `[\S\s]*`  
*Minimum*: `0`  
*Maximum*: `1024`  
*Update requires*: [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt)

`MonitorSpecification`  <a name="cfn-ce-anomalymonitor-monitorspecification"></a>
The array of `MonitorSpecification` in JSON array format. For instance, you can use `MonitorSpecification` to specify a tag, Cost Category, or linked account for your custom anomaly monitor. For further information, see the [Examples](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ce-anomalymonitor.html#aws-resource-ce-anomalymonitor--examples) section of this page.  
*Required*: No  
*Type*: String  
*Update requires*: [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)

`MonitorType`  <a name="cfn-ce-anomalymonitor-monitortype"></a>
The type of the monitor.   
Set this to `DIMENSIONAL` for an AWS managed monitor. AWS managed monitors automatically track up to the top 5,000 values by cost within a dimension of your choosing. Each dimension value is evaluated independently. If you start incurring cost in a new value of your chosen dimension, it will automatically be analyzed by an AWS managed monitor.  
Set this to `CUSTOM` for a customer managed monitor. Customer managed monitors let you select specific dimension values that get monitored in aggregate.   
For more information about monitor types, see [Monitor types](https://docs.aws.amazon.com/cost-management/latest/userguide/getting-started-ad.html#monitor-type-def) in the *Billing and Cost Management User Guide*.  
*Required*: Yes  
*Type*: String  
*Allowed values*: `DIMENSIONAL | CUSTOM`  
*Update requires*: [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)

`ResourceTags`  <a name="cfn-ce-anomalymonitor-resourcetags"></a>
Property description not available.  
*Required*: No  
*Type*: Array of [ResourceTag](aws-properties-ce-anomalymonitor-resourcetag.md)  
*Minimum*: `0`  
*Maximum*: `200`  
*Update requires*: [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)

## Return values
<a name="aws-resource-ce-anomalymonitor-return-values"></a>

### Ref
<a name="aws-resource-ce-anomalymonitor-return-values-ref"></a>

When you pass the logical ID of this resource to the intrinsic `Ref` function, `Ref` returns`MonitorArn`. For example:

            `{ "Ref": "myAnomalySubscriptionLogicalName" }`        

For more information about using the `Ref` function, see [https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/intrinsic-function-reference-ref.html](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/intrinsic-function-reference-ref.html).

### Fn::GetAtt
<a name="aws-resource-ce-anomalymonitor-return-values-fn--getatt"></a>

The `Fn::GetAtt` intrinsic function returns a value for a specified attribute of this type. The following are the available attributes and sample return values.

For more information about using the `Fn::GetAtt` intrinsic function, see [https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/intrinsic-function-reference-getatt.html](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/intrinsic-function-reference-getatt.html).

#### 
<a name="aws-resource-ce-anomalymonitor-return-values-fn--getatt-fn--getatt"></a>

`CreationDate`  <a name="CreationDate-fn::getatt"></a>
The date when the monitor was created.

`DimensionalValueCount`  <a name="DimensionalValueCount-fn::getatt"></a>
The value for evaluated dimensions. 

`LastEvaluatedDate`  <a name="LastEvaluatedDate-fn::getatt"></a>
The date when the monitor last evaluated for anomalies. 

`LastUpdatedDate`  <a name="LastUpdatedDate-fn::getatt"></a>
The date when the monitor was last updated.

`MonitorArn`  <a name="MonitorArn-fn::getatt"></a>
The Amazon Resource Name (ARN) value for the monitor. 

## Examples
<a name="aws-resource-ce-anomalymonitor--examples"></a>



**Topics**
+ [Service monitor](#aws-resource-ce-anomalymonitor--examples--Service_monitor)
+ [Anomaly monitor with tags](#aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_tags)
+ [Anomaly monitor with Cost Category](#aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_Cost_Category)
+ [Anomaly monitor with linked account](#aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_linked_account)
+ [Attaching subscriptions to monitors](#aws-resource-ce-anomalymonitor--examples--Attaching_subscriptions_to_monitors)

### Service monitor
<a name="aws-resource-ce-anomalymonitor--examples--Service_monitor"></a>

The following example creates a service anomaly monitor.

#### JSON
<a name="aws-resource-ce-anomalymonitor--examples--Service_monitor--json"></a>

```
{
  "Resources": {
    "AnomalyServiceMonitor": {
      "Type": "AWS::CE::AnomalyMonitor",
      "Properties": {
        "MonitorName": "MonitorName",
        "MonitorType": "DIMENSIONAL",
        "MonitorDimension": "SERVICE"
      }
    }
  }
}
```

#### YAML
<a name="aws-resource-ce-anomalymonitor--examples--Service_monitor--yaml"></a>

```
Resources:
  AnomalyServiceMonitor:
    Type: 'AWS::CE::AnomalyMonitor'
    Properties:
      MonitorName: 'MonitorName'
      MonitorType: 'DIMENSIONAL'
      MonitorDimension: 'SERVICE'
```

### Anomaly monitor with tags
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_tags"></a>

The following example creates a custom anomaly monitor with tags.

#### JSON
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_tags--json"></a>

```
{
  "Resources": {
    "CustomAnomalyMonitorWithTags": {
      "Type": "AWS::CE::AnomalyMonitor",
      "Properties": {
        "MonitorName": "MonitorName",
        "MonitorType": "CUSTOM",
        "MonitorSpecification": " { \"Tags\" : { \"Key\" : \"Tag Key\", \"Values\" : [ \"TagValue1\", \"TagValue2\" ] } }"
      }
    }
  }
}
```

#### YAML
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_tags--yaml"></a>

```
Resources:
  CustomAnomalyMonitorWithTags:
    Type: 'AWS::CE::AnomalyMonitor'
    Properties:
      MonitorName: "MonitorName"
      MonitorType: "CUSTOM"
      MonitorSpecification: '
            {
              "Tags" : {
                "Key" : "Tag Key",
                "Values" : [ "TagValue1", "TagValue2" ]
              }
            }'
```

### Anomaly monitor with Cost Category
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_Cost_Category"></a>

The following example creates a custom anomaly monitor with a Cost Category.

#### JSON
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_Cost_Category--json"></a>

```
{
  "Resources": {
    "CustomAnomalyMonitorWithCC": {
      "Type": "AWS::CE::AnomalyMonitor",
      "Properties": {
        "MonitorName": "MonitorName",
        "MonitorType": "CUSTOM",
        "MonitorSpecification": " { \"CostCategories\" : { \"Key\" : \"CostCategoryKey\", \"Values\" : [ \"CostCategoryValue\" ] } }"
      }
    }
  }
}
```

#### YAML
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_Cost_Category--yaml"></a>

```
Resources:
   CustomAnomalyMonitorWithCC:
    Type: 'AWS::CE::AnomalyMonitor'
    Properties:
      MonitorName: "MonitorName"
      MonitorType: "CUSTOM"
      MonitorSpecification: '
            {
              "CostCategories" : {
                "Key" : "CostCategoryKey",
                "Values" : [ "CostCategoryValue" ]
              }
            }'
```

### Anomaly monitor with linked account
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_linked_account"></a>

The following example creates a custom anomaly monitor with a linked account.

#### JSON
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_linked_account--json"></a>

```
{
  "Resources": {
    "CustomAnomalyMonitorWithLinkedAccount": {
      "Type": "AWS::CE::AnomalyMonitor",
      "Properties": {
        "MonitorName": "MonitorName",
        "MonitorType": "CUSTOM",
        "MonitorSpecification": " { \"Dimensions\" : { \"Key\" : \"LINKED_ACCOUNT\", \"Values\" : [ \"123456789012\", \"123456789013\" ] } }"
      }
    }
  }
}
```

#### YAML
<a name="aws-resource-ce-anomalymonitor--examples--Anomaly_monitor_with_linked_account--yaml"></a>

```
Resources:
   CustomAnomalyMonitorWithLinkedAccount:
    Type: 'AWS::CE::AnomalyMonitor'
    Properties:
      MonitorName: "MonitorName"
      MonitorType: "CUSTOM"
      MonitorSpecification: '
            {
              "Dimensions" : {
                "Key" : "LINKED_ACCOUNT",
                "Values" : [ "123456789012", "123456789013" ]
              }
            }'
```

### Attaching subscriptions to monitors
<a name="aws-resource-ce-anomalymonitor--examples--Attaching_subscriptions_to_monitors"></a>

The following example shows two anomaly monitors attached to an anomaly subscription.

#### JSON
<a name="aws-resource-ce-anomalymonitor--examples--Attaching_subscriptions_to_monitors--json"></a>

```
{
  "Resources": {
    "CustomAnomalyMonitorWithLinkedAccount": {
      "Type": "AWS::CE::AnomalyMonitor",
      "Properties": {
        "MonitorName": "MonitorName",
        "MonitorType": "CUSTOM",
        "MonitorSpecification": " { \"Dimensions\" : { \"Key\" : \"LINKED_ACCOUNT\", \"Values\" : [ \"123456789012\", \"123456789013\" ] } }"
      }
    },
    "AnomalyServiceMonitor": {
      "Type": "AWS::CE::AnomalyMonitor",
      "Properties": {
        "MonitorName": "MonitorName",
        "MonitorType": "DIMENSIONAL",
        "MonitorDimension": "SERVICE"
      }
    },
    "AnomalySubscription": {
      "Type": "AWS::CE::AnomalySubscription",
      "Properties": {
        "SubscriptionName": "SubscriptionName",
        "Threshold": 100,
        "Frequency": "DAILY",
        "MonitorArnList": [
         { “Ref”: "CustomAnomalyMonitorWithLinkedAccount"},
         { "Ref": "AnomalyServiceMonitor"}
        ],
        "Subscribers": [
          {
            "Type": "EMAIL",
            "Address": "abc@def.com"
          }
        ]
      }
    }
  }
}
```

#### YAML
<a name="aws-resource-ce-anomalymonitor--examples--Attaching_subscriptions_to_monitors--yaml"></a>

```
Resources:
   CustomAnomalyMonitorWithLinkedAccount:
    Type: 'AWS::CE::AnomalyMonitor'
    Properties:
      MonitorName: "MonitorName"
      MonitorType: "CUSTOM"
      MonitorSpecification: '
            {
              "Dimensions" : {
                "Key" : "LINKED_ACCOUNT",
                "Values" : [ "123456789012", "123456789013" ]
              }
            }' 
            
   AnomalyServiceMonitor:
    Type: 'AWS::CE::AnomalyMonitor'
    Properties:
      MonitorName: 'MonitorName'
      MonitorType: 'DIMENSIONAL'
      MonitorDimension: 'SERVICE' 

   AnomalySubscription:
    Type: 'AWS::CE::AnomalySubscription'
    Properties:
      SubscriptionName: "SubscriptionName"
      Threshold: 100
      Frequency: "DAILY"
      MonitorArnList: [
         !Ref CustomAnomalyMonitorWithLinkedAccount,
         !Ref AnomalyServiceMonitor
      ]
      Subscribers: [
        {
          "Type": "EMAIL",
          "Address": "abc@def.com"
        }
      ]
```

## See also
<a name="aws-resource-ce-anomalymonitor--seealso"></a>
+ [AnomalyMonitor](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_AnomalyMonitor.html) in the *AWS Billing and Cost Management API Reference*. 
+ [CreateAnomalyMonitor](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_CreateAnomalyMonitor.html) in the *AWS Billing and Cost Management API Reference*. 
+ [DeleteAnomalyMonitor](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_DeleteAnomalyMonitor.html) in the *AWS Billing and Cost Management API Reference*. 
+ [GetAnomalyMonitors](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_GetAnomalyMonitors.html) in the *AWS Billing and Cost Management API Reference*. 
+ [UpdateAnomalyMonitor](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_UpdateAnomalyMonitor.html) in the *AWS Billing and Cost Management API Reference*. 



# AWS::CE::AnomalyMonitor ResourceTag
<a name="aws-properties-ce-anomalymonitor-resourcetag"></a>

The tag structure that contains a tag key and value. 

**Note**  
Tagging is supported only for the following Cost Explorer resource types: [https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_AnomalyMonitor.html](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_AnomalyMonitor.html), [https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_AnomalySubscription.html](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_AnomalySubscription.html), [https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_CostCategory.html](https://docs.aws.amazon.com/aws-cost-management/latest/APIReference/API_CostCategory.html).

## Syntax
<a name="aws-properties-ce-anomalymonitor-resourcetag-syntax"></a>

To declare this entity in your CloudFormation template, use the following syntax:

### JSON
<a name="aws-properties-ce-anomalymonitor-resourcetag-syntax.json"></a>

```
{
  "[Key](#cfn-ce-anomalymonitor-resourcetag-key)" : String,
  "[Value](#cfn-ce-anomalymonitor-resourcetag-value)" : String
}
```

### YAML
<a name="aws-properties-ce-anomalymonitor-resourcetag-syntax.yaml"></a>

```
  [Key](#cfn-ce-anomalymonitor-resourcetag-key): String
  [Value](#cfn-ce-anomalymonitor-resourcetag-value): String
```

## Properties
<a name="aws-properties-ce-anomalymonitor-resourcetag-properties"></a>

`Key`  <a name="cfn-ce-anomalymonitor-resourcetag-key"></a>
The key that's associated with the tag.   
*Required*: Yes  
*Type*: String  
*Pattern*: `^(?!aws:).*$`  
*Minimum*: `1`  
*Maximum*: `128`  
*Update requires*: [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)

`Value`  <a name="cfn-ce-anomalymonitor-resourcetag-value"></a>
The value that's associated with the tag.   
*Required*: Yes  
*Type*: String  
*Minimum*: `0`  
*Maximum*: `256`  
*Update requires*: [Replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-replacement)