Creating a trigger for Yandex IoT Core that passes messages to the Cloud Functions function

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 function, run this 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-function-id <function ID> \
  --invoke-function-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-function-id: Function ID.
• --invoke-function-service-account-id: Service account with rights to invoke the function.
• --retry-attempts: Number of invocation retries before the trigger moves a message to the Dead Letter Queue. This is an optional parameter. You can specify values from 1 to 5, 1 being default.
• --retry-interval: Time after which the function will be invoked again if the current attempt fails. This is an optional parameter. You can specify values from 10 to 60 seconds, 10 being default.
• --dlq-queue-id: Dead Letter Queue ID. This is an optional parameter.
• --dlq-service-account-id: Service account with the permission to write messages to the Dead Letter Queue. This is an optional parameter.

Result:

id: a1sl0mkmimfj3uv52fr8
folder_id: b1g88tflru0ek1omtsu0
created_at: "2019-09-25T13:54:35.654935Z"
name: iot-trigger
rule:
  iot_message:
    registry_id: arenou2oj4ct42eq8g3n
    device_id: areqjd6un3afc3cefcvm
    mqtt_topic: $devices/areqjd6un3afc3cefcvm/events
    invoke_function:
      function_id: d4eofc7n0m03lmudse8l
      function_tag: $latest
      service_account_id: aje3932acd0c5ur7dagp
      retry_settings:
        retry_attempts: "1"
        interval: 10s
status: ACTIVE

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it by configuration files. They store the infrastructure description in HashiCorp Configuration Language (HCL). Terraform and its providers are distributed under the Mozilla Public License.

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

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

If you do not have Terraform yet, 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.

   Example of the configuration file structure:

   resource "yandex_function_trigger" "my_trigger" {
     name        = "<trigger name>"
     description = "<trigger description>"
     iot {
       registry_id = "<registry ID>"
       device_id   = "<device ID>"
       topic       = "<topic ID>"
     }
     function {
       id                 = "<function ID>"
       service_account_id = "<service account ID>"
     }
   }
   

   Where:

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

     • The length can be from 3 to 63 characters.
     • It may contain lowercase Latin letters, numbers, and hyphens.
     • The first character must be a letter. The last character can't be a hyphen.

   • description: Trigger description.

   • iot: Topic parameters:

     • registry-id: Registry ID.
     • device-id: Device ID. If you're creating a trigger for a registry topic, you can omit this parameter.
     • topic: ID of the topic you want to create a trigger for.

   • function: Settings for the function, which will be activated by the trigger:

     • id: Function ID.
     • service_account_id: ID of the service account with rights to invoke a function.

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

2. Make sure the configuration files are valid.

   1. In the command line, go to the directory where you created the configuration file.

   2. Run the check using this command:

      terraform plan
      

   If the configuration is described correctly, the terminal will display a list of created resources and their parameters. If the configuration contains any errors, Terraform will point them out.

3. Deploy cloud resources.

   1. If the configuration does not contain any errors, run this command:

      terraform apply
      

   2. Confirm the resource creation: type yes in the terminal and press Enter.

      Once you are done, all the resources you need will be created in the specified folder. You can verify that the resources are there and their configuration is correct using the management console or the following CLI command:

      yc serverless trigger get <trigger ID>
      

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.