To deploy an Amazon Machine Image with Wallarm Node:
- Log in to you Amazon Web Services account.
- Launch a Wallarm Node instance.
- SSH to the Wallarm Node instance.
- Install a Wallarm license key.
- Connect the Wallarm Node to Wallarm Cloud.
- Set up filtering and proxying rules.
Log in at aws.amazon.com.
Launch your Wallarm Node instance. See Amazon Elastic Compute Cloud: Launching an Instance.
The instance launches with a pre-installed Wallarm Node.
Wallarm sends the license key to the email address provided when signing up at https://my.wallarm.com/.
- Copy the license key to the file
- Set the access rights to the key:
chmod 0640 /etc/wallarm/license.key
chown root:wallarm /etc/wallarm/license.key
The filter node interacts with the Wallarm cloud located on a remote server.
addnode script connects the filter node to the Wallarm cloud.
Run the script
Enter the login and password. This is the same login and password that you use to access Wallarm console at https://my.wallarm.com. The profile must have the Administrator role and 2FA should be disabled. If the profile has the Analyst role or has 2FA enabled, the script will error out.
To interact with the Wallarm cloud, the filter node must have access to https://api.wallarm.com:444.
Ensure the access is not blocked by a firewall.
wallarm_mode string in the file
To uncomment, remove the
# character at the beginning of the string.
By default, the directive is set to
Set it to
File contents example:
# # Wallarm module specific parameters # wallarm_mode monitoring; # wallarm_mode_allow_override on;
Wallarm Node uses the in-memory storage Tarantool.
By default, the amount of RAM allocated to Tarantool is 75% of the total instance memory.
You can change the amount of RAM allocated for Tarantool
To allocate the instance RAM to Tarantool:
Open the Tarantool configuration file:
Set the amount of allocated RAM in the
SLAB_ALLOC_ARENAin GB. For example, to set 24 GB:
To apply changes, restart the Tarantool daemon:
systemctl restart wallarm-tarantool
Check that the filter node runs and filters the traffic. See Check the filter node operation.