Sets or updates the AWS IoT Events logging options.
If you update the value of any loggingOptions
field, it takes up to one minute for the change to take effect. If you change the policy attached to the role you specified in the roleArn
field (for example, to correct an invalid policy), it takes up to five minutes for that change to take effect.
See also: AWS API Documentation
See ‘aws help’ for descriptions of global parameters.
put-logging-options
--logging-options <value>
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
--logging-options
(structure)
The new values of the AWS IoT Events logging options.
roleArn -> (string)
The ARN of the role that grants permission to AWS IoT Events to perform logging.
level -> (string)
The logging level.
enabled -> (boolean)
If TRUE, logging is enabled for AWS IoT Events.
detectorDebugOptions -> (list)
Information that identifies those detector models and their detectors (instances) for which the logging level is given.
(structure)
The detector model and the specific detectors (instances) for which the logging level is given.
detectorModelName -> (string)
The name of the detector model.
keyValue -> (string)
The value of the input attribute key used to create the detector (the instance of the detector model).
Shorthand Syntax:
roleArn=string,level=string,enabled=boolean,detectorDebugOptions=[{detectorModelName=string,keyValue=string},{detectorModelName=string,keyValue=string}]
JSON Syntax:
{
"roleArn": "string",
"level": "ERROR"|"INFO"|"DEBUG",
"enabled": true|false,
"detectorDebugOptions": [
{
"detectorModelName": "string",
"keyValue": "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. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated.
See ‘aws help’ for descriptions of global parameters.
Note
To use the following examples, you must have the AWS CLI installed and configured. See the Getting started guide in the AWS CLI User Guide for more information.
Unless otherwise stated, all examples have unix-like quotation rules. These examples will need to be adapted to your terminal’s quoting rules. See Using quotation marks with strings in the AWS CLI User Guide .
To set logging options
The following put-logging-options
example sets or updates the AWS IoT Events logging options. If you update the value of any loggingOptions` field, it can take up to one minute for the change to take effect. Also, if you change the policy attached to the role you specified in the ``roleArn
field (for example, to correct an invalid policy) it can take up to five minutes for that change to take effect.
aws iotevents put-logging-options \
--cli-input-json file://logging-options.json
Contents of logging-options.json
:
{
"loggingOptions": {
"roleArn": "arn:aws:iam::123456789012:role/IoTEventsRole",
"level": "DEBUG",
"enabled": true,
"detectorDebugOptions": [
{
"detectorModelName": "motorDetectorModel",
"keyValue": "Fulton-A32"
}
]
}
}
This command produces no output.
For more information, see PutLoggingOptions in the AWS IoT Events API Reference.
None