Get started
Yandex Serverless Containers

Creating a trigger for Yandex IoT Core that sends messages to a Serverless Containers container

Written by

Create a trigger for a device topic or the Yandex IoT Core service registry and process copies of messages using a Serverless Containers container.

Warning

The trigger must be in the same cloud with the registry or device it reads messages from.

Before you begin

To create a trigger, you need:

  • A container that the trigger will invoke. If you don't have a container:

  • (optional) A Dead Letter Queue where messages that could not be processed by a container will be redirected. If you don't have a queue, create one.

  • Service account with rights to invoke the container and (optionally) write messages to the Dead Letter Queue. You can use the same service account or different ones. If you don't have a service account, create one.

Creating a trigger

Note

The trigger is initiated within 5 minutes of being created.

  1. In the management console, select the folder where you wish to create your trigger.

  2. Open Serverless Containers.

  3. On the left-hand panel, select Triggers.

  4. Click Create trigger.

  5. Under Basic parameters:

    • Enter a name and description for the trigger.
    • In the Type field, select Yandex IoT Core.
    • In the Launched resource field, select Container.

  6. Under Yandex IoT Core message settings, specify the registry, device, and MQTT topic to create a trigger for. If you are creating a trigger for a registry topic, you don't need to specify a device or an MQTT topic.

  7. Under Container settings, select a container and specify:

  8. (optional) Under Repeat request settings:

    • In the Interval field, specify the time delay for the container to be invoked again if the current attempt fails. Values can be from 10 to 60 seconds. The default is 10 seconds.
    • In the Number of attempts field, specify the number of invocation retries before the trigger moves a message to the Dead Letter Queue. Values can be from 1 to 5. The default is 1.

  9. (optional) Under Dead Letter Queue settings, select the Dead Letter Queue and the service account with write privileges for this queue.

  10. Click Create trigger.

If you don't have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To create a trigger that invokes a container, run the command:

yc serverless trigger create internet-of-things \
  --name <trigger_name> \
  --registry-id <registry_ID> \
  --device-id <device_ID> \
  --mqtt-topic '$devices/<device_ID>/events' \
  --invoke-container-id <container_ID> \
  --invoke-container-service-account-id <service_account_ID> \
  --retry-attempts 1 \
  --retry-interval 10s \
  --dlq-queue-id <Dead_Letter_Queue_ID> \
  --dlq-service-account-id <service_account_ID>

Where:

  • --name: Trigger name.
  • --registry-id: Registry ID.
  • --device-id: Device ID. If you're creating a trigger for a registry topic, you can omit this parameter.
  • --mqtt-topic: The topic you want to create a trigger for.
  • --invoke-container-id: Container ID.
  • --invoke-container-service-account-id: Service account with rights to invoke the container.
  • --retry-attempts: Time to retry invoking the container if the current attempt fails. Optional. Values can be from 10 to 60 seconds. The default is 10 seconds.
  • --retry-interval: The number of invocation retries before the trigger moves a message to the Dead Letter Queue. Optional. Values can be from 1 to 5. The default is 1.
  • --dlq-queue-id: Dead Letter Queue ID. Optional.
  • --dlq-service-account-id: Service account with rights to write messages to the Dead Letter Queue. Optional.

Result:

id: a1s5msktij**********
folder_id: b1gmit33hg**********
created_at: "2022-10-24T15:19:15.353909857Z"
name: iot-trigger
rule:
  iot_message:
    registry_id: arenou2oj4**********
    device_id: areqjd6un3**********
    mqtt_topic: $devices/areqjd6un**********/events
    invoke_container:
      container_id: bba5jb38o8**********
      service_account_id: aje3932acd**********
      retry_settings:
        retry_attempts: "1"
        interval: 10s
status: ACTIVE

You can create a trigger for Yandex IoT Core using the create.

Checking the result

Make sure the trigger is working properly. To do this, view container logs that show information about invocations.

See also

In this article: