Contact UsTry it for free
© 2025 Direct Cursus Technology L.L.C.

Creating a demo Cloud Apps product

Written by
Updated at October 13, 2025

In this tutorial, you will create a basic Cloud Apps product with a Yandex Managed Service for PostgreSQL cluster and Yandex Compute Cloud VM connected to it, install the created app (product instance), and test its behavior.

Getting started

  1. Upload your disk image to Yandex Compute Cloud. To complete this tutorial, you can use this Ubuntu image. When using this image to install an app in Cloud Apps, a VM will be created automatically.

    Tip

    For your demo app, you can create a VM from a Cloud Marketplace public image, such as Ubuntu 22.04 LTS, and build an image from that VM's disk. See also Getting started with Packer.

  2. Fill out the questionnaire on the Yandex Cloud Marketplace page.

  3. Register an account.

  4. Create a Cloud Apps product.

Create a configuration

  1. Select the product for which you want to create a configuration.
  2. Navigate the Configurations tab.
  3. Click Create configuration.
  4. On the From scratch tab:
    1. Specify the following:
      • Folder to save your configuration to. You need the cloudapps.editor role for that folder.
      • Configuration name, e.g., demo.
    2. Click Create. Your demo configuration will appear on the Configurations tab with the Draft status.

Set up your configuration

Add an artifact

  1. Select the demo configuration.
  2. In the Selection of artifacts tab, click Add artifact.
  3. Select Disk image as the Artifact type.
  4. Specify a Name, e.g., ubuntu.
  5. Select the disk image you created when Getting started.
  6. Click Add.

Create a form

  1. Navigate to the Parameters tab.

  2. Add the following fields one by one by clicking Add field:

    • Database username:

      Parameter Value Description
      Variable type String
      Field view Base Plain string
      Variable name pg_username You can use the variable name when creating resources to access the value entered by the user.
      Required Selected This field is required.
      Pattern ^[a-z][a-z0-9]*$ The regular expression that the database username must match.
      Pattern error Wrong name The error message the user sees if the database username does not match the specified pattern.
      Field title (RU) Database username The field name the user sees in the interface.
      Field title (EN) Database username The field name the user sees in the interface.

    • Secret with DB user password:

      Parameter Value Description
      Variable type String
      Field view Lockbox Secret Yandex Lockbox secret with the DB user password
      Variable name pg_password_secret You can use the variable name when creating resources to access the value entered by the user.
      Required Selected This field is required.
      Field title (RU) Secret with DB user password The field name the user sees in the interface.
      Field title (EN) Secret with DB user password The field name the user sees in the interface.

    • Cloud network:

      Parameter Value Description
      Variable type String
      Field view VPC network Yandex Virtual Private Cloud cloud network for your app in Cloud Apps
      Variable name vpc_network You can use the variable name when creating resources to access the value entered by the user.
      Required Selected This field is required.
      Field title (RU) Cloud network The field name the user sees in the interface.
      Field title (EN) Cloud network The field name the user sees in the interface.

    • Subnet 1:

      Parameter Value Description
      Variable type String
      Field view VPC subnet Yandex Virtual Private Cloud subnet
      Variable name vpc_subnet_0 You can use the variable name when creating resources to access the value entered by the user.
      Required Selected This field is required.
      Field title (RU) Subnet 1 The field name the user sees in the interface.
      Field title (EN) Subnet 1 The field name the user sees in the interface.

    • Subnet 2:

      Parameter Value Description
      Variable type String
      Field view VPC subnet Yandex Virtual Private Cloud subnet
      Variable name vpc_subnet_1 You can use the variable name when creating resources to access the value entered by the user.
      Required Selected This field is required.
      Field title (RU) Subnet 2 The field name the user sees in the interface.
      Field title (EN) Subnet 2 The field name the user sees in the interface.

Add resources

  1. Navigate to the Resources tab.

  2. Add the following resources one by one by clicking Add resource:

    Note

    User resources are resources the user creates on their own prior to installing the app.

    New resources are those automatically created in the user folder while installing the app.

    • Data source → VPC Network:

      Parameter Value Description
      Name vpc-network Click next to the auto-generated cloud network name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Network id Parameter → vpc_network The cloud network ID will be retrieved from the Cloud network field as specified by the user when filling out the form.

    • Data source → VPC Subnet:

      Subnet 1

      Parameter Value Description
      Name vpc-subnet-0 Click next to the auto-generated subnet name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Subnet id Parameter → vpc_subnet_0 The subnet ID will be retrieved from the Subnet 1 field as specified by the user when filling out the form.

      Subnet 2

      Parameter Value Description
      Name vpc-subnet-1 Click next to the auto-generated subnet name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Subnet id Parameter → vpc_subnet_1 The cloud network ID will be retrieved from the Subnet 2 field as specified by the user when filling out the form.

    • Data source → Lockbox Secret:

      Parameter Value Description
      Name lockbox-secret-with-db-password Click next to the auto-generated Yandex Lockbox secret name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Secret id Parameter → pg_password_secret The Lockbox secret ID will be retrieved from the Secret with DB user password field as specified by the user when filling out the form.

    • New resource → Service account:

      Parameter Value Description
      Name service-account Click next to the auto-generated service account name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Folder id Application attribute → Folder ID The service account to use for deploying the application will be automatically created in the same folder the user selected for app installation.
      Name Value → my-best-app The name of the automatically created service account will be my-best-app.

    • New resource → Folder member:

      Parameter Value Description
      Name lockbox-payload-viewer Click next to the auto-generated folder user name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Folder id Application attribute → Folder ID The specified roles will be assigned to the service account for the folder the user selected for app installation.
      Member Value → Service account → Reference → service-account → id The specified roles will be assigned to the my-best-app service account.
      Role Value → lockbox.payloadViewer The service account will get the lockbox.payloadViewer role required for accessing the Yandex Lockbox secret that stores the DB user password.

    • New resource → PostgreSQL Cluster:

      Parameter Value Description
      Name postgres-cluster Click next to the Yandex Managed Service for PostgreSQL cluster’s auto-generated name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Environment Value → PRODUCTION The environment where you want to create the cluster. The production environment is used for stable app versions.
      Folder id Application attribute → Folder ID The cluster will be automatically created in the same folder the user selected for app installation.
      Name Value → my-best-app-pg-cluster The new cluster’s name will be my-best-app-pg-cluster.
      Network id Resource → vpc-network The cluster will be automatically created in the cloud network named vpc-network.
      Config Value → Key: Version → Value → 16 DBMS version.
      Config Value → Key: Resources → Value → Key: Disk size → Value → 10 Disk size.
      Config Value → Key: Resources → Value → Key: Disk type id → Value → network-ssd Disk type.
      Config Value → Key: Resources → Value → Key: Resource preset id → Value → c3-c2-m4 Host class
      Host Value → Item 1 → Value → Key: Subnet id → Resource → vpc-subnet-0 The cluster will include two hosts. The first host will reside in vpc-subnet-0.
      Host Value → Item 1 → Value → Key: Zone → Reference → vpc-subnet-0 → zone The first host will reside in the same availability zone as vpc-subnet-0.
      Host Value → Item 2 → Value → Key: Subnet id → Resource → vpc-subnet-1 The cluster will include two hosts. The second host will reside in vpc-subnet-1.
      Host Value → Item 2 → Value → Key: Zone → Reference → vpc-subnet-1 → zone The second host will reside in the same availability zone as vpc-subnet-1.

    • New resource → PostgreSQL User:

      Parameter Value Description
      Name postgresql-user Click next to the auto-generated PostgreSQL user name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Cluster id Resource → postgres-cluster The cluster to which pg_username will have access.
      Name Parameter → pg_username The username will be retrieved from the Database username field as specified by the user when filling out the form.
      Password Reference → lockbox-secret-with-db-password → entries[0].text_value To access the cluster, pg_username will use the password retrieved from lockbox-secret-with-db-password.

    • New resource → PostgreSQL Database:

      Parameter Value Description
      Name postgresql-db Click next to the auto-generated PostgreSQL DB name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Cluster id Resource → postgres-cluster The cluster where the pg_username database will be automatically created.
      Name Parameter → pg_username The database name will be retrieved from the Database username field as specified by the user when filling out the form. The DB user name and the DB name match in the demo example.
      Owner Reference → postgresql-user → name The DB owner name will be the PostgreSQL user name, postgresql-user.

    • New resource → Compute Instance:

      Parameter Value Description
      Name instance Click next to the auto-generated VM name to change it. The resource name must be unique within the configuration. The user will see it when installing the app.
      Folder id Application attribute → Folder ID The Compute Cloud VM will be automatically created in the same folder the user selected for app installation.
      Boot disk Value → Key: Initialize params → Value → Key: Image id → Artifact → ubuntu Disk image to create the VM from. You added it at this step.
      Boot disk Value → Key: Initialize params → Value → Key: Size → Value → 32 Disk size.
      Boot disk Value → Key: Initialize params → Value → Key: Type → Value → network-ssd Disk type.
      Network interface Value → Item 1 → Value → Key: Subnet id → Resource → vpc-subnet-0 The VM will reside in vpc-subnet-0.
      Resources Value → Key: Cores → Value → 2 Number of vCPUs
      Resources Value → Key: Memory → Value → 8 Amount of RAM
      Metadata Value → Item 1 → Key: pg-host-0 → Reference → postgres-cluster → host[0].fqdn Settings for connecting from the VM to the database. First cluster host.
      Metadata Value → Item 2 → Key: pg-host-1 → Reference → postgres-cluster → host[1].fqdn Settings for connecting from the VM to the database. Second cluster host.
      Metadata Value → Item 3 → Key: pg-username → Reference → postgres-user → name Settings for connecting from the VM to the database. Database username.
      Metadata Value → Item 4 → Key: pg-password-lockbox-secret-id → Parameter → postgres_password_secret Settings for connecting from the VM to the database. DB user password.
      Platform id Value → standard-v3 Platform on which the VM will run.
      Service account id Resource → service-account The service account with read permissions for the Lockbox secret that stores the DB user password.
      Zone Reference → vpc-subnet-0 → zone The VM will reside in the same availability zone as vpc-subnet-0.
      Depends on lockbox-payload-viewer The VM will be created after the lockbox-payload-viewer resource.

  3. Click Save to save the configuration.

Install the app

  1. In the top-right corner, click Run.
  2. Fill out the form.
  3. Click Install.
  4. Wait for the service to verify the resources you are creating and click Confirm.
  5. The application list will now contain your demo-app with the Deploying status. Wait until the status switches to Deployed. This may take several minutes.
  6. Check all newly created resources. Connect to the VM and make sure it can access the Yandex Managed Service for PostgreSQL cluster.
Previous
Product access requests
Next
Partner profile