Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • 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
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Serverless Integrations
  • Comparison with other Yandex Cloud services
    • All guides
        • Viewing roles assigned for a resource
        • Assigning roles for a resource
        • Revoking roles assigned for a resource
    • Viewing operations with service resources
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Public materials
  • Release notes
  1. Step-by-step guides
  2. EventRouter
  3. Managing permissions to access resources
  4. Revoking roles assigned for a resource

Revoking roles assigned for an EventRouter resource

Written by
Yandex Cloud
Updated at June 9, 2025
CLI
API

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

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

Run this command to revoke a role for an EventRouter resource from:

  • User:

    yc serverless <resource_type> remove-access-binding <resource_name_or_ID> \
      --user-account-id <user_ID> \
      --role <role>
    
  • Service account:

    yc serverless <resource_type> remove-access-binding <resource_name_or_ID> \
      --service-account-id <service_account_ID> \
      --role <role>
    
  • All authorized users (the All authenticated users public group):

    yc serverless <resource_type> remove-access-binding <resource_name_or_ID> \
      --all-authenticated-users \
      --role <role>
    

Example

Revoking a role for a bus from a service account:

yc serverless eventrouter bus remove-access-binding epdplu8jn7sr******** \
  --service-account-id rrbilgiqaptv******** \
  --role serverless.eventrouter.auditor

Result:

...1s...done (3s)

Use the updateAccessBinding REST API method for the relevant resource or the <service>/UpdateAccessBinding gRPC API call.

For example, for a bus, use the updateAccessBinding REST API method for the Bus resource or the BusService/UpdateAccessBinding gRPC API call.

Was the article helpful?

Previous
Assigning roles for a resource
Next
Viewing operations with service resources
© 2025 Direct Cursus Technology L.L.C.