Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Serverless Integrations
  • Comparing with other Yandex Cloud services
    • All guides
        • Editing a connector
        • Running a connector
        • Stopping a connector
        • Deleting a connector
    • Viewing operations with service resources
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Public materials
  • Release notes
  1. Step-by-step guides
  2. EventRouter
  3. Managing a connector
  4. Stopping a connector

Stopping a connector

Written by
Yandex Cloud
Updated at June 18, 2026
View in Markdown

When a connector is stopped, it no longer sends messages to the bus.

Management console
CLI
API
  1. In the management console, navigate to the folder where you want to stop a connector.
  2. Navigate to Serverless Integrations.
  3. In the left-hand panel, click EventRouter.
  4. Select the bus in question.
  5. Navigate to the Connectors tab.
  6. In the line with the connector, click and select Stop.

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

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

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

    yc serverless eventrouter connector stop --help
    
  2. Get a list of connectors:

    yc serverless eventrouter connector list
    

    Result:

    +----------------------+-----------------------+----------------------+----------------------+---------+---------------------+
    |          ID          |         NAME          |        BUS ID        |      FOLDER ID       | STATUS  | DELETION PROTECTION |
    +----------------------+-----------------------+----------------------+----------------------+---------+---------------------+
    | f66g4h59ih2g******** | connector-my-ydb-flow | f66qn4p7uk6p******** | b1g681qpemb4******** | STOPPED | true                |
    | f66g6jcnc5no******** | yds-via-cli           | f66qn4p7uk6p******** | b1g681qpemb4******** | RUNNING | false               |
    | f66jfhcg1u71******** | mq-via-terraform      | f66qn4p7uk6p******** | b1g681qpemb4******** | RUNNING | false               |
    +----------------------+-----------------------+----------------------+----------------------+---------+---------------------+
    
  3. Stop the connector:

    yc serverless eventrouter connector stop <connector_name_or_ID>
    

    Result:

    id: f66g4h59ih2g********
    bus_id: f66qn4p7uk6p********
    folder_id: b1g681qpemb4********
    cloud_id: b1gia87mbaom********
    created_at: "2025-02-20T15:30:05.248052Z"
    name: renamed-ydb
    ...
    status: STOPPED
    

To stop a connector, use the Stop REST API method for the Connector resource or the Connector/Stop gRPC API call.

Was the article helpful?

Previous
Running a connector
Next
Deleting a connector
© 2026 Direct Cursus Technology L.L.C.