1 Answer
- Newest
- Most votes
- Most comments
1
When you create a MonitorDimension of SERVICE, this is the "default" monitor that watches each service. You don't want to specify anything other than what is below.
Resources:
AnomalyServiceMonitor:
Type: 'AWS::CE::AnomalyMonitor'
Properties:
MonitorName: 'MonitorName'
MonitorType: 'DIMENSIONAL'
MonitorDimension: 'SERVICE'
In contrast, the other three types of monitors for Linked Accounts, Cost Categories, or Cost Allocation tags would be a CUSTOM type, not a DIMENSIONAL type. The MonitorDimension would not apply for these.
Resources:
CustomAnomalyMonitorWithLinkedAccount:
Type: 'AWS::CE::AnomalyMonitor'
Properties:
MonitorName: "MonitorName"
MonitorType: "CUSTOM"
MonitorSpecification: '
{
"Dimensions" : {
"Key" : "LINKED_ACCOUNT",
"Values" : [ "123456789012", "123456789013" ]
}
}'
These three require a MonitorSpecification to denote the tags, account numbers, Cost Categories, or whatever combination of dimensions you are trying to monitor. There are examples of each on the page you linked toward the bottom.
answered 2 years ago
Relevant content
- asked 13 days ago
- asked 12 days ago
- Accepted Answerasked 13 days ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 months ago
Thanks for the quick reply, setting just MonitorType: DIMENSIONAL and MonitorDimension: SERVICE worked.
But where in the documentation is the description what MonitorType: DIMENSIONAL means - how should I have known that was the right answer?