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 MPP Analytics for PostgreSQL
  • Getting started
    • Overview of Greenplum® and Apache Cloudberry™ DBMSs in Yandex MPP Analytics for PostgreSQL
    • Resource relationships
    • Host classes
    • High availability clusters
    • Calculating the cluster configuration
    • Networking in Yandex MPP Analytics for PostgreSQL
    • Quotas and limits
    • Backups
    • Resource groups
    • Sharding
    • Users and roles
    • User authentication
    • Command center
    • Command center settings
    • External tables
    • Managing connections
    • Expanding a cluster
    • Maintenance
    • Table and system folder vacuuming
    • DBMS settings
    • Differences between Apache Cloudberry™ and Greenplum®
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Concepts
  2. User authentication

User authentication

Written by
Yandex Cloud
Updated at July 6, 2026
View in Markdown

User authentication in Yandex MPP Analytics for PostgreSQL is set up under User authentication using rules. This section is an interface for the pg_hba.conf file management with some limitations:

  • Some connection types and authentication methods are not available.
  • Using system databases and users is not allowed.
  • Special values and regular expressions for databases and users are not available.

For more information about these limitations, see Authentication rule settings.

Each authentication rule determines the connection type, DB name, user name or user group name, host FQDN or IP range to connect from, and authentication method. Rules are read from top to bottom, and the first suitable one is applied for authentication. If authentication based on the first suitable rule fails, other rules do not apply.

If no authentication rules are set, the default rule is used; it allows authentication for all users in any database and from any host using the md5 method (password-based authentication). If the authentication rules are set, the default rule is read last.

Authentication rule settingsAuthentication rule settings

You can specify the following authentication settings when adding or updating rules:

Available connection types:

  • host: TCP/IP with or without SSL encryption
  • hostssl: TCP/IP with SSL encryption
  • hostnossl: TCP/IP without SSL encryption

The following is not available to databases and users:

  • System databases, e.g., postgres.
  • System users, e.g., mdb_admin.
  • Special values, e.g., all or sameuser.
  • Regular expressions

The name of a database user group must begin with +, e.g, +dbwriters.

As an address, you can use a host's FQDN, IP range, or the special all value that allows connections from any host:

  • rc1a-goh2a9tr********.mdb.yandexcloud.net
  • 172.20.143.89/32
  • ::0/0
  • all

The following authentication methods are supported:

  • md5: Password-based authentication. For more information, see this PostgreSQL article.
  • iam: IAM-based authentication.
  • reject: User connection is not allowed.

Read more about settings in this PostgreSQL guide.

Was the article helpful?

Previous
Users and roles
Next
Command center
© 2026 Direct Cursus Technology L.L.C.