Creating a trigger that will send messages to a Serverless Containers container from a Yandex IoT Core registry or device topic

If you do not 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 this command:

yc serverless trigger create internet-of-things \
  --name <trigger_name> \
  --registry-id <registry_ID> \
  --device-id <device_ID> \
  --mqtt-topic '<broker_MQTT_topic>' \
  --batch-size <message_batch_size> \
  --batch-cutoff <maximum_wait_time> \
  --invoke-container-id <container_ID> \
  --invoke-container-service-account-id <service_account_ID> \
  --retry-attempts <number_of_retry_invocation_attempts> \
  --retry-interval <interval_between_retry_attempts> \
  --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 are creating a trigger for a registry topic, you can omit this parameter.
• --mqtt-topic: MQTT topic you want to create a trigger for. This is an optional parameter. If this parameter is skipped, the trigger fires for all registry or device topics.

• --batch-size: Size of the message batch from MQTT topics. This is an optional parameter. The values may range from 1 to 10. The default value is 1.
• --batch-cutoff: Maximum waiting time. This is an optional parameter. The values may range from 1 to 60 seconds. The default value is 1 second. The trigger groups messages for a period not exceeding batch-cutoff and sends them to a container. The number of messages cannot exceed batch-size.

• --invoke-container-id: Container ID.
• --invoke-container-service-account-id: ID of the service account with permissions to invoke the container.
• --retry-attempts: Number of invocation retries before the trigger moves a message to the dead-letter queue. This is an optional parameter. The values may range from 1 to 5. The default value is 1.
• --retry-interval: Time to retry invoking the container if the current attempt fails. This is an optional parameter. The values may range from 10 to 60 seconds. The default value is 10 seconds.
• --dlq-queue-id: Dead-letter queue ID. This is an optional parameter.
• --dlq-service-account-id: ID of the service account with write permissions to the dead-letter queue. This is an optional parameter.

Result:

id: a1s5msktijh2********
folder_id: b1gmit33hgh2********
created_at: "2022-10-24T15:19:15.353909857Z"
name: iot-trigger
rule:
  iot_message:
    registry_id: arenou2oj4h2********
    device_id: areqjd6un3h2********
    mqtt_topic: $devices/areqjd6unh2********/events
    batch_settings:
      size: "1"
      cutoff: 0s
    invoke_container:
      container_id: bba5jb38o8h2********
      service_account_id: aje3932acdh2********
      retry_settings:
        retry_attempts: "1"
        interval: 10s
status: ACTIVE

Terraform allows you to quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. Configuration files store the infrastructure description in the HashiCorp Configuration Language (HCL). Terraform and its providers are distributed under the Business Source License.

For more information about the provider resources, see the documentation on the Terraform website or the mirror.

If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

If you don't have Terraform, install it and configure the Yandex Cloud provider.

To create a trigger for Yandex IoT Core:

1. In the configuration file, describe the trigger parameters:

   resource "yandex_function_trigger" "my_trigger" {
     name = "<trigger_name>"
     container {
       id                 = "<container_ID>"
       service_account_id = "<service_account_ID>"
       retry_attempts     = "<number_of_retry_invocation_attempts>"
       retry_interval     = "<interval_between_retry_attempts>"
     }
     iot {
       registry_id  = "<registry_ID>"
       device_id    = "<device_ID>"
       topic        = "<broker_MQTT_topic>"
       batch_cutoff = "<maximum_wait_time>"
       batch_size   = "<message_batch_size>"
     }
     dlq {
      queue_id           = "<dead_letter_queue_ID>"
      service_account_id = "<service_account_ID>"
    }
   }
   

   Where:

   • name: Trigger name. The name format is as follows:

     • The name must be from 3 to 63 characters long.
     • It may contain lowercase Latin letters, numbers, and hyphens.
     • The first character must be a letter and the last character cannot be a hyphen.

   • container-name: Container parameters:

     • id: Container ID.
     • service_account_id: ID of the service account with rights to invoke the container.
     • retry_attempts: Number of invocation retries before the trigger moves a message to the dead letter queue. This is an optional parameter. The values may range from 1 to 5. The default value is 1.
     • retry_intervall: Time to retry invoking the container if the current attempt fails. This is an optional parameter. The values may range from 10 to 60 seconds. The default value is 10 seconds.

   • iot: Trigger parameters:

     • registry-id: Registry ID.
     • device-id: Device ID. If you are creating a trigger for a registry topic, you can omit this parameter.
     • topic: MQTT topic you want to create a trigger for. This is an optional parameter. If this parameter is skipped, the trigger fires for all registry or device topics.
     • batch_cutoff: Maximum wait time. This is an optional parameter. The values may range from 1 to 60 seconds. The default value is 1 second. The trigger groups messages for a period not exceeding batch_cutoff and sends them to a container. The number of messages cannot exceed batch_size.
     • batch-size: Size of the message batch from MQTT topics. This is an optional parameter. The values may range from 1 to 10. The default value is 1.
   • dlq: Dead-letter queue message parameters:
     • queue_id: Dead-letter queue ID. This is an optional parameter.
     • service_account_id: ID of the service account with write permissions to the dead-letter queue. This is an optional parameter.

   For more information about resource parameters in Terraform, see the provider documentation.

2. Create resources:

   1. In the terminal, change to the folder where you edited the configuration file.

   2. Make sure the configuration file is correct using the command:

      terraform validate
      

      If the configuration is correct, the following message is returned:

      Success! The configuration is valid.
      

   3. Run the command:

      terraform plan
      

      The terminal will display a list of resources with parameters. No changes are made at this step. If the configuration contains errors, Terraform will point them out.

   4. Apply the configuration changes:

      terraform apply
      

   5. Confirm the changes: type yes in the terminal and press Enter.

   Terraform will create all the required resources. You can check the new resources using the management console or this CLI command:

   yc serverless trigger list
   

To create a trigger for Yandex IoT Core, use the create REST API method for the Trigger resource or the TriggerService/Create gRPC API call.