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.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • mdb_mysql_cluster
          • mdb_mysql_database
          • mdb_mysql_user

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for permission
  • Nested Schema for connection_limits
  1. Terraform reference
  2. Resources
  3. Managed Service for MySQL
  4. Data Sources
  5. mdb_mysql_user

yandex_mdb_mysql_user (Data Source)

Written by
Yandex Cloud
Updated at November 17, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for permission
    • Nested Schema for connection_limits

Get information about a Yandex Managed MySQL user. For more information, see the official documentation.

Example usageExample usage

//
// Get information about existing MDB MySQL Database User.
//
data "yandex_mdb_mysql_user" "my_user" {
  cluster_id = "some_cluster_id"
  name       = "test"
}

output "permission" {
  value = data.yandex_mdb_mysql_user.foo.permission
}

SchemaSchema

RequiredRequired

  • cluster_id (String) The ID of the MySQL cluster.
  • name (String) The name of the MySQL user.

OptionalOptional

  • permission (Block Set) (see below for nested schema)

Read-OnlyRead-Only

  • authentication_plugin (String) Authentication plugin. Allowed values: MYSQL_NATIVE_PASSWORD, CACHING_SHA2_PASSWORD, SHA256_PASSWORD, MYSQL_NO_LOGIN, MDB_IAMPROXY_AUTH (for version 5.7 MYSQL_NATIVE_PASSWORD, SHA256_PASSWORD, MYSQL_NO_LOGIN, MDB_IAMPROXY_AUTH).
  • connection_limits (List of Object) (see below for nested schema)
  • connection_manager (Map of String) Connection Manager connection configuration. Filled in by the server automatically.
  • global_permissions (Set of String) List user's global permissions. Allowed permissions: REPLICATION_CLIENT, REPLICATION_SLAVE, PROCESS, FLUSH_OPTIMIZER_COSTS, SHOW_ROUTINE, MDB_ADMIN for clear list use empty list. If the attribute is not specified there will be no changes.
  • id (String) The ID of this resource.

Nested Schema for Nested Schema for permission

Optional:

  • roles (List of String) List user's roles in the database. Allowed roles: ALL,ALTER,ALTER_ROUTINE,CREATE,CREATE_ROUTINE,CREATE_TEMPORARY_TABLES, CREATE_VIEW,DELETE,DROP,EVENT,EXECUTE,INDEX,INSERT,LOCK_TABLES,SELECT,SHOW_VIEW,TRIGGER,UPDATE,REFERENCES.

Read-Only:

  • database_name (String) The name of the database that the permission grants access to.

Nested Schema for Nested Schema for connection_limits

Read-Only:

  • max_connections_per_hour (Number) Max connections per hour.

  • max_questions_per_hour (Number) Max questions per hour.

  • max_updates_per_hour (Number) Max updates per hour.

  • max_user_connections (Number) Max user connections.

Was the article helpful?

Previous
mdb_mysql_database
Next
mdb_mysql_cluster
© 2025 Direct Cursus Technology L.L.C.