Upgrading the cloud node image¶

These instructions describe the steps to update the cloud node image deployed on AWS, GCP up to 2.18.

Update procedure¶

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

Launch a new virtual machine based on the filtering node 2.18 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: Launch a new instance with the filtering node 2.18¶

Open the Wallarm filtering node image on the cloud platform marketplace and proceed to the image launch:
- Amazon Marketplace
- GCP Marketplace
At the launch step, set the following settings:
- Select the image version 2.18.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 2: 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:
- AWS documentation
- GCP documentation
Connect the filtering node to Wallarm Cloud using a new node token or username and password to Wallarm Console 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¶

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 2.18:
- /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
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 4: Test Wallarm node operation¶

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

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

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

Step 6: 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 management console.