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 MetaData Hub
  • About Yandex MetaData Hub
    • Getting started
      • Getting information about clusters
      • Creating a cluster
      • Updating a cluster
      • Stopping and starting a cluster
      • Configuring security groups
      • Connecting Yandex Data Processing to Apache Hive™ Metastore
      • Exporting and importing a cluster
      • Connecting to a Yandex Object Storage bucket with a bucket policy
      • Transferring logs to Cloud Logging
      • Deleting a cluster
    • Service roles for access management
    • Troubleshooting
    • Terraform reference
    • Audit Trails events
  • Access management
  • Quotas and limits
  • Pricing policy
  • Public materials
  • Release notes
  1. Apache Hive™ Metastore
  2. Step-by-step guides
  3. Configuring security groups

Configuring Apache Hive™ Metastore cluster security groups

Written by
Yandex Cloud
Updated at October 15, 2025

If the cloud network uses security groups, they can hinder the Apache Hive™ Metastore cluster performance. Set up the default security group to work with Apache Hive™ Metastore. To do this, add the following rules to it:

  • For incoming client traffic:

    • Port range: 30000-32767
    • Protocol: Any (Any)
    • Source: CIDR
    • CIDR blocks: 0.0.0.0/0
  • For incoming load balancer traffic:

    • Port range: 10256
    • Protocol: Any (Any)
    • Source: Load balancer healthchecks

If you plan to use multiple security groups for a cluster, enable all traffic between these groups.

Note

You can specify more granular rules for your security groups, such as only allowing traffic within specific subnets.

Apache® and Apache Hive™ are either registered trademarks or trademarks of the Apache Software Foundation in the United States and/or other countries.

Was the article helpful?

Previous
Stopping and starting a cluster
Next
Connecting Yandex Data Processing to Apache Hive™ Metastore
© 2025 Direct Cursus Technology L.L.C.