Skip to content

Akamai EdgeWorkers with Wallarm Code Bundle

Akamai EdgeWorkers is a powerful edge computing platform that allows for the execution of custom logic and the deployment of lightweight JavaScript functions at the edge of the platform. For customers who have their APIs and traffic running on Akamai EdgeWorkers, Wallarm provides a code bundle that can be deployed on Akamai EdgeWorkers to secure their infrastructure.

The solution involves deploying the Wallarm node externally and injecting custom code or policies into the specific platform. This enables traffic to be directed to the external Wallarm node for analysis and protection against potential threats. Referred to as Wallarm's connectors, they serve as the essential link between platforms like Azion Edge, Akamai Edge, Mulesoft, Apigee, and AWS Lambda, and the external Wallarm node. This approach ensures seamless integration, secure traffic analysis, risk mitigation, and overall platform security.

Use cases

Among all supported Wallarm deployment options, this solution is the recommended one for the following use cases:

  • Securing APIs or traffic running on Akamai EdgeWorkers.

  • Requiring a security solution that offers comprehensive attack observation, reporting, and instant blocking of malicious requests.


The solution has certain limitations as it only works with incoming requests:

  • Vulnerability discovery using the passive detection method does not function properly. The solution determines if an API is vulnerable or not based on server responses to malicious requests that are typical for the vulnerabilities it tests.

  • The Wallarm API Discovery cannot explore API inventory based on your traffic, as the solution relies on response analysis.

  • The protection against forced browsing is not available since it requires response code analysis.

There are also limitations caused by EdgeWorkers product limitations and http-request:

  • The only supported traffic delivery method is enhanced TLS.

  • Maximum response header size is 8000 bytes.

  • Maximum body size is 1 MB.

  • Unsupported HTTP methods: CONNECT, TRACE, OPTIONS (supported methods: GET, POST, HEAD, PUT, PATCH, DELETE).

  • Unsupported headers: connection, keep-alive, proxy-authenticate, proxy-authorization, te, trailers, transfer-encoding, host, content-length, vary, accept-encoding, content-encoding, upgrade.


To proceed with the deployment, ensure that you meet the following requirements:

  • Understanding of Akamai EdgeWorkers technologies

  • APIs or traffic running through Akamai EdgeWorkers.


To secure APIs on Akamai EdgeWorkers with Wallarm, follow these steps:

  1. Deploy a Wallarm node using one of the available deployment options.

  2. Obtain the Wallarm code bundle and run it on Akamai EdgeWorkers.

1. Deploy a Wallarm node

When utilizing Wallarm on Akami EdgeWorkers, the traffic flow is in-line.

  1. Choose one of the supported Wallarm node deployment solutions or artifacts for in-line deployment and follow the provided deployment instructions.

  2. Configure the deployed node using the following template:

    server {
        listen 80;
        server_name _;
        access_log off;
        wallarm_mode off;
        location / {
            proxy_set_header Host $http_x_forwarded_host;
            proxy_pass http://unix:/tmp/wallarm-nginx.sock;
    server {
        listen 443 ssl;
        server_name yourdomain-for-wallarm-node.tld;
        ### SSL configuration here
        access_log off;
        wallarm_mode off;
        location / {
            proxy_set_header Host $http_x_forwarded_host;
            proxy_pass http://unix:/tmp/wallarm-nginx.sock;
    server {
        listen unix:/tmp/wallarm-nginx.sock;
        server_name _;
        wallarm_mode monitoring;
        #wallarm_mode block;
        real_ip_header X-EDGEWRK-REAL-IP;
        set_real_ip_from unix:;
        location / {

    Please ensure to pay attention to the following configurations:

    • TLS/SSL certificates for HTTPS traffic: To enable the Wallarm node to handle secure HTTPS traffic, configure the TLS/SSL certificates accordingly. The specific configuration will depend on the chosen deployment method. For example, if you are using NGINX, you can refer to its article for guidance.
    • Wallarm operation mode configuration.
  3. Once the deployment is complete, make a note of the node instance IP as you will need it later to set the address for incoming request forwarding.

2. Obtain the Wallarm code bundle and run it on Akamai EdgeWorkers

To acquire and run the Wallarm code bundle on Akamai EdgeWorkers, follow these steps:

  1. Contact to obtain the Wallarm code bundle.

  2. Add EdgeWorkers to your contract on Akamai.

  3. Create an EdgeWorker ID.

  4. Open the created ID, press Create Version and upload the Wallarm code bundle.

  5. Activate the created version, initially in the staging environment.

  6. After confirming everything is working correctly, repeat the version publication in the production environment.

  7. In Akamai Property Manager, choose or create a new property where you want install Wallarm.

  8. Create new behavior with newly created EdgeWorker, call it for example Wallarm Edge and add the following criteria:

    Request Header 
    does not exist
  9. Create another behavior Wallarm Node with Origin Server pointing to previously deployed node. Switch Forward Host Header to Origin Hostname and add the following criteria:

    Request Header 
  10. Add new property variable PMUSER_WALLARM_MODE with value monitoring (default) or block.

    Choose Hidden for Security settings.

  11. Save the new version and deploy it initially to the staging environment, and then to production.


To test the functionality of the deployed policy, follow these steps:

  1. Send the request with the test Path Traversal attack to your API:

    curl http://<YOUR_APP_IP_OR_DOMAIN>/etc/passwd
  2. Open Wallarm Console → Attacks section in the US Cloud or EU Cloud and make sure the attack is displayed in the list.

    Attacks in the interface

    If the Wallarm node mode is set to blocking, the request will also be blocked.

Need assistance?

If you encounter any issues or require assistance with the described deployment of Wallarm in conjunction with Akamai EdgeWorkers, you can reach out to the Wallarm support team. They are available to provide guidance and help resolve any problems you may face during the implementation process.