Prerequisites — Aurva Docs

Before deploying Aurva, ensure the following are in place.

Infrastructure

Aurva supports deployment on all major cloud providers (AWS, GCP, Azure) and on-premise systems. The Aurva Data Plane can be deployed on managed Kubernetes services (EKS, GKE, AKS), self-managed Kubernetes clusters, or traditional virtual machine instances. Ensure you have the necessary permissions for your deployment platform before proceeding.

For Managed Kubernetes (EKS, GKE, AKS):

Cloud provider account with appropriate permissions (IAM roles for AWS, service accounts for GCP/Azure)
kubectl configured and pointing at your target cluster
Helm 3.x installed

For Self-Managed Kubernetes or On-Premise:

Access to a Kubernetes cluster with appropriate permissions
kubectl configured and pointing at your target cluster
Helm 3.x installed

For VM-Based Deployments (EC2, Compute Engine, VMs):

Compute instance permissions for your cloud provider or on-premise infrastructure
Docker installed

Data Sources

Connector credentials (database username/password, S3 bucket policy, etc.) for each data source you want to connect
Network connectivity between the Data Plane and your data sources (VPC peering, security group rules, or RDS public accessibility)

Notifications

At least one Alert Route configured before creating policies — Aurva needs somewhere to send alerts
Slack webhook URL, Jira project + API token, or SMTP credentials depending on your chosen route

Access

Aurva admin credentials provided during onboarding
IAM role or service account with read access to your data sources (Aurva does not require write access for discovery)

Start with a non-production environment. Deploy Data Plane, connect one data source, run a scan, and validate the results before rolling out to production data assets.