Add Bot Manager Lite to a Firewall
Deploy the Bot Manager Lite Integration Kit template to add a function instance and a Rules Engine rule to a firewall you already have.
You add Bot Manager Lite to a firewall you already run by deploying the Bot Manager Lite Integration Kit template from Azion Console.
The template creates one Bot Manager Lite function instance on the firewall you name, and one Rules Engine rule that runs it. It adds to a firewall rather than creating one, so the deployment asks for the firewall’s ID.
To create the instance and the rule yourself instead, refer to Bot Manager quickstart.
Prerequisites
- A firewall in your account, and its ID. For more information, refer to Set a firewall’s main settings.
- The Functions module turned on for that firewall.
- Bot Manager Lite installed from Marketplace. For more information, refer to Install Bot Manager Lite.
- Access to Azion Console. To sign in, refer to How to access Azion Console.
- The instance runs as a Functions instance, which can generate usage costs. For the metrics Bot Manager is billed on, refer to Pricing.
The template checks the first three requirements before it creates anything. When one of them is not met, the deployment fails and writes a log line naming the reason.
Deploy the template
To deploy the template in Azion Console:
Access Azion Console > Firewalls, select the firewall, and copy the ID from the address. The address ends in /firewalls/edit/<firewall-id>.
Go to the Bot Manager Lite Integration Kit template.
In Firewall ID, enter the ID you copied. A field marked with an asterisk is mandatory.
When the deployment finishes, the firewall carries the new function instance and the rule that runs it.
What the template configures
The function instance is listed under the firewall’s Functions Instances tab, and the rule that runs it under its Rules Engine tab. The instance carries three arguments:
| Argument | Value | What it does |
|---|---|---|
threshold | 10 | The score at which action fires. The function ships a default of 30, so the template acts on more requests than an instance that sets nothing |
action | allow | The instance scores every request and refuses none. The seven values action takes are listed in Arguments |
internal_logs | 2 | Every request produces a report log line, whatever it scored. The four values are listed in Bot Manager Lite |
Nothing validates that object. Every key an instance carries is stored and read back exactly as it was sent, including a key the function never reads. Write thresold in place of threshold and the instance keeps thresold, the function keeps scoring against 30, and no interface reports a problem.
Edit the arguments in the instance’s Arguments section. The installed function publishes no argument schema, so the editor has no form to build from one and the object is written as raw JSON. For every argument an instance accepts, refer to Arguments.
Read what the instance scored
With internal_logs set to 2, the instance writes one report log line for every request it scores, including a request that scored 0. Read those lines in Real-Time Events, or forward them to a destination you own with Data Stream. For the fields a line carries, refer to Logs.
Because action is allow, the instance refuses nothing while you read them. Set threshold and action from the scores your own traffic produces, rather than from the values the template starts at. For more information, refer to Monitor and calibrate Bot Manager.