--- name: azion-test-bot-manager-lite-with-the-starter-kit description: >- Deploy the Bot Manager Lite Starter Kit template to get a sandbox that scores the requests you send from its test page. --- # Test Bot Manager Lite with the Starter Kit You see [Bot Manager Lite](/en/documentation/platform/firewall/bot-manager/bot-manager-lite/) score a request you send yourself by deploying the Bot Manager Lite Starter Kit template from Azion Console. The template deploys a sandbox: an application, a function that serves a test page, a [firewall](/en/documentation/platform/firewall/) carrying a Bot Manager Lite function instance, and a domain that reaches them from a browser. It creates the firewall itself, so the deployment asks for no object you already run. To add Bot Manager Lite to a firewall you already run, refer to [Add Bot Manager Lite to a Firewall](/en/documentation/guides/application-development/integrations/bot-manager-lite-integration-kit/). --- ## Prerequisites - Bot Manager Lite installed from Marketplace. For more information, refer to [Install Bot Manager Lite](/en/documentation/guides/application-development/integrations/bot-manager-lite/). - Access to Azion Console. To sign in, refer to [How to access Azion Console](/en/documentation/guides/platform/account-and-billing/how-to-access-azion-console/). - The instance runs as a [Functions](/en/documentation/platform/functions/) instance, which can generate usage costs. For the metrics Bot Manager is billed on, refer to [Pricing](/en/documentation/fundamentals/pricing/#bot-manager). The template checks that Bot Manager Lite is installed before it creates anything. When it is not, the deployment fails and writes a log line naming the reason. --- ## Deploy the template To deploy the template in Azion Console: 1. **Open the template** Go to the [Bot Manager Lite Starter Kit](https://console.azion.com/create/azion/bot-manager-starter-kit) template. 2. **Name the application** In **Applications Name**, enter a name. The template gives the same name to the firewall instance it creates. A field marked with an asterisk is mandatory. 3. **Name the sample function** In **Sample Function Name**, enter a name for the function that serves the test page. 4. **Select Deploy** The deployment shows its log as it runs. When it finishes, the account carries the application, the function, the firewall, and the domain. The domain takes a few minutes to propagate across Azion's distributed infrastructure. Until it answers, the test page does not open in a browser. --- ## What the template configures The template creates four objects: - An application with the **Functions** module turned on, which runs the sample function. - A function that serves the test page and its request buttons. - A firewall carrying a Bot Manager Lite function instance and a [Rules Engine](/en/documentation/platform/firewall/rules-engine/) rule that runs it. - A [workload](/en/documentation/platform/workloads/), which answers on a domain in the format `.map.azionedge.net`. The instance is listed under the firewall's **Functions Instances** tab, and the rule that runs it under the **Rules Engine** tab. The instance carries `action` set to `deny`, so a request that scores at or above the threshold receives a `403` response carrying Azion's default error page. It also writes a report log line for every request it scores, which is what `internal_logs` controls. Read and change that object 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. Nothing validates it either: every key an instance carries is stored and read back exactly as it was sent, including a key the function never reads. For every argument an instance accepts, refer to [Arguments](/en/documentation/platform/firewall/bot-manager/arguments/). The application serves the sample function rather than an origin you own, so the configuration is a demonstration rather than a running site. To reach the sandbox on a domain you own, add that domain to the workload the template created. --- ## Send a good and a bad request To score a request you send yourself: 1. **Open the test page** In a browser, go to the domain the template created. 2. **Send a good request** Select **Send Request** for the good request. The page renders a success message. 3. **Send a bad request** Select **Send Request** for the bad request. The page renders the `403` response the `deny` action returns. Each request the page sends produces one report log line, whatever it scored. To send a refused request to a location you choose instead of the default error page, set `action` to `redirect` and give `redirect_to` the destination. For more information, refer to [Arguments](/en/documentation/platform/firewall/bot-manager/arguments/#action). --- ## Read what the instance scored Read the report log lines in [Real-Time Events](/en/documentation/platform/real-time-events/), or forward them to a destination you own with [Data Stream](/en/documentation/platform/data-stream/). For the fields a line carries, refer to [Logs](/en/documentation/platform/firewall/bot-manager/logs/). The scores the test page produces come from requests the sandbox shaped, not from traffic of your own. Set `threshold` and `action` from the scores your own traffic produces before an instance refuses anything in front of an application you run. For more information, refer to [Monitor and calibrate Bot Manager](/en/documentation/guides/application-security/bots-and-network/monitor-and-calibrate-bot-manager/#read-the-report-log-in-real-time-events). --- ## Next steps - [Bot Manager quickstart](/en/documentation/platform/firewall/bot-manager/quickstart.md): Create the instance and the rule yourself, from Azion Console, the Azion CLI, or the API. - [Add Bot Manager Lite to a Firewall](/en/documentation/guides/application-development/integrations/bot-manager-lite-integration-kit.md): Deploy the same instance and rule onto a firewall you already run. - [Arguments](/en/documentation/platform/firewall/bot-manager/arguments.md): Every argument a function instance accepts, with its type, its default, and the values it takes. - [Firewall best practices](/en/documentation/platform/firewall/best-practices.md#bot-manager): Set the threshold from your own score distribution before the instance refuses anything.