[ aws . ssm-contacts ]
Tags a contact or escalation plan. You can tag only contacts and escalation plans in the first region of your replication set.
See also: AWS API Documentation
See ‘aws help’ for descriptions of global parameters.
tag-resource
--resource-arn <value>
--tags <value>
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
--resource-arn (string)
The Amazon Resource Name (ARN) of the contact or escalation plan.
--tags (list)
A list of tags that you are adding to the contact or escalation plan.
(structure)
A container of a key-value name pair.
Key -> (string)
Name of the object key.
Value -> (string)
Value of the tag.
Shorthand Syntax:
Key=string,Value=string ...
JSON Syntax:
[
{
"Key": "string",
"Value": "string"
}
...
]
--cli-input-json | --cli-input-yaml (string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml.
--generate-cli-skeleton (string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. Similarly, if provided yaml-input it will print a sample input YAML that can be used with --cli-input-yaml. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command.
See ‘aws help’ for descriptions of global parameters.
To tag a contact
The following tag-resource example tags a specified contact with the provided tag key value pair.
aws ssm-contacts tag-resource \
--resource-arn "arn:aws:ssm-contacts:us-east-1:111122223333:contact/akuam" \
--tags '[{"Key":"group1","Value":"1"}]'
This command produces no output.
For more information, see Tagging in the Incident Manager User Guide.
None