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 MetaData Hub
  • About Yandex MetaData Hub
    • Getting started
      • Getting information about clusters
      • Creating a cluster
      • Updating a cluster
      • Stopping and restarting 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
      • Managing cluster access
      • 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 July 2, 2026
View in Markdown

If your cloud network uses security groups, they can hinder the Apache Hive™ Metastore cluster performance. In which case you need to configure the security group assigned to the Apache Hive™ Metastore cluster by adding the following rules for incoming traffic to it:

  • For incoming service traffic:

    • Port range: 30000-32767
    • Protocol: TCP
    • Source: Security group
    • Security group: Current
  • For incoming traffic from clients over Thrift:

    • Description: thrift
    • Port range: 9083
    • Protocol: TCP
    • Source: Address range
    • IPv4 CIDR: 0.0.0.0/0
  • For incoming traffic from clients over REST:

    • Description: iceberg rest (4.2+)
    • Port range: 9001
    • Protocol: TCP
    • Source: Address range
    • IPv4 CIDR: 0.0.0.0/0
  • For incoming load balancer traffic:

    • Protocol: 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, e.g., to allow traffic only in 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 restarting a cluster
Next
Connecting Yandex Data Processing to Apache Hive™ Metastore
© 2026 Direct Cursus Technology L.L.C.