Upgrading the cloud node image¶

These instructions describe the steps to upgrade the cloud node image deployed on AWS, GCP, or Yandex.Cloud up to 3.4.

Breaking changes and recommendations for different node type upgrade

If upgrading Wallarm node 2.18 or lower, please note that version 3.x contains breaking changes. Before upgrading the modules of 2.18 and lower up to 3.4, please carefully review the list of Wallarm node changes and consider a possible configuration change.
We recommend to upgrade both the regular (client) and partner nodes of version 3.2 or lower up to version 3.4. It allows to stay up to date with Wallarm releases and prevent installed module deprecation.

Upgrade procedure¶

To upgrade the version of the filtering node deployed in the cloud:

If upgrading Wallarm node 2.18 or lower, inform Wallarm technical support that you are upgrading Wallarm node modules up to 3.4.
If upgrading Wallarm node 3.0 or lower, adjust Wallarm node filtration mode settings to changes released in newer versions.
Launch a new virtual machine based on the filtering node 3.4 image.
Copy the filtering node settings from the previous version to the new version.
Delete the previous Wallarm node instance.

A more detailed description of the upgrade steps is provided below.

Step 1: Inform Wallarm technical support that you are upgrading filtering node modules¶

If upgrading Wallarm node 2.18 or lower, please inform Wallarm technical support that you are upgrading filtering node modules up to 3.4 and ask to enable new IP lists logic for your Wallarm account. When new IP lists logic is enabled, please open Wallarm Console and ensure that the section IP lists is available.

Step 2: Launch a new instance with the filtering node 3.4¶

Open the Wallarm filtering node image on the cloud platform marketplace and proceed to the image launch:
At the launch step, set the following settings:
- Select the image version 3.4.x
- For AWS, select the created security group in the field Security Group Settings
- For AWS, select the name of the created key pair in the field Key Pair Settings
Confirm the instance launch.
For GCP, configure the instance following these instructions.

Step 3: Adjust Wallarm node filtration mode settings to changes released in version 3.2¶

If upgrading Wallarm node 3.0 or lower:

Ensure that the expected behavior of settings listed below corresponds to the changed logic of the off and monitoring filtration modes:
If the expected behavior does not correspond to the changed filtration mode logic, please adjust the filtration mode settings to released changes using the instructions.

Step 4: Connect the filtering node to Wallarm Cloud¶

Connect to the filtering node instance via SSH. More detailed instructions for connecting to the instances are available in the cloud platform documentation:
Connect the filtering node to Wallarm Cloud using a new cloud node token or username and password to Wallarm Console as described in the instructions for the cloud platform:
- AWS
- GCP
- Yandex.Cloud

Step 5: Copy the filtering node settings from the previous version to the new version¶

Copy the settings for processing and proxying requests from the following configuration files of the previous Wallarm node version to the files of the filtering node 3.4:
- /etc/nginx/nginx.conf and other files with NGINX settings
- /etc/nginx/conf.d/wallarm.conf with global filtering node settings
- /etc/nginx/conf.d/wallarm-status.conf with the filtering node monitoring service settings
- /etc/environment with environment variables
- /etc/default/wallarm-tarantool with Tarantool settings
- other files with custom settings for processing and proxying requests
If upgrading Wallarm node 2.18 or lower, migrate whitelist and blacklist configuration from previous Wallarm node version to 3.4 following the instructions.
Restart NGINX to apply the settings:
```
sudo systemctl restart nginx
```

Detailed information about working with NGINX configuration files is available in the official NGINX documentation.

The list of filtering node directives is available here.

Step 6: Test Wallarm node operation¶

Send the request with test SQLI and XSS attacks to the application address:
```
curl http://localhost/?id='or+1=1--a-<script>prompt(1)</script>'
```
Open the Wallarm Console → Events section in the EU Cloud or US Cloud and ensure attacks are displayed in the list.

Step 7: Creating the virtual machine image based on the filtering node 3.4 in AWS or GCP¶

To create the virtual machine image based on the filtering node 3.4, please follow the instructions for AWS or GCP.

Step 8: Delete the previous Wallarm node instance¶

If the new version of the filtering node is successfully configured and tested, remove the instance and virtual machine image with the previous version of the filtering node using the AWS, GCP, or Yandex.Cloud management console.