Installing WordPress High Availability using Cloud Apps

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id options.

1. Create a cloud network in the default folder:

   yc vpc network create --name wordpress-network
   

2. Get the list of the cloud networks in the folder:

   yc vpc network list --folder-id b1g6ci08ma55********
   

   Result:

   +----------------------+-------------------+
   |          ID          |      NAME         |
   +----------------------+-------------------+
   | enpavfmgapum******** | wordpress-network |
   | enplom7a98s1******** | default           |
   +----------------------+-------------------+
   

3. Select NAME or ID of the cloud network you need. Create a subnet in the ru-central1-a availability zone:

   yc vpc subnet create \
     --network-id enpavfmgapum******** \
     --zone ru-central1-a \
     --range 192.168.0.0/24
   

   Where:

   • --network-id: Cloud network ID. When creating a subnet, specify the cloud network for the subnet and CIDR.
   • --zone: Subnet availability zone.
   • --range: List of internal IPv4 addresses specified for this subnet, such as 10.0.0.0/22 or 192.168.0.0/16. Make sure the addresses are unique within the network. The minimum subnet size is /28, and the maximum subnet size is /16. Only IPv4 is supported.

   The subnet naming requirements are as follows:

   • Length: between 3 and 63 characters.
   • It can only contain lowercase Latin letters, numbers, and hyphens.
   • It must start with a letter and cannot end with a hyphen.

4. Similarly, create a subnet in the ru-central1-d availability zone.

To create a cloud network, use the create REST API method for the Network resource or the NetworkService/Create gRPC API call and provide the ID of the folder to host the new network in the folderId parameter of your request:

To learn how to find out the folder ID, see Getting the folder ID.

To create subnets in the ru-central1-a and ru-central1-d availability zones, use the create REST API method for the Subnet resource or the SubnetService/Create gRPC API call, and provide the following in your request:

• ID of the folder the subnet will reside in, in the folderId parameter.
• ID of the network the subnet will be placed in, in the networkId parameter.
• ID of the availability zone the subnet will be placed in, in the zoneId parameter.
• List of internal IPv4 addresses specified for this subnet, in the v4CidrBlocks[] array, e.g., 10.0.0.0/22 or 192.168.0.0/16. Make sure the addresses are unique within the network. The minimum subnet size is /28, while the maximum subnet size is /16. Only IPv4 is supported.

To get the subnet ID, use the list REST API method for the Subnet resource or the SubnetService/List gRPC API call and provide the folder ID in the folderId request parameter.

1. Create a public DNS zone:

   yc dns zone create \
     --name example-zone \
     --zone example.com. \
     --public-visibility
   

   Where --zone is your domain name, e.g., example.com.. The --zone parameter value must end with a trailing dot.

   Result:

   id: dns39gihj0ef********
   folder_id: b1g681qpemb4********
   created_at: "2024-09-09T15:23:34.919887Z"
   name: example-zone
   zone: example.com.
   public_visibility: {}
   

   For more information about the yc dns zone create command, see the CLI reference.

2. Delegate your domain to Yandex Cloud servers. Do it by specifying the addresses of the ns1.yandexcloud.net and ns2.yandexcloud.net DNS servers in your domain registrar's account.

   Delegation does not take effect immediately. It usually takes up to 24 hours for internet service providers to update records.

To create a public DNS zone, use the create REST API method for the DnsZone resource or the DnsZoneService/Create gRPC API call.

Delegate your domain to Yandex Cloud servers. Do it by specifying the addresses of the ns1.yandexcloud.net and ns2.yandexcloud.net DNS servers in your domain registrar's account.

To create a secret that will store the Yandex Managed Service for MySQL® database password, run this command:

yc lockbox secret create \
  --name db-password-secret \
  --payload "[{'key': 'db_password', 'text_value': '<password>'}]"

Where text_value is the Yandex Managed Service for MySQL® database password.

Result:

id: e6q0rdjdggjp********
folder_id: b1g681qpemb4********
created_at: "2025-07-12T18:23:49.844Z"
name: db-password-secret
status: ACTIVE
current_version:
  id: e6qbp772i014********
  secret_id: e6q0rdjdggjp********
  created_at: "2025-07-12T18:23:49.844Z"
  status: ACTIVE
  payload_entry_keys:
    - db_password

Similarly, create a secret that will store the WordPress admin password. Specify wp_admin_password in the key parameter.

To create a secret, use the create REST API method for the Secret resource or the SecretService/Create gRPC API call.

Specify db_password in the key parameter for the key to contain the Yandex Managed Service for MySQL® database password. Specify wp_admin_password for the key to store the WordPress administrator password.