Providing your own tags (without using Resource Tagger) - AMS Accelerate Operations Plan

Providing your own tags (without using Resource Tagger)

The tag-based Alarm Manager manages the lifecycle of per-resource CloudWatch alarms; however, it requires that the managed resources have specific tags defined by AMS Accelerate. AMS Accelerate provides a default configuration profile that assumes that your tags have been applied by Resource Tagger.

If you want to use an alternate method of applying tags to your resources, such as AWS CloudFormation or Terraform, and not Resource Tagger, you create overrides for all AMS Accelerate-provided monitoring rules. For instructions on changing your custom alarm configuration, see Changing the configuration. You also need to make the following changes.

Copy the contents of the AMSManagedAlarms configuration into the CustomerManagedAlarms configuration profile. Update each tag filter to remove the ams:rt: prefix. For example, change this:

"AMSCpuAlarm": { "Tag": { "Key": "ams:rt:ams-monitoring-policy", "Value": "ams-monitored" }, "AlarmDefinition": { ... } },

 

To this (note the changed tag key):

 

"AMSCpuAlarm": { "Tag": { "Key": "ams-monitoring-policy", "Value": "ams-monitored" }, "AlarmDefinition": { ... } },

Then, apply tags to your resources according to the following guidelines:

Resource type Tag key Tag value

All supported resources (described in this table)

ams-monitoring-policy

ams-monitored

EC2 instances (Linux)

ams-monitoring-policy-platform

ams-monitored-linux

EC2 instances (Windows)

ams-monitoring-policy-platform

ams-monitored-windows

Elasticsearch Domain with KMS

ams-monitoring-with-kms

ams-monitored-with-kms

Elasticsearch Domain with Dedicated Master Node

ams-monitoring-with-master

ams-monitored-with-master

Resources that have these tag keys and values are managed by the AMS Accelerate Alarm Manager.