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.
Yandex Managed Service for Valkey™
  • Getting started
    • All tutorials
    • Storing PHP sessions in Yandex Managed Service for Valkey™
    • Migrating a database to Yandex Managed Service for Valkey™
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Required paid resources
  • Getting started
  • Prepare the infrastructure
  • Configure additional settings
  • Configure PHP to use the Yandex Managed Service for Valkey™ cluster as storage for sessions
  • Check whether PHP session data is saved to the Yandex Managed Service for Valkey™ cluster
  • Delete the resources you created
  1. Tutorials
  2. Storing PHP sessions in Yandex Managed Service for Valkey™

Using a Yandex Managed Service for Valkey™ cluster as a PHP session storage

Written by
Yandex Cloud
Updated at May 5, 2025
  • Required paid resources
  • Getting started
    • Prepare the infrastructure
    • Configure additional settings
  • Configure PHP to use the Yandex Managed Service for Valkey™ cluster as storage for sessions
  • Check whether PHP session data is saved to the Yandex Managed Service for Valkey™ cluster
  • Delete the resources you created

You can use Yandex Managed Service for Valkey™ clusters for storing PHP session data.

To configure a Yandex Managed Service for Valkey™ cluster as PHP session storage:

  1. Configure PHP to use the Yandex Managed Service for Valkey™ cluster as storage for sessions.
  2. Check whether PHP session data is saved to the Yandex Managed Service for Valkey™ cluster.

If you no longer need the resources you created, delete them.

Required paid resourcesRequired paid resources

The support cost includes:

  • Yandex Managed Service for Valkey™ target cluster fee: Using computing resources allocated to hosts, and its disk space (see Valkey™ pricing).
  • Fee for using public IP addresses if public access is enabled for cluster hosts (see Virtual Private Cloud pricing).
  • VM fee: using computing resources, storage, and public IP address (see Compute Cloud pricing).

Getting startedGetting started

Prepare the infrastructurePrepare the infrastructure

Manually
Terraform
  1. If you use Virtual Private Cloud security groups, configure them. Add TCP settings to the security group to allow the following:

    • Incoming traffic on port 22 from any IP addresses for SSH.
    • Outgoing and incoming traffic on ports 80 and 443 to and from any IP address for HTTP/HTTPS.
    • Outgoing and incoming traffic on port 6379 to and from internal network IP addresses for Valkey™.

    For more information, see Security groups.

  2. Create a virtual machine with LAMP/LEMP in Yandex Compute Cloud of any suitable configuration.

    When creating a VM, select the security group that you set up earlier. To check the security settings, enter the VM's public IP address in the browser address bar: the default page of the web server should be displayed.

  3. Create a Yandex Managed Service for Valkey™ cluster with any suitable configuration. When creating a Yandex Managed Service for Valkey™ cluster, specify the same network and security groups as those of the VM hosting the web server.

  1. If you do not have Terraform yet, install it.

  2. Get the authentication credentials. You can add them to environment variables or specify them later in the provider configuration file.

  3. Configure and initialize a provider. There is no need to create a provider configuration file manually, you can download it.

  4. Place the configuration file in a separate working directory and specify the parameter values. If you did not add the authentication credentials to environment variables, specify them in the configuration file.

  5. Download the configuration file for the appropriate cluster type to the same working directory:

    • redis-cluster-non-sharded-and-vm-for-php.tf: For a non-sharded cluster.
    • redis-cluster-sharded-and-vm-for-php.tf: For a sharded cluster.

    Each file describes the following:

    • Network.
    • Subnet.
    • Default security group and rules required to connect to the cluster and VM from the internet.
    • Yandex Managed Service for Valkey™ cluster.
    • Virtual machine.
  6. Specify the following in the configuration file:

    • Password to access the Yandex Managed Service for Valkey™ cluster.
    • ID of the public LAMP/LEMP image.
    • Username and path to the public key file for accessing the virtual machine. By default, the specified username is ignored in the image that is currently used. A user with the ubuntu username is created instead. Use it to connect to the VM.
  7. Make sure the Terraform configuration files are correct using this command:

    terraform validate
    

    If there are any errors in the configuration files, Terraform will point them out.

  8. Create the required infrastructure:

    1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

    All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

Configure additional settingsConfigure additional settings

  1. Connect to the VM with the web server via SSH and configure it:

    • Install certificates:

      sudo mkdir --parents /usr/local/share/ca-certificates/Yandex/ && \
      sudo wget "https://storage.yandexcloud.net/cloud-certs/CA.pem" \
          --output-document /usr/local/share/ca-certificates/Yandex/YandexInternalRootCA.crt
      
    • Prepare the environment and install the phpredis library using pecl:

      sudo apt update && \
      sudo apt install php-dev pkg-php-tools redis-tools --yes && \
      sudo pecl channel-update pecl.php.net && \
      sudo pecl install redis
      
    • Become the owner of the /var/www/html/ directory and delete all its contents:

      sudo chown <username> /var/www/html/ --recursive && \
      rm /var/www/html/*
      

Configure PHP to use the Yandex Managed Service for Valkey™ cluster as storage for sessionsConfigure PHP to use the Yandex Managed Service for Valkey™ cluster as storage for sessions

  1. Make changes to the php.ini configuration file for your web server.

    The php.ini file is usually located in the following directory:

    • /etc/php/7.2/apache2/ for Apache
    • /etc/php/7.2/fpm/ for NGINX

    To find out the location of php.ini, run the sudo find /etc/ -name php.ini command.

    Note

    There is no need to make any changes to php.ini for the PHP CLI.

    Non-sharded cluster
    Sharded cluster
    [PHP]
    ...
    extension = redis
    ...
    [Session]
    session.save_handler = redis
    session.save_path = "tcp://<Valkey™_master_host_FQDN>:6379?auth=<password>"
    
    [PHP]
    ...
    extension = redis
    ...
    [Session]
    session.save_handler = rediscluster
    session.save_path = "seed[]=<FQDN1>:6379&seed[]=<FQDN2>:6379&seed[]=<FQDN3>:6379&auth=<password>"
    

    Here, <FQDN1>, <FQDN2>, and <FQDN3> are fully qualified domain names of cluster master hosts. For example, for a cluster with three shards and password for password, the session.save_path parameter value will look like this:

    session.save_path = "seed[]=rc1a-t9h8gxqo********.mdb.yandexcloud.net:6379&seed[]=rc1b-7qxk0h3b********.mdb.yandexcloud.net:6379&seed[]=rc1c-spy1c1i4********.mdb.yandexcloud.net:6379&auth=password"
    

    For more information about how to connect to clusters, see Setting up a connection.

  2. Restart the web server:

    • sudo systemctl restart apache2 for Apache
    • sudo systemctl restart php7.2-fpm for NGINX

Check whether PHP session data is saved to the Yandex Managed Service for Valkey™ clusterCheck whether PHP session data is saved to the Yandex Managed Service for Valkey™ cluster

  1. In the /var/www/html/ directory, create a file named index.php that will be outputting the powers of 2:

    <?php
    session_start();
    
    $count = isset($_SESSION['count']) ? $_SESSION['count'] : 1;
    
    echo $count;
    
    $_SESSION['count'] = $count * 2;
    

    Each time the page is refreshed, the output value will increase. The $count variable value will be saved in the session data. A unique key will be created for each session in Valkey™.

  2. Connect to the Valkey™ cluster from the VM via redis-cli:

    redis-cli -c -h <master_host_FQDN> -a <password>
    

    Enter the following command to see what keys are stored in Valkey™:

    KEYS *
    
    (empty list or set)
    

    The returned result shows that no data is currently stored in Valkey™.

  3. Check whether user sessions are saved when connecting to the web server:

    1. Enter the public IP of the VM hosting the web server in the browser address bar. The first time you open the page, 1 will be output.
    2. Refresh the page several times: the output value will increase.
    3. Open the page in a different browser: the count will start from 1.
    4. Refresh the page several times: the output value will increase, too.

    The fact that the $count variable value is saved between the browser page updates shows that the configured PHP session storage mechanism in the Yandex Managed Service for Valkey™ cluster works well.

  4. Repeat the query to view the keys stored in Valkey™:

    KEYS *
    
    1) "PHPREDIS_SESSION:keb02haicgi0ijeju3********"
    2) "PHPREDIS_SESSION:c5r0mbe1v84pn2b5kj********"
    

    The returned result shows that, for each session in Valkey™, its own key is created.

Delete the resources you createdDelete the resources you created

Delete the resources you no longer need to avoid paying for them:

Manually
Terraform
  • Delete the Yandex Managed Service for Valkey™ cluster.
  • Delete the virtual machine.
  • If you reserved public static IP addresses, release and delete them.
  1. In the terminal window, go to the directory containing the infrastructure plan.

    Warning

    Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

  2. Delete resources:

    1. Run this command:

      terraform destroy
      
    2. Confirm deleting the resources and wait for the operation to complete.

    All the resources described in the Terraform manifests will be deleted.

Was the article helpful?

Previous
All tutorials
Next
Migrating a database to Yandex Managed Service for Valkey™
© 2025 Direct Cursus Technology L.L.C.