aws ssm create-ops-item
Creates a new OpsItem. You must have permission in AWS Identity and Access Management (IAM) to create a new OpsItem. For more information, see Getting started with OpsCenter in the AWS Systems Manager User Guide. Operations engineers and IT professionals use OpsCenter to view, investigate, and remediate operational issues impacting the performance and health of their AWS resources. For more information, see AWS Systems Manager OpsCenter in the AWS Systems Manager User Guide
Options
| Name | Description |
|---|---|
--description <string> | Information about the OpsItem |
--ops-item-type <string> | The type of OpsItem to create. Currently, the only valid values are /aws/changerequest and /aws/issue |
--operational-data <map> | Operational data is custom data that provides useful reference details about the OpsItem. For example, you can specify log files, error strings, license keys, troubleshooting tips, or other relevant data. You enter operational data as key-value pairs. The key has a maximum length of 128 characters. The value has a maximum size of 20 KB. Operational data keys can't begin with the following: amazon, aws, amzn, ssm, /amazon, /aws, /amzn, /ssm. You can choose to make the data searchable by other users in the account or you can restrict search access. Searchable data means that all users with access to the OpsItem Overview page (as provided by the DescribeOpsItems API action) can view and search on the specified data. Operational data that is not searchable is only viewable by users who have access to the OpsItem (as provided by the GetOpsItem API action). Use the /aws/resources key in OperationalData to specify a related resource in the request. Use the /aws/automations key in OperationalData to associate an Automation runbook with the OpsItem. To view AWS CLI example commands that use these keys, see Creating OpsItems manually in the AWS Systems Manager User Guide |
--notifications <list> | The Amazon Resource Name (ARN) of an SNS topic where notifications are sent when this OpsItem is edited or changed |
--priority <integer> | The importance of this OpsItem in relation to other OpsItems in the system |
--related-ops-items <list> | One or more OpsItems that share something in common with the current OpsItems. For example, related OpsItems can include OpsItems with similar error messages, impacted resources, or statuses for the impacted resource |
--source <string> | The origin of the OpsItem, such as Amazon EC2 or Systems Manager. The source name can't contain the following strings: aws, amazon, and amzn |
--title <string> | A short heading that describes the nature of the OpsItem and the impacted resource |
--tags <list> | Optional metadata that you assign to a resource. You can restrict access to OpsItems by using an inline IAM policy that specifies tags. For more information, see Getting started with OpsCenter in the AWS Systems Manager User Guide. Tags use a key-value pair. For example: Key=Department,Value=Finance To add tags to an existing OpsItem, use the AddTagsToResource action |
--category <string> | Specify a category to assign to an OpsItem |
--severity <string> | Specify a severity to assign to an OpsItem |
--actual-start-time <timestamp> | The time a runbook workflow started. Currently reported only for the OpsItem type /aws/changerequest |
--actual-end-time <timestamp> | The time a runbook workflow ended. Currently reported only for the OpsItem type /aws/changerequest |
--planned-start-time <timestamp> | The time specified in a change request for a runbook workflow to start. Currently supported only for the OpsItem type /aws/changerequest |
--planned-end-time <timestamp> | The time specified in a change request for a runbook workflow to end. Currently supported only for the OpsItem type /aws/changerequest |
--cli-input-json <string> | Performs service operation based on the JSON string provided. The JSON string follows the format provided by ``--generate-cli-skeleton``. If other arguments are provided on the command line, the CLI 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 |
--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``. If provided with the value ``output``, it validates the command inputs and returns a sample output JSON for that command |