Updating the cloud WAF node image¶
These instructions describe the steps to update the cloud WAF node image deployed on AWS, GCP, or Yandex.Cloud up to 2.18.
To update the version of the WAF node deployed in the cloud:
Launch a new virtual machine based on the WAF node 2.18 image.
Copy the WAF node settings from the previous version to the new version.
Delete the previous WAF node instance.
A more detailed description of the upgrade steps is provided below.
Step 1: Launch a new instance with the WAF node 2.18¶
Open the Wallarm WAF 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 2: Connect the WAF node to Wallarm Cloud¶
Connect to the WAF node instance via SSH. More detailed instructions for connecting to the instances are available in the cloud platform documentation:
Connect the WAF 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 3: Copy the WAF 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 WAF node version to the files of the WAF node 2.18:
/etc/nginx/nginx.confand other files with NGINX settings
/etc/nginx/conf.d/wallarm.confwith global WAF node settings
/etc/nginx/conf.d/wallarm-status.confwith the WAF node monitoring service settings
/etc/environmentwith environment variables
/etc/default/wallarm-tarantoolwith 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 WAF node directives is available here.
Step 4: Test WAF node operation¶
Step 5: Creating the virtual machine image based on the WAF node 2.18 in AWS or GCP¶
Step 6: Delete the previous WAF node instance¶
If the new version of the WAF node is successfully configured and tested, remove the instance and virtual machine image with the previous version of the WAF node using the AWS, GCP, or Yandex.Cloud management console.