Updating the cloud node image¶
These instructions describe the steps to update the cloud node image deployed on AWS, GCP, or Yandex.Cloud up to 3.2.
Breaking changes and recommendations for different node type update
- The Wallarm node 3.x is totally incompatible with Wallarm node of version 2.18 and lower. Before updating the modules up to 3.2, please carefully review the list of Wallarm node changes and consider a possible configuration change.
- We recommend to update both the regular (client) and partner nodes of version 3.0 or lower up to version 3.2. This release enables IP greylists and other new features and stabilizes Wallarm node operation.
To update the version of the filtering node deployed in the cloud:
If updating Wallarm node 2.18 or lower, inform Wallarm technical support that you are updating Wallarm node modules up to 3.2.
Adjust Wallarm node filtration mode settings to changes released in version 3.2.
Launch a new virtual machine based on the filtering node 3.2 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 updating filtering node modules¶
If updating Wallarm node 2.18 or lower, please inform Wallarm technical support that you are updating filtering node modules up to 3.2 and ask to enable new IP lists logic for your Wallarm account. When new IP lists logic is enabled, please open the Wallarm Console and ensure that the section IP lists is available.
Step 2: Adjust Wallarm node filtration mode settings to changes released in version 3.2¶
Ensure that the expected behavior of settings listed below corresponds to the changed logic of the
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 3: Launch a new instance with the filtering node 3.2¶
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:
Confirm the instance launch.
For GCP, configure the instance following these 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 the Wallarm Console as described in the instructions for the cloud platform:
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.2:
/etc/nginx/nginx.confand other files with NGINX settings
/etc/nginx/conf.d/wallarm.confwith global filtering node settings
/etc/nginx/conf.d/wallarm-status.confwith the filtering node monitoring service settings
/etc/environmentwith environment variables
/etc/default/wallarm-tarantoolwith Tarantool settings
- other files with custom settings for processing and proxying requests
If updating Wallarm node 2.18 or lower, migrate whitelist and blacklist configuration from previous Wallarm node version to 3.2 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¶
Step 7: Creating the virtual machine image based on the filtering node 3.2 in 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.