Skip to content

Upgrading the cloud node image 2.18 or lower

These instructions describe the steps to upgrade the cloud node image 2.18 or lower deployed on AWS or GCP up to 3.6.

Wallarm nodes 2.18 and lower have been deprecated

You are recommended to upgrade the Wallarm nodes 2.18 and lower since these versions are fully deprecated.

Node configuration and traffic filtration have been significantly simplified in the Wallarm node of version 3.6. Before upgrading the modules, please carefully review the list of changes and general recommendations. Please note that some settings of node 3.6 are incompatible with the nodes 2.18 and lower.

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

Please inform Wallarm technical support that you are upgrading filtering node modules up to 3.6 and ask to enable new IP list logic for your Wallarm account. When new IP list logic is enabled, please ensure the section IP lists of Wallarm Console is available.

Step 2: Disable the Active threat verification module (if upgrading node 2.16 or lower)

If upgrading Wallarm node 2.16 or lower, please disable the Active threat verification module in Wallarm Console → Scanner → Settings.

The module operation can cause false positives during the upgrade process. Disabling the module minimizes this risk.

Step 3: Launch a new instance with the filtering node 3.6

  1. Open the Wallarm filtering node image on the cloud platform marketplace and proceed to the image launch:

  2. At the launch step, set the following settings:

    • Select the image version 3.6.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
  3. Confirm the instance launch.

  4. For GCP, configure the instance following these instructions.

Step 4: Adjust Wallarm node filtration mode settings to changes released in the latest versions

  1. Ensure that the expected behavior of settings listed below corresponds to the changed logic of the off and monitoring filtration modes:

  2. 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 5: Connect the filtering node to Wallarm Cloud

  1. Connect to the filtering node instance via SSH. More detailed instructions for connecting to the instances are available in the cloud platform documentation:

  2. 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:

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

  1. 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.6:

    • /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
  2. Rename the following NGINX directives if they are explicitly specified in configuration files:

    We only changed the names of the directives, their logic remains the same. Directives with former names will be deprecated soon, so you are recommended to rename them before.

  3. Migrate whitelist and blacklist configuration from previous Wallarm node version to 3.6.

  4. If the page &/usr/share/nginx/html/wallarm_blocked.html is returned to blocked requests, copy and customize its new version.

    In the new node version, the Wallarm sample blocking page has been changed. The logo and support email on the page are now empty by default.

  5. 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 7: Test Wallarm node operation

  1. 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>'
    
  2. Open the Wallarm Console → Events section in the EU Cloud or US Cloud and ensure attacks are displayed in the list.

    Attacks in the interface

Step 8: Create the virtual machine image based on the filtering node 3.6 in AWS or GCP

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

Step 9: 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 or GCP management console.

Step 10: Re-enable the Active threat verification module (if upgrading node 2.16 or lower)

Learn the recommendation on the Active threat verification module setup and re-enable it if required.

After a while, ensure the module operation does not cause false positives. If discovering false positives, please contact the Wallarm technical support.

Back to top