コンテンツにスキップ

Self-Hosted Deployment Options

In a self-hosted deployment, you are responsible for installing and operating the Wallarm Node within your infrastructure - on Kubernetes clusters, virtual machines, or cloud environments. This gives you full control over configuration, networking, and scaling.

Wallarm supports many deployment options enabling you to seamlessly integrate the platform with your environment. Learn the options and choose the most appropriate one from this document.

Kubernetes

Public clouds

Amazon Web Services

Artifacts for Wallarm deployment on AWS

Google Cloud

Artifacts for Wallarm deployment on GCP

Microsoft Azure

Artifacts for Wallarm deployment on Microsoft Azure

Alibaba Cloud

Artifacts for Wallarm deployment on Alibaba Cloud

Heroku

Build a Wallarm Docker image and run it on Heroku

Amazon Web Services

Artifacts for Wallarm deployment on AWS

AMI

Use the official Amazon Machine Image to deploy Wallarm

ECS

Use the Docker image to deploy Wallarm with Elastic Container Service

Terraform module

Use the Terraform module for Wallarm deployment

Microsoft Azure

Artifacts for Wallarm deployment on Microsoft Azure

Azure Container Instances

Use the Docker image to deploy Wallarm with Azure Container Instances

Alibaba Cloud

Artifacts for Wallarm deployment on Alibaba Cloud

ECS

Use the Docker image to deploy Wallarm with Elastic Compute Service

API gateways

Choose an API gateway connector if traffic already flows through a gateway and you want to add protection alongside it.

CDN

Choose a CDN or edge integration if your traffic is fronted by a CDN and you want protection at the edge.

API management platform

Choose an API management connector if you expose APIs through one of these platforms and want to add security without changing it.

Packages & containers

Choose packages or containers if you run on VMs or bare metal and prefer them over managed options.

On-premise

Special setups

Deployment options that don't follow the platform matrix: known scenarios (multi-tenant, separate postanalytics, custom NGINX) and custom requests when nothing above fits.