CloudWatch | Create Alarms

To check the change type version, use this command:

aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID

INLINE CREATE:

Issue the create RFC command with execution parameters provided inline (escape quotation marks when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:

aws --profile saml --region us-east-1 amscm create-rfc --change-type-id "ct-361vpyun9a9dd" --change-type-version "1.0" --title "Test Create CloudWatch Alarms" --execution-parameters "{\"Alarms\": [{\"ActionsEnabled\": true,\"AlarmActions\": [\"arn:aws:sns:us-east-1:000000000000:SNS-Topic\"],\"AlarmDescription\": \"Test alarm description.\",\"AlarmName\": \"Test alarm name\",\"ComparisonOperator\": \"GreaterThanThreshold\",\"DatapointsToAlarm\": 1,\"Dimensions\": [{\"Name\": \"InstanceId\",\"Value\": \"i-12345678901234567\"}],\"EvaluateLowSampleCountPercentile\": \"ignore\",\"EvaluationPeriods\": 2,\"InsufficientDataActions\": [\"arn:aws:sns:us-east-1:000000000000:SNS-Topic\"],\"MetricName\": \"TestMetric\",\"Namespace\": \"AWS/Test\",\"OkActions\": [\"arn:aws:sns:us-east-1:000000000000:SNS-Topic\"],\"Period\": 300,\"Statistic\": \"Average\",\"Threshold\": 85,\"TreatMissingData\": \"breaching\",\"Unit\": \"Percent\"}],\"Region\": \"us-east-1\"}"

TEMPLATE CREATE:

1. Output the execution parameters JSON schema for this change type to a file in your current folder; this example names it CwAlarmsParams.json:

   aws amscm get-change-type-version --change-type-id "ct-361vpyun9a9dd" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CwAlarmsParams.json

2. Modify and save the CwAlarmsParams.json file. For example, you can replace the contents with something like this:

   {
     "Alarms": [
       {
         "ActionsEnabled": true,
         "AlarmActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
         "AlarmDescription": "Test alarm description.",
         "AlarmName": "Test alarm name",
         "ComparisonOperator": "GreaterThanThreshold",
         "DatapointsToAlarm": 1,
         "Dimensions": [
           {
             "Name": "InstanceId",
             "Value": "i-12345678901234567"
           }
         ],
         "EvaluateLowSampleCountPercentile": "ignore",
         "EvaluationPeriods": 2,
         "InsufficientDataActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
         "MetricName": "TestMetric",
         "Namespace": "AWS/Test",
         "OkActions": ["arn:aws:sns:us-east-1:000000000000:SNS-Topic"],
         "Period": 300,
         "Statistic": "Average",
         "Threshold": 85,
         "TreatMissingData": "breaching",
         "Unit": "Percent"
       }
     ],
     "Region": "us-east-1"
   }

3. Output the JSON template for CreateRfc to a file in your current folder; this example names it CwAlarmsRfc.json:

   aws amscm create-rfc --generate-cli-skeleton > CwAlarmsRfc.json

4. Modify and save the CwAlarmsRfc.json file. For example, you can replace the contents with something like this:

   {
   "ChangeTypeVersion":    "1.0",
   "ChangeTypeId":         "ct-361vpyun9a9dd",
   "Title":                "CW-ALARMS-RFC"
   }

5. Create the RFC, specifying the CwAlarmsRfc file and the execution parameters file:

   aws amscm create-rfc --cli-input-json file://CwAlarmsRfc.json --execution-parameters file://CwAlarmsParams.json

   You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start.