Creating a connector for Message Queue

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder specified when creating the CLI profile is used by default. To change the default folder, use the yc config set folder-id <folder_ID> command. You can specify a different folder using the --folder-name or --folder-id parameter.

1. View the description of the CLI command to create a connector:

   yc serverless eventrouter connector create message-queue --help
   

2. Create a connector for Message Queue:

   yc serverless eventrouter connector create message-queue \
     --bus-id <bus_ID> \
     --queue-arn <queue_ARN> \
     --service-account-id <service_account_ID> \
     --visibility-timeout <visibility_timeout> \
     --batch-size <group_size> \
     --polling-timeout <poll_timeout> \
     --name <connector_name> \
     --description "<connector_description>" \
     --labels <label_list> \
     --deletion-protection
   

   Where:

   • --bus-id: EventRouter bus ID.

   • --queue-arn: Yandex Message Queue queue ARN.

   • --service-account-id: ID of the service account with permissions to read from the message queue.

   • --visibility-timeout: Time period during which messages are hidden from the queue after one of the recipients has accepted a message. Valid values ​​range from 0 to 12 hours. The default value is 0. This is an optional parameter.

   • --batch-size: Maximum number of messages EventRouter groups together before sending from the source to the rule. Valid values ​​range from 0 to 12. The default value is 10. This is an optional parameter.

   • --polling-timeout: Maximum time during which EventRouter is grouping messages before sending them from the source to the rule. The values may range from 0 to 20 seconds. The default value is 10 seconds. This is an optional parameter.

     The connector groups messages for a period not exceeding the specified survey timeout and sends these to a rule. At the same time, the number of messages does not exceed the specified group size.

   • --name: Connector name. Follow these naming requirements:

     • The name must be from 3 to 63 characters long.
     • It may contain uppercase and lowercase Latin and Cyrillic letters, numbers, hyphens, underscores, and spaces.
     • The first character must be a letter. The last character cannot be a hyphen, underscore, or space.

   • --description: Connector description. This is an optional parameter.

   • --labels: List of labels. This is an optional parameter.

     You can specify one or more labels separated by commas in <key1>=<value1>,<key2>=<value2> format.

   • --deletion-protection: Connector deletion protection. By default, protection is disabled. You cannot delete a connector with this option enabled. To disable deletion protection, specify --no-deletion-protection. This is an optional parameter.

   Result:

   id: f66l8kgo20d8********
   bus_id: f66qn4p7uk6p********
   folder_id: b1g681qpemb4********
   cloud_id: b1gia87mbaom********
   created_at: "2025-02-21T09:04:33.248254Z"
   name: mq-via-cli
   description: created via cli
   labels:
     interface: yccli
     owner: admin
   source:
     message_queue:
       queue_arn: yrn:yc:ymq:ru-central1:b1g681qpemb4********:my-queue
       service_account_id: ajelprpohp7r********
       visibility_timeout: 60s
       batch_size: "3"
       polling_timeout: 0.100s
   deletion_protection: true
   status: RUNNING
   

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

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

If you do not have Terraform yet, install it and configure its Yandex Cloud provider.

To create a connector for Message Queue:

1. In the configuration file, define the parameters of the resources you want to create:

   resource "yandex_serverless_eventrouter_connector" "example_connector" {
     bus_id              = "<bus_ID>"
     name                = "<connector_name>"
     description         = "<connector_description>"
     deletion_protection = <true|false>
   
     labels = {
       <key_1> = "<value_1>"
       <key_2> = "<value_2>"
       ...
       <key_n> = "<value_n>"
     }
   
     ymq {
       queue_arn          = "<queue_ARN>"
       service_account_id = "<service_account_ID>"
       visibility_timeout = "1m"
       batch_size         = "3"
       polling_timeout    = "100ms"
     }
   }
   

   Where:

   • bus_id: EventRouter bus ID.

   • name: Connector name. Follow these naming requirements:

     • The name must be from 3 to 63 characters long.
     • It may contain uppercase and lowercase Latin and Cyrillic letters, numbers, hyphens, underscores, and spaces.
     • The first character must be a letter. The last character cannot be a hyphen, underscore, or space.

   • description: Connector description. This is an optional parameter.

   • deletion_protection: Connector deletion protection, true or false. You cannot delete a connector with this option enabled. This is an optional parameter.

   • labels: List of labels. Provide labels in <key> = "<value>" format. This is an optional parameter.

   • queue_arn: Queue ARN of Yandex Message Queue.

   • service-account-id: ID of the service account with permissions to read from the message queue.

   • visibility_timeout: Time period during which messages are hidden from the queue after one of the recipients has accepted a message. Valid values ​​range from 0 to 12 hours. The default value is 0. This is an optional parameter.

   • batch_size: Maximum number of messages EventRouter groups together before sending from the source to the rule. Valid values ​​range from 0 to 12. The default value is 10. This is an optional parameter.

   • polling_timeout: Maximum time during which EventRouter is grouping messages before sending them from the source to the rule. The values may range from 0 to 20 seconds. The default value is 10 seconds. This is an optional parameter.

     The connector groups messages for a period not exceeding the specified survey timeout and sends these to a rule. At the same time, the number of messages does not exceed the specified group size.

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

2. Create the 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 eventrouter connector list
   

To create a connector for Message Queue, use the Create REST API method for the connector resource or the connector/Create gRPC API call.