Email & S3

Configure email notifications and Amazon S3 archival for Aurva alerts and audit data.

Aurva supports email and Amazon S3 as alert destinations. Use email for human-readable notifications and S3 for long-term, machine-readable archival.

Email

Navigate to Settings -> Integrations -> Email and provide:

Field	Description
SMTP Host	Mail server hostname (e.g. `smtp.example.com`)
Port	Typically `587` (STARTTLS) or `465` (SSL)
Username	SMTP authentication username
Password	SMTP authentication password
From Address	Sender address shown on notifications
To Addresses	One or more recipient addresses

Mode	Behaviour
Immediate	One email per alert, sent as soon as the policy fires
Digest	Aggregated summary email on a schedule (hourly or daily)

Digest mode is recommended for medium- and low-severity alerts to avoid inbox overload. Configure the mode per Alert Route.

Each email includes:

1
Create an S3 bucket
Create a bucket in the same AWS region as your Aurva deployment (e.g. aurva-alerts-archive).
2
Configure IAM permissions
Grant Aurva's IAM role s3:PutObject and s3:PutObjectAcl on the bucket. See AWS IAM Permissions for details.
3
Add S3 in Aurva
Navigate to Settings -> Integrations -> S3 and provide the bucket name and optional path prefix.
4
Assign to an Alert Route
Add S3 as a destination on one or more Alert Routes.

Format	Best For
JSON	Easy parsing, integration with downstream pipelines
Parquet	Efficient columnar storage, ideal for Athena/BigQuery queries

Select the format in the S3 integration settings. Files are partitioned by date (year=YYYY/month=MM/day=DD/).

Configure S3 lifecycle rules to manage storage costs:

Transition to S3 Glacier after 90 days
Delete after the retention period required by your compliance framework (typically 1--7 years for BFSI)