Wallarm API Security Wallarm updates logo

Wallarm updates

Discover the latest features, improvements, and updates in Wallarm API Security

Subscribe to Updates

Labels

  • All Posts
  • API Security
  • WAAP
  • ANNOUNCEMENT
  • IMPROVEMENT
  • FIX
  • FAST

Jump to Month

  • April 2025
  • March 2025
  • February 2025
  • January 2025
  • November 2024
  • October 2024
  • September 2024
  • August 2024
  • July 2024
  • June 2024
  • May 2024
  • April 2024
  • March 2024
  • February 2024
  • January 2024
  • December 2023
  • November 2023
  • October 2023
  • September 2023
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • March 2022
  • February 2022
  • December 2021
  • November 2021
  • October 2021
  • August 2021
  • April 2021
  • March 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • December 2019
  • October 2019
  • August 2019
  • April 2019
ANNOUNCEMENT
5 years ago

Auto-scaling of nodes in AWS, GCP, Azure

Good news! Wallarm Nodes now natively support auto-scaling capabilities in AWS and GCP. Updated images are already available in cloud provider marketplaces.

Many of our customers rely on the auto-scaling capabilities to horizontally scale their apps and APIs. Auto-scaling mechanisms monitor your applications and automatically adjusts capacity to maintain steady, predictable performance at the lowest possible cost.

In the earlier releases, it was already possible to automatically scale Wallarm Nodes based on the load, for example, with native support of Kubernetes. From now on, you can also dynamically add additional nodes or remove underutilized ones using the native auto-scaling mechanism of AWS and GCP.

You can scale the number of instances based on a number of standard load parameters including: the utilization of CPU, amount of inbound/outbound traffic, etc. For example, for a group of Wallarm Node instances in AWS, you can set up the following policy: If Average CPU Utilization exceeds 60% for over 5 min then add 2 more nodes.

Support of auto-scaling is available in Wallarm Node 2.12.0+. Find the images in Amazon Web Services and Google Cloud Platform.

Detailed tutorials on how to set up auto-scaling are available in the Wallarm Docs for AWS and GCP.

Avatar of authorWallarm team
ANNOUNCEMENT
6 years ago

Action status for every malicious request

Wallarm nodes can operate in detection only (aka monitoring) or blocking modes. With a recent change in UI, every malicious request from the traffic is displayed with an explicit status detailing whether it was blocked or reached the application. Designed to be especially helpful for teams using individual modes for different applications and APIs.

With previous console versions, teams had to pay attention to each status code returned to the client. A 403 was the default status code if an incoming request was blocked by Wallarm node. Now, an explicit status of whether a malicious request was blocked is shown in the console. The same data is provided for attacks (groups of malicious request related to each other).

Avatar of authorWallarm team