Aurva

Prerequisites

Requirements before deploying and configuring Aurva.

Before deploying Aurva, ensure the following are in place.

Infrastructure

Aurva requires either an Amazon EKS cluster or EC2 instances to deploy the Aurva Data Plane (Data Plane). Ensure you have the necessary AWS permissions before proceeding.

  • AWS account with permissions to create IAM roles, EKS node groups (or EC2 instances), and VPC security groups
  • kubectl configured and pointing at your target cluster (EKS deployments)
  • Helm 3.x installed (EKS deployments)
  • Docker installed (EC2 deployments)

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.