Module aws_sdk_iotevents::types

source ·
Expand description

Data structures used by operation inputs/outputs.

Modules§

  • Builders
  • Error types that AWS IoT Events can respond with.

Structs§

  • Specifies whether to get notified for alarm state changes.

  • An action to be performed when the condition is TRUE.

  • Specifies one of the following actions to receive notifications when the alarm state changes.

  • Contains the configuration information of alarm state changes.

  • Contains information about one or more alarm actions.

  • Contains a summary of an alarm model.

  • Contains a summary of an alarm model version.

  • Contains information about one or more notification actions.

  • Defines when your alarm is invoked.

  • Contains the result of the analysis.

  • Contains information that you can use to locate the field in your detector model that the analysis result references.

  • A structure that contains timestamp information. For more information, see TimeInNanos in the AWS IoT SiteWise API Reference.

  • A structure that contains value information. For more information, see AssetPropertyValue in the AWS IoT SiteWise API Reference.

  • A structure that contains an asset property value. For more information, see Variant in the AWS IoT SiteWise API Reference.

  • The attributes from the JSON payload that are made available by the input. Inputs are derived from messages sent to the AWS IoT Events system using BatchPutMessage. Each such message contains a JSON payload. Those attributes (and their paired values) specified here are available for use in the condition expressions used by detectors.

  • Information needed to clear the timer.

  • The detector model and the specific detectors (instances) for which the logging level is given.

  • Information about the detector model.

  • Information about how the detector model is configured.

  • Information that defines how a detector operates.

  • Information about the detector model.

  • Information about the detector model version.

  • Defines an action to write to the Amazon DynamoDB table that you created. The default action payload contains all the information about the detector model instance and the event that triggered the action. You can customize the payload. A separate column of the DynamoDB table receives one attribute-value pair in the payload that you specify.

  • Defines an action to write to the Amazon DynamoDB table that you created. The standard action payload contains all the information about the detector model instance and the event that triggered the action. You can customize the payload. One column of the DynamoDB table receives all attribute-value pairs in the payload that you specify.

  • Contains the configuration information of email notifications.

  • Contains the subject and message of an email.

  • Contains the information of one or more recipients who receive the emails.

  • Specifies the actions to be performed when the condition evaluates to TRUE.

  • Sends information about the detector model instance and the event that triggered the action to an Amazon Kinesis Data Firehose delivery stream.

  • Specifies the default alarm state. The configuration applies to all alarms that were created based on this alarm model.

  • Information about the input.

  • Information about the configuration of an input.

  • The definition of the input.

  • The identifer of the input.

  • Information about the input.

  • Sends an AWS IoT Events input, passing in information about the detector model instance and the event that triggered the action.

  • The identifier of the input routed to AWS IoT Events.

  • Sends information about the detector model instance and the event that triggered the action to a specified asset property in AWS IoT SiteWise.

  • The asset model property identifer of the input routed from AWS IoT SiteWise.

  • The identifer of the input routed from AWS IoT SiteWise.

  • Information required to publish the MQTT message through the AWS IoT message broker.

  • Calls a Lambda function, passing in information about the detector model instance and the event that triggered the action.

  • The values of the AWS IoT Events logging options.

  • Contains the notification settings of an alarm model. The settings apply to all alarms that were created based on this alarm model.

  • Specifies an AWS Lambda function to manage alarm notifications. You can create one or use the AWS Lambda function provided by AWS IoT Events.

  • When entering this state, perform these actions if the condition is TRUE.

  • When exiting this state, perform these actions if the specified condition is TRUE.

  • Specifies the actions performed when the condition evaluates to TRUE.

  • Information needed to configure the payload.

  • The information that identifies the recipient.

  • Information required to reset the timer. The timer is reset to the previously evaluated result of the duration. The duration expression isn't reevaluated when you reset the timer.

  • Contains information about the routed resource.

  • Information needed to set the timer.

  • Information about the variable and its new value.

  • A rule that compares an input property value to a threshold value with a comparison operator.

  • Contains the configuration information of SMS notifications.

  • Information required to publish the Amazon SNS message.

  • Sends information about the detector model instance and the event that triggered the action to an Amazon SQS queue.

  • Contains information about your identity source in AWS Single Sign-On. For more information, see the AWS Single Sign-On User Guide.

  • Information that defines a state of a detector.

  • Metadata that can be used to manage the resource.

  • Specifies the actions performed and the next state entered when a condition evaluates to TRUE.

Enums§

  • When writing a match expression against AlarmModelVersionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against AnalysisResultLevel, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against AnalysisStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against ComparisonOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against DetectorModelVersionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against EvaluationMethod, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against InputStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against LoggingLevel, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
  • When writing a match expression against PayloadType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.