Quick Start
Get up and running with Aurva in under 30 minutes.
This guide gets a new Aurva tenant from zero to first insight in under 30 minutes. It assumes you already have Aurva account credentials and admin rights to one cloud account.
1. Sign in
Log into the Aurva console at your tenant URL (e.g., https://app.aurva.io or your private instance). On first login you will land on the Overview Dashboard, which will be empty until you onboard an environment.
2. Connect a Data Plane
Aurva needs a Data Plane running inside the environment you want to protect. Pick the path that matches your infrastructure:
- AWS EKS — Data Plane on AWS EKS
- AWS EC2 (VMs) — Data Plane on AWS VMs (Terraform)
- GCP GKE — Data Plane on GCP GKE
- On-Premises — Data Plane on On-Premises Servers
The Data Plane will auto-register with the Control Plane within a few minutes of becoming healthy.
3. Onboard a data asset
Once a Data Plane is online, add your first data asset so Aurva can discover and classify its contents. Follow Onboarding a Data Asset Manually.
After onboarding, scan jobs run automatically. Initial classification typically completes within 30–60 minutes for small assets.
4. Enable Database Activity Monitoring
To capture queries against the new asset, configure DAM. See Monitoring Configuration. For self-hosted databases, install the eBPF agent or AIDA. For RDS, use AWS RDS DAM.
5. Create your first policy
With activity flowing in, set up a baseline policy. The fastest path is a Detect & Alert policy that flags anomalous behaviour without blocking traffic. Follow Creating a Custom Policy.
6. Verify and iterate
Return to the Overview Dashboard. You should now see:
- Discovered assets and their classification breakdown
- Live query activity in the DAM widgets
- Open risks (if any)
- Initial compliance scoring
From here, expand to additional assets, refine policies, and route alerts to Slack or Jira via the Alert Routes configuration.