Upgrading the cloud node image¶

These instructions describe the steps to upgrade the cloud node image 4.x deployed on AWS or GCP up to 4.6.

To upgrade the end‑of‑life node (3.6 or lower), please use the different instructions.

Requirements¶

• Access to the account with the Administrator role in Wallarm Console in the US Cloud or EU Cloud

• Access to https://us1.api.wallarm.com if working with US Wallarm Cloud or to https://api.wallarm.com if working with EU Wallarm Cloud. Please ensure the access is not blocked by a firewall

Step 1: Launch a new instance with the filtering node 4.6¶

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

   • Amazon Marketplace
   • GCP Marketplace

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

   • Select the image version 4.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 2: 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:

   • AWS documentation
   • GCP documentation

2. Create a new Wallarm node and connect it to the Wallarm Cloud using the generated token as described in the instructions for the cloud platform:

   • AWS
   • GCP

Step 3: 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 4.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. 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.

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 4: Restart NGINX¶

Restart NGINX to apply the settings:

sudo systemctl restart nginx

Step 5: Test Wallarm node operation¶

1. Send the request with test Path Traversal attack to a protected resource address:

   curl http://localhost/etc/passwd
   

2. Open Wallarm Console → Events section in the US Cloud or EU Cloud and make sure the attack is displayed in the list.
   

   

Step 6: Create the virtual machine image based on the filtering node 4.6 in AWS or GCP¶

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

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