Actions for AWS::IoTEvents Detector Model
---AWS CDK v1 has reached End-of-Support on 2023-06-01. This package is no longer being updated, and users should migrate to AWS CDK v2.
For more information on how to migrate, see the Migrating to AWS CDK v2 guide.
This library contains integration classes to specify actions of state events of Detector Model in @aws-cdk/aws-iotevents.
Instances of these classes should be passed to State defined in @aws-cdk/aws-iotevents
You can define built-in actions to use a timer or set a variable, or send data to other AWS resources.
This library contains integration classes to use a timer or set a variable, or send data to other AWS resources. AWS IoT Events can trigger actions when it detects a specified event or transition event.
Currently supported are:
- Set variable to detector instanse
- Invoke a Lambda function
Set variable to detector instanse
The code snippet below creates an Action that set variable to detector instanse when it is triggered.
# Example automatically generated from non-compiling source. May contain errors.
import aws_cdk.aws_iotevents as iotevents
import aws_cdk.aws_iotevents_actions as actions
# input: iotevents.IInput
state = iotevents.State(
state_name="MyState",
on_enter=[iotevents.Event(
event_name="test-event",
condition=iotevents.Expression.current_input(input),
actions=[actions, [
actions.SetVariableAction("MyVariable",
iotevents.Expression.input_attribute(input, "payload.temperature"))
]
]
)]
)
Invoke a Lambda function
The code snippet below creates an Action that invoke a Lambda function when it is triggered.
import aws_cdk.aws_iotevents as iotevents
import aws_cdk.aws_iotevents_actions as actions
import aws_cdk.aws_lambda as lambda_
# input: iotevents.IInput
# func: lambda.IFunction
state = iotevents.State(
state_name="MyState",
on_enter=[iotevents.Event(
event_name="test-event",
condition=iotevents.Expression.current_input(input),
actions=[actions.LambdaInvokeAction(func)]
)]
)
Metadata
Release files for aws-cdk.aws-iotevents-actions 1.204.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aws-cdk.aws-iotevents-actions-1.204.0.tar.gz | 27.8 kB | Without provenance | Details for aws-cdk.aws-iotevents-actions-1.204.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aws_cdk.aws_iotevents_actions-1.204.0-py3-none-any.whl | Python 3 | none | any | Details for aws_cdk.aws_iotevents_actions-1.204.0-py3-none-any.whl |
Total release size: 55.1 kB
Release files / aws-cdk.aws-iotevents-actions-1.204.0.tar.gz
| Download URL | aws-cdk.aws-iotevents-actions-1.204.0.tar.gz |
|---|---|
| Size | 27.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47b5cfc032439a0f5ce30e0d91385a99cb388b71720f5094ba7feae2b0925b09
|
|
BLAKE2b-256 checksum How to use checksums |
0efb71c1b7d3ec578e2bbaf6903cea885a0310f1ae1ab6f53bacc5bb8da4ec68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Release files / aws_cdk.aws_iotevents_actions-1.204.0-py3-none-any.whl
| Download URL | aws_cdk.aws_iotevents_actions-1.204.0-py3-none-any.whl |
|---|---|
| Size | 27.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d8f48b138ce6e1f3e48c3330f1aae6f755e3e2bf34db2c0f1c1854c14be103cd
|
|
BLAKE2b-256 checksum How to use checksums |
dd010d739f1c234d76c032cc6c63168ed45d64b2cfbd23d3ae151234d9ca3f5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.2
|
Security for aws-cdk.aws-iotevents-actions 1.204.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.