Creating an MySQL® cluster

If you do not have the Yandex Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To create a Managed Service for MySQL® cluster:

1. Check whether the folder has any subnets for the Managed Service for MySQL® cluster hosts:

   yc vpc subnet list
   

   If there are no subnets in the folder, create the required subnets in Yandex Virtual Private Cloud.

2. View the description of the create Managed Service for MySQL® cluster CLI command:

   yc managed-mysql cluster create --help
   

3. Specify the Managed Service for MySQL® cluster parameters in the create command:

   yc managed-mysql cluster create \
     --name=<cluster_name> \
     --environment <environment> \
     --network-name <network_name> \
     --host zone-id=<availability_zone>,`
       `subnet-id=<subnet_ID>,`
       `assign-public-ip=<public_access_to_host>,`
       `priority=<priority_when_selecting_master_host>,`
       `backup-priority=<backup_priority> \
     --mysql-version <MySQL®_version> \
     --resource-preset <host_class> \
     --user name=<username>,password=<user_password> \
     --database name=<DB_name> \
     --disk-size <storage_size_in_GB> \
     --disk-type <network-hdd|network-ssd|network-ssd-nonreplicated|local-ssd> \
     --security-group-ids <list_of_security_group_IDs>
   

   You need to specify the subnet-id if the selected availability zone has two or more subnets.

   Where:

   • environment: Environment, prestable or production.

   • assign-public-ip: Public access to the host, true or false.

   • --disk-type: Disk type.

     Warning

     You cannot change disk type after you create a cluster.

   • priority: Host priority when selecting a new master host, between 0 and 100.

   • backup-priority: Backup priority, between 0 and 100.

   • mysql-version: MySQL® version, 5.7 or 8.0.

   Configure additional Managed Service for MySQL® cluster settings, if required:

   yc managed-mysql cluster create \
     ...
     --backup-window-start <backup_start_time> \
     --backup-retain-period-days=<backup_retention_period> \
     --datalens-access=<true_or_false> \
     --websql-access=<true_or_false> \
     --deletion-protection \
     --performance-diagnostics enabled=true,`
                              `sessions-sampling-interval=<session_sampling_interval>,`
                              `statements-sampling-interval=<statement_sampling_interval>
   

   Where:

   • backup-window-start: Backup start time.
   • backup-retain-period-days: Automatic backup retention period, in days.
   • datalens-access: Enables access from Yandex DataLens. The default value is false. For more information about how to connect to DataLens, see Connecting to a MySQL® cluster from DataLens.
   • websql-access: Enables SQL queries against cluster databases from the Yandex Cloud management console using Yandex WebSQL. The default value is false.
   • deletion-protection: Cluster deletion protection.
   • performance-diagnostics: Enabling statistics collection for cluster performance diagnostics. For sessions-sampling-interval and statements-sampling-interval, possible values range from 1 to 86400 seconds.

   The DB name may contain Latin letters, numbers, hyphens, and underscores. The name may be up to 63 characters long. Such names as mysql, sys, information_schema, and performance_schema are reserved for Managed Service for MySQL®. You cannot create DBs with these names.

   Enabled deletion protection will not prevent a manual connection with the purpose to delete database contents.

   Configure the DBMS settings, if required.

   Note

   When creating a cluster, the anytime maintenance mode is set by default. You can set a specific maintenance period when updating the cluster settings.

Terraform allows you to quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. Configuration files store the infrastructure description in the HashiCorp Configuration Language (HCL). Terraform and its providers are distributed under the Business Source License.

For more information about the provider resources, see the documentation on the Terraform website or the mirror.

If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

If you don't have Terraform, install it and configure the Yandex Cloud provider.

To create a Managed Service for MySQL® cluster:

1. In the configuration file, describe the parameters of the resources you want to create:

   • DB cluster: Description of the cluster and its hosts

   • Database: Description of the cluster DB

     The DB name may contain Latin letters, numbers, hyphens, and underscores. The name may be up to 63 characters long. Such names as mysql, sys, information_schema, and performance_schema are reserved for Managed Service for MySQL®. You cannot create DBs with these names.

   • User: Description of the cluster user

   • Network: Description of the cloud network where a cluster will be located. If you already have a suitable network, you don't have to describe it again.

   • Subnets: Description of the subnets to connect the cluster hosts to. If you already have suitable subnets, you don't have to describe them again.

   Here is an example of the configuration file structure:

   resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
     name                = "<cluster_name>"
     environment         = "<environment>"
     network_id          = "<network_ID>"
     version             = "<MySQL®_version>"
     security_group_ids  = [ "<list_of_security_group_IDs>" ]
     deletion_protection = <cluster_deletion_protection>
   
     resources {
       resource_preset_id = "<host_class>"
       disk_type_id       = "<disk_type>"
       disk_size          = "<storage_size_in_GB>"
     }
   
     host {
       zone             = "<availability_zone>"
       subnet_id        = "<subnet_ID>"
       assign_public_ip = <public_access_to_host>
       priority         = <priority_when_selecting_master_host>
       backup_priority  = <backup_priority>
     }
   }
   
   resource "yandex_mdb_mysql_database" "<DB_name>" {
     cluster_id = "<cluster_ID>"
     name       = "<DB_name>"
   }
   
   resource "yandex_mdb_mysql_user" "<username>" {
     cluster_id = "<cluster_ID>"
     name       = "<username>"
     password   = "<user_password>"
     permission {
       database_name = "<DB_name>"
       roles         = ["ALL"]
     }
   }
   
   resource "yandex_vpc_network" "<network_name>" { name = "<network_name>" }
   
   resource "yandex_vpc_subnet" "<subnet_name>" {
     name           = "<subnet_name>"
     zone           = "<availability_zone>"
     network_id     = "<network_ID>"
     v4_cidr_blocks = ["<range>"]
   }
   

   Where:

   • environment: Environment, PRESTABLE or PRODUCTION.
   • version: MySQL® version, 5.7 or 8.0.
   • deletion_protection: Cluster deletion protection, true or false.
   • assign_public_ip: Public access to the host, true or false.
   • priority: Host priority when selecting a new master host, between 0 and 100.
   • backup_priority: Backup priority, between 0 and 100.

   Enabled deletion protection will not prevent a manual connection with the purpose to delete database contents.

   • To set up the maintenance window (for disabled clusters as well), add the maintenance_window block to the cluster description:

     resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
       ...
       maintenance_window {
         type = <maintenance_type>
         day  = <day_of_week>
         hour = <hour>
       }
       ...
     }
     

     Where:

     • type: Maintenance type. The possible values include:
       • anytime: Anytime.
       • weekly: By schedule.
     • day: Day of the week for the weekly type in DDD format, e.g., MON.
     • hour: Hour of the day for the weekly type in the HH format, e.g., 21.

   • To enable access from DataLens and allow execution of SQL queries from the management console using Yandex WebSQL, add a section named access to the cluster description:

     resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
       ...
       access {
         data_lens = <true_or_false>
         web_sql   = <true_or_false>
         ...
       }
       ...
     }
     

   • To set the backup start time, add the backup_window_start section to the Managed Service for MySQL® cluster description:

     resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
       ...
       backup_window_start {
         hours   = <hour>
         minutes = <minute>
       }
       ...
     }
     

     Where:

     • hours: Backup start hour.
     • minutes: Backup start minute.

   • To set the retention period for backup files, define the backup_retain_period_days parameter in the Managed Service for MySQL® cluster description:

     resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
       ...
         backup_retain_period_days = <backup_retention_period>
         ...
     }
     

     Where backup_retain_period_days is the automatic backup retention period, in days.

     The possible values range from 7 to 60. The default value is 7.

   • To enable statistics collection for cluster performance diagnostics, add the performance_diagnostics section to your Managed Service for MySQL® cluster description:

     resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
       ...
       performance_diagnostics {
         enabled = true
         sessions_sampling_interval = <session_sampling_interval>
         statements_sampling_interval = <statement_sampling_interval>
       }
       ...
     }
     

     For sessions_sampling_interval and statements_sampling_interval, possible values range from 1 to 86400 seconds.

   For more information about the resources you can create with Terraform, see the provider documentation.

2. Make sure the configuration files are correct.

   1. In the command line, go to the folder where you created the configuration file.

   2. Run a check using this command:

      terraform plan
      

   If the configuration is described correctly, the terminal will display a list of created resources and their parameters. If the configuration contains any errors, Terraform will point them out. This is a test step; no resources will be created.

3. Create a Managed Service for MySQL® cluster.

   1. If the configuration does not contain any errors, run this command:

      terraform apply
      

   2. Confirm that you want to create the resources.

   After this, all required resources will be created in the specified folder and the IP addresses of the VMs will be displayed in the terminal. You can check the new resources and their configuration using the management console.

   Time limits

   A Terraform provider sets the timeout for Managed Service for MySQL® cluster operations:

   • Creating a cluster, including by restoring one from a backup: 15 minutes.
   • Editing a cluster, including the MySQL® version update: 60 minutes.
   • Deleting a cluster: 15 minutes.

   Operations exceeding the set timeout are interrupted.

   How do I change these limits?

   Add the timeouts block to the cluster description, for example:

   resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
     ...
     timeouts {
       create = "1h30m" # 1 hour 30 minutes
       update = "2h"    # 2 hours
       delete = "30m"   # 30 minutes
     }
   }
   

1. Get an IAM token for API authentication and put it into the environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Create a file named body.json and add the following contents to it:

   {
       "folderId": "<folder_ID>",
       "name": "<cluster_name>",
       "environment": "<environment>",
       "networkId": "<network_ID>",
       "securityGroupIds": [
           "<security_group_1_ID>",
           "<security_group_2_ID>",
           ...
           "<security_group_N_ID>"
       ],
       "deletionProtection": <deletion_protection:_true_or_false>,
       "configSpec": {
           "version": "<MySQL®_version>",
           "resources": {
               "resourcePresetId": "<host_class>",
               "diskSize": "<storage_size_in_bytes>",
               "diskTypeId": "<disk_type>"
           },
           "access": {
               "dataLens": <access_to_DataLens:_true_or_false>,
               "webSql": <access_to_WebSQL:_true_or_false>,
               "dataTransfer": <access_to_Data_Transfer:_true_or_false>
           },
           "performanceDiagnostics": {
               "enabled": <activate_statistics_collection:_true_or_false>,
               "sessionsSamplingInterval": "<session_sampling_interval>",
               "statementsSamplingInterval": "<statement_sampling_interval>"
           }
       },
       "databaseSpecs": [
           {
               "name": "<DB_name>"
           },
           { <similar_configuration_for_DB_2> },
           { ... },
           { <similar_configuration_for_DB_N> }
       ],
       "userSpecs": [
           {
               "name": "<username>",
               "password": "<user_password>",
               "permissions": [
                   {
                       "databaseName": "<DB_name>",
                       "roles": [
                           "<privilege_1>", "<privilege_2>", ..., "<privilege_N>"
                       ]
                   }
               ]
           },
           { <similar_configuration_for_user_2> },
           { ... },
           { <similar_configuration_for_user_N> }
       ],
       "hostSpecs": [
           {
               "zoneId": "<availability_zone>",
               "subnetId": "<subnet_ID>",
               "assignPublicIp": <public_host_address:_true_or_false>
           },
           { <similar_configuration_for_host_2> },
           { ... },
           { <similar_configuration_for_host_N> }
       ]
   }
   

   Where:

   • folderId: Folder ID. You can request it with a list of folders in the cloud.

   • name: Cluster name.

   • environment: Cluster environment, PRODUCTION or PRESTABLE.

   • networkId: ID of the network to place the cluster in.

   • securityGroupIds: Security group IDs.

   • deletionProtection: Protection of the cluster, its databases, and users against deletion.

   • configSpec: Cluster settings:

     • version: PostgreSQL version.

     • resources: Cluster resources:

       • resourcePresetId: Host class.
       • diskSize: Disk size in bytes.
       • diskTypeId: Disk type.

     • access: Settings for cluster access to the following Yandex Cloud services:

       • dataLens: Yandex DataLens
       • webSql: Yandex WebSQL
       • dataTransfer: Yandex Data Transfer

   • performanceDiagnostics: Settings for collecting statistics:

     • enabled: Enables statistics collection.
     • sessionsSamplingInterval: Session sampling interval, 1 to 86400 seconds.
     • statementsSamplingInterval: Statement sampling interval, 1 to 86400 seconds.

   • databaseSpecs: Database settings as an array of elements, one for each DB. Each element has the name parameter (the DB name).

     The DB name may contain Latin letters, numbers, hyphens, and underscores. The name may be up to 63 characters long. Such names as mysql, sys, information_schema, and performance_schema are reserved for Managed Service for MySQL®. You cannot create DBs with these names.

   • userSpecs: User settings as an array of elements, one for each user. Each element has the following structure:

     • name: Username.

     • password: User password.

     • permissions: User permission settings:

       • databaseName: Name of the database the user gets access to.
       • roles: Array of user's privileges, each provided as a separate string in the array. For the list of possible values, see User privileges in a cluster.

       For each database, add a separate item with permission settings to the permissions array.

   • hostSpecs: Cluster host settings as an array of elements, one for each host. Each element has the following structure:

     • zoneId: Availability zone.
     • subnetId: Subnet ID.
     • assignPublicIp: Permission to connect to the host from the internet.

3. Use the Cluster.create method and make a request, e.g., via cURL:

   curl \
       --request POST \
       --header "Authorization: Bearer $IAM_TOKEN" \
       --header "Content-Type: application/json" \
       --url 'https://mdb.api.cloud.yandex.net/managed-mysql/v1/clusters' \
       --data "@body.json"
   

4. View the server response to make sure the request was successful.

1. Get an IAM token for API authentication and put it into the environment variable:

   export IAM_TOKEN="<IAM_token>"
   

2. Clone the cloudapi repository:

   cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
   

   Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

3. Create a file named body.json and add the following contents to it:

   {
       "folder_id": "<folder_ID>",
       "name": "<cluster_name>",
       "environment": "<environment>",
       "network_id": "<network_ID>",
       "security_group_ids": [
           "<security_group_1_ID>",
           "<security_group_2_ID>",
           ...
           "<security_group_N_ID>"
       ],
       "deletion_protection": <deletion_protection:_true_or_false>,
       "config_spec": {
           "version": "<MySQL®_version>",
           "resources": {
               "resource_preset_id": "<host_class>",
               "disk_size": "<storage_size_in_bytes>",
               "disk_type_id": "<disk_type>"
           },
           "access": {
               "data_lens": <access_to_DataLens:_true_or_false>,
               "web_sql": <access_to_WebSQL:_true_or_false>,
               "data_transfer": <access_to_Data_Transfer:_true_or_false>
           },
           "performance_diagnostics": {
               "enabled": <activate_statistics_collection:_true_or_false>,
               "sessions_sampling_interval": "<session_sampling_interval>",
               "statements_sampling_interval": "<statement_sampling_interval>"
           }
       },
       "database_specs": [
             {
                 "name": "<DB_name>"
             },
             { <similar_configuration_for_DB_2> },
             { ... },
             { <similar_configuration_for_DB_N> }
         ],
       "user_specs": [
           {
               "name": "<username>",
               "password": "<user_password>",
               "permissions": [
                   {
                       "database_name": "<DB_name>",
                       "roles": [
                           "<privilege_1>", "<privilege_2>", ..., "<privilege_N>"
                       ]
                   }
               ]
           }
       ],
       "host_specs": [
           {
               "zone_id": "<availability_zone>",
               "subnet_id": "<subnet_ID>",
               "assign_public_ip": <public_host_address:_true_or_false>
           }
       ]
   }
   

   Where:

   • folder_id: Folder ID. You can request it with a list of folders in the cloud.

   • name: Cluster name.

   • environment: Cluster environment, PRODUCTION or PRESTABLE.

   • network_id: ID of the network to place the cluster in.

   • security_group_ids: Security group IDs.

   • deletion_protection: Protection of the cluster, its databases, and users against deletion.

   • config_spec: Cluster settings:

     • version: PostgreSQL version.

     • resources: Cluster resources:

       • resource_preset_id: Host class.
       • disk_size: Disk size in bytes.
       • disk_type_id: Disk type.

     • access: Settings for cluster access to the following Yandex Cloud services:

       • data_lens: Yandex DataLens
       • web_sql: Yandex WebSQL
       • data_transfer: Yandex Data Transfer

   • performance_diagnostics: Settings for collecting statistics:

     • enabled: Enables statistics collection.
     • sessions_sampling_interval: Session sampling interval, 1 to 86400 seconds.
     • statements_sampling_interval: Statement sampling interval, 60 to 86400 seconds.

   • database_specs: Database settings as an array of elements, one for each DB. Each element has the name parameter (the DB name).

   • user_specs: User settings as an array of elements, one for each user. Each element has the following structure:

     • name: Username.

     • password: User password.

     • permissions: User permission settings:

       • database_name: Name of the database the user gets access to.
       • roles: Array of user's privileges, each provided as a separate string in the array. For the list of possible values, see User privileges in a cluster.

       For each database, add a separate item with permission settings to the permissions array.

   • host_specs: Cluster host settings as an array of elements, one for each host. Each element has the following structure:

     • zone_id: Availability zone.
     • subnet_id: Subnet ID.
     • assign_public_ip: Permission to connect to the host from the internet.

4. Use the ClusterService/Create call and make a request, e.g., via gRPCurl:

   grpcurl \
       -format json \
       -import-path ~/cloudapi/ \
       -import-path ~/cloudapi/third_party/googleapis/ \
       -proto ~/cloudapi/yandex/cloud/mdb/mysql/v1/cluster_service.proto \
       -rpc-header "Authorization: Bearer $IAM_TOKEN" \
       -d @ \
       mdb.api.cloud.yandex.net:443 \
       yandex.cloud.mdb.mysql.v1.ClusterService.Create \
       < body.json
   

5. View the server response to make sure the request was successful.

Create a Managed Service for MySQL® cluster and a network for it with the following test specifications:

• Name: my-mysql

• Version: 8.0.

• Environment: PRESTABLE

• Cloud ID: b1gq90dgh25bebiu75o.

• Folder ID: b1gia87mbaomkfvsleds.

• New network: mynet

• Host: s2.micro (one host), new subnet: mysubnet, availability zone: ru-central1-a. Range for mysubnet: 10.5.0.0/24.

• New security group: mysql-sg, allowing connections to Managed Service for MySQL® clusters from the Internet through port 3306.

• Network SSD storage (network-ssd): 20 GB.

• User: user1, password: user1user1.

• With one db1 database, in which the user1 user has full rights (same as GRANT ALL PRIVILEGES on db1.*).

• Protection against accidental Managed Service for MySQL® cluster deletion: Enabled.

The configuration file for this Managed Service for MySQL® cluster is as follows:

resource "yandex_mdb_mysql_cluster" "my-mysql" {
  name                = "my-mysql"
  environment         = "PRESTABLE"
  network_id          = yandex_vpc_network.mynet.id
  version             = "8.0"
  security_group_ids  = [ yandex_vpc_security_group.mysql-sg.id ]
  deletion_protection = true

  resources {
    resource_preset_id = "s2.micro"
    disk_type_id       = "network-ssd"
    disk_size          = 20
  }

  host {
    zone      = "ru-central1-a"
    subnet_id = yandex_vpc_subnet.mysubnet.id
  }
}

resource "yandex_mdb_mysql_database" "db1" {
  cluster_id = yandex_mdb_mysql_cluster.my-mysql.id
  name       = "db1"
}

resource "yandex_mdb_mysql_user" "<username>" {
  cluster_id = yandex_mdb_mysql_cluster.my-mysql.id
  name       = "user1"
  password   = "user1user1"
  permission {
    database_name = yandex_mdb_mysql_database.db1.name
    roles         = ["ALL"]
  }
}

resource "yandex_vpc_network" "mynet" {
  name = "mynet"
}

resource "yandex_vpc_security_group" "mysql-sg" {
  name       = "mysql-sg"
  network_id = yandex_vpc_network.mynet.id

  ingress {
    description    = "MySQL®"
    port           = 3306
    protocol       = "TCP"
    v4_cidr_blocks = [ "0.0.0.0/0" ]
  }
}

resource "yandex_vpc_subnet" "mysubnet" {
  name           = "mysubnet"
  zone           = "ru-central1-a"
  network_id     = yandex_vpc_network.mynet.id
  v4_cidr_blocks = ["10.5.0.0/24"]
}

Create a Managed Service for MySQL® cluster and a network for it with the following test specifications:

• Name: my-mysql-3.

• Version: 8.0.

• Environment: PRESTABLE.

• Cloud ID: b1gq90dgh25bebiu75o.

• Folder ID: b1gia87mbaomkfvsleds.

• New network: mynet.

• s2.micro public hosts: 3.

  One host will be added to each one of the new subnets:

  • mysubnet-a: 10.5.0.0/24, availability zone: ru-central1-a.
  • mysubnet-b: 10.6.0.0/24, availability zone: ru-central1-b.
  • mysubnet-d: 10.7.0.0/24, availability zone: ru-central1-d.

  These subnets will belong to the mynet network.

  The host residing in mysubnet-b will have the backup priority. Backups will be created from this host's data unless you choose it to be the master host.

• New security group: mysql-sg, allowing connections to Managed Service for MySQL® clusters from the internet through port 3306.

• Network SSD storage (network-ssd): 32 GB.

• User: user1, password: user1user1.

• With one db1 database, in which the user1 user has full rights (same as GRANT ALL PRIVILEGES on db1.*).

The configuration file for this Managed Service for MySQL® cluster is as follows:

resource "yandex_mdb_mysql_cluster" "my-mysql-3" {
  name                = "my-mysql-3"
  environment         = "PRESTABLE"
  network_id          = yandex_vpc_network.mynet.id
  version             = "8.0"
  security_group_ids  = [ yandex_vpc_security_group.mysql-sg.id ]

  resources {
    resource_preset_id = "s2.micro"
    disk_type_id       = "network-ssd"
    disk_size          = 32
  }

  host {
    zone             = "ru-central1-a"
    subnet_id        = yandex_vpc_subnet.mysubnet-a.id
    assign_public_ip = true
  }

  host {
    zone             = "ru-central1-b"
    subnet_id        = yandex_vpc_subnet.mysubnet-b.id
    assign_public_ip = true
    backup_priority  = 10
  }

  host {
    zone             = "ru-central1-d"
    subnet_id        = yandex_vpc_subnet.mysubnet-d.id
    assign_public_ip = true
  }
}

resource "yandex_mdb_mysql_database" "db1" {
  cluster_id = yandex_mdb_mysql_cluster.my-mysql-3.id
  name       = "db1"
}

resource "yandex_mdb_mysql_user" "user1" {
  cluster_id = yandex_mdb_mysql_cluster.my-mysql-3.id
  name       = "user1"
  password   = "user1user1"
  permission {
    database_name = yandex_mdb_mysql_database.db1.name
    roles         = ["ALL"]
  }
}

resource "yandex_vpc_network" "mynet" {
  name = "mynet"
}

resource "yandex_vpc_security_group" "mysql-sg" {
  name       = "mysql-sg"
  network_id = yandex_vpc_network.mynet.id

  ingress {
    description    = "MySQL®"
    port           = 3306
    protocol       = "TCP"
    v4_cidr_blocks = [ "0.0.0.0/0" ]
  }
}

resource "yandex_vpc_subnet" "mysubnet-a" {
  name             = "mysubnet-a"
  zone             = "ru-central1-a"
  network_id       = yandex_vpc_network.mynet.id
  v4_cidr_blocks   = ["10.5.0.0/24"]
}

resource "yandex_vpc_subnet" "mysubnet-b" {
  name             = "mysubnet-b"
  zone             = "ru-central1-b"
  network_id       = yandex_vpc_network.mynet.id
  v4_cidr_blocks   = ["10.6.0.0/24"]
}

resource "yandex_vpc_subnet" "mysubnet-d" {
  name             = "mysubnet-d"
  zone             = "ru-central1-d"
  network_id       = yandex_vpc_network.mynet.id
  v4_cidr_blocks   = ["10.7.0.0/24"]
}