How to Backup Axis P3245-V HDTV 1080p Dome Camera to Wasabi Hot Cloud

High-performance enterprise dome with Lightfinder 2.0 and encrypted FTPS/SFTP. Follow our step-by-step setup guide below to stream footage directly into AWS S3, Cloudflare R2, or Backblaze B2 via FTP, FTPS, or SFTP with Rilavek as the pipe, zero on-prem NVR required.

Get Started Free10 GB/mo free ingest included

Jump to:Advantages Data Flow Setup Steps Comparison FAQ

Zero NVR Vulnerability

Your Axis P3245-V uploads footage offsite in real time. Intruders cannot steal or destroy evidence by seizing on-prem recorder hardware.

S3-Native Retention

Store Axis P3245-V recordings on your own terms. Apply automated bucket lifecycle rules to roll over or archive clips after 30, 90, or 365 days.

Direct Streaming Bridge

Rilavek ingests native FTP, FTPS, and SFTP streams from your Axis P3245-V and writes them directly into multipart S3 PUTs with zero disk writes.

Axis P3245-V HDTV 1080p Dome Camera

FTP/FTPS/SFTP

Rilavek Bridge

S3 API

Wasabi Hot Cloud

Step-by-Step Setup Guide for Axis P3245-V HDTV 1080p Dome Camera

Follow these 8 steps to select your cloud provider, provision your object storage, configure Rilavek’s Data Store, Sender, and Ingestion Pipe, enter your camera firmware settings, verify ingestion, and establish automated S3 retention rules.

Step 1Select Cloud Step 2Bucket & Keys Step 3Data Store Step 4Camera Sender Step 5Ingestion Pipe Step 6Camera Setup Step 7Verify Ingest Step 8 · OptionalLifecycle Policy

01

Select Your Cloud Storage Provider

Choose where you want to store your Axis surveillance footage. Selecting a provider customizes the bucket setup steps, endpoint URLs, and API key instructions in Step 2.

02

Set Up Your Wasabi Hot Cloud Bucket & Generate API Keys

Configure your target bucket and API credentials inside Wasabi Hot Cloud so Rilavek can stream motion clips and continuous video directly into your storage.

1

Create a Wasabi Hot Cloud Storage Bucket

Log into the Wasabi Console and select Create Bucket . Choose your preferred datacenter region and assign a unique bucket name.

2

Generate an API Access Key

Go to Access Keys in the left sidebar and click Create New Access Key . Create a sub-user key or standalone key with permissions restricted to your surveillance bucket.

3

Save API Credentials & Endpoint URL

Download the credentials file or copy your API Key and Secret Key. Wasabi regional endpoints use https://s3.<region>.wasabisys.com (for example, https://s3.us-east-1.wasabisys.com).

Official Wasabi Hot Cloud Documentation

Bucket Setup & Regions

Official guide for bucket provisioning, tiers, and privacy

API & Access Keys Guide

Generate and scope Access Key & Secret Key pairs

03

Add Your Data Store in Rilavek

In your Rilavek dashboard, navigate to Data Stores > New Data Store, select your provider, and enter your S3 credentials. Rilavek verifies the connection with an automated write-probe before saving.

Grant minimal S3 permissions only.Rilavek needs minimal, write-focused actions and nothing more.

Read our S3 Permissions Guide

Rilavek Dashboard · Data Stores > New S3 Data Store

Add New Data Store

S3 Compatible

Data Store Name *

Axis Surveillance Storage

Endpoint *

https://s3.<region>.wasabisys.com

Access Key ID *

AKIAIOSFODNN7EXAMPLE

Secret Access Key *

••••••••••••••••••••••••••••••••

Bucket Name *How to create →

cctv-axis-recordings

Region *

us-east-1

Automatically executes multipart write-probe test before saving.Save Data Store

Fig 1: Add New S3 Data Store configuration in the Rilavek console.

04

Create a Camera Sender in Rilavek

Go to Senders in the Rilavek sidebar and click New Sender. A Sender represents the hardware identity of your Axis P3245-V HDTV 1080p Dome Camera and generates a dedicated device-level password.

Rilavek Dashboard · Senders > Create New Sender Modal

Create New Sender

Display Name *

Axis P3245-V HDTV 1080p Dome Camera

Username *

cam_p3245v

Must be at least 6 characters, lowercase, start with a letter/underscore, and contain only letters, numbers, hyphens, or underscores.

Email (Optional)

security@axis-cctv.local

Secure credentials will be automatically generated for this sender.

CancelCreate Sender

Fig 2: Create New Sender modal assigning dedicated camera hardware identity.

Rilavek Dashboard · Senders > Generated Device Credentials

Sender Credentials

Make sure to copy your password now as you will not be able to see it again.

Username

cam_p3245v

PasswordSave for Step 6

••••••••••••

Done

Fig 3: Generated device-level username and one-time password for camera authentication.

05

Create & Configure Your Ingestion Pipe in Rilavek

Go to Pipes in the sidebar and click Create Pipe. Configure the 4 core sections of your pipeline: General (Pipe ID), Inputs (FTP), Access Control (Sender permission), and Destinations (Data Store).

1General Settings (Pipe ID)

Every pipeline in Rilavek is assigned an immutable, globally unique Pipe ID (e.g. p_cctv9x). This ID acts as an isolated ingestion channel that segregates audit logs, real-time transfer metrics, and storage routing. It also forms the second half of your scoped camera FTP login username (username@p_cctv9x).

Rilavek Dashboard · Pipes > Pipeline Settings > General

Pipe ID

p_cctv9x

Use this ID to identify this pipe in logs. Combine it with the sender username for complete authentication details.

Fig 4: General settings displaying the unique Pipe ID used for authentication.

2Inputs (FTP / FTPS Ingress)

The Inputs configuration defines how camera files enter Rilavek. Enabling the FTP Ingress input provides a persistent, high-availability ingestion server (ftp.rilavek.com) compatible with active and passive FTP modes, explicit TLS negotiation, and standard CCTV firmware video push routines.

Rilavek Dashboard · Pipes > Pipeline Settings > Inputs

Inputs

Enable inputs to receive data.

1 input enabled

FTP

SFTP

FTP Ingress

Endpoint enabled. Connect using your Sender credentials.

Host

ftp.rilavek.com

Port

21

Username

<sender>@p_cctv9x

Example: cam_p3245v@p_cctv9x

Password

••••••••••••

Use the password configured for the specific Sender.

Fig 5: Enabling the FTP Ingress endpoint for incoming surveillance video streams.

3Access Control (Sender Authorization)

Access Control prevents unauthorized uploads by enforcing a zero-trust boundary on the ingestion pipe. Only explicitly authorized Senders (such as Axis P3245-V HDTV 1080p Dome Camera) can authenticate and stream video into this pipe. Any requests with unassigned credentials are rejected at the network edge.

Rilavek Dashboard · Pipes > Pipeline Settings > Access Control

Access Control

Restricts who can upload to this pipe.

1 sender allowed

1Individuals

Groups

Individual Senders

Grant or revoke pipe access for specific individual senders.

Axis P3245-V HDTV 1080p Dome Camera

cam_p3245v@p_cctv9x

Fig 6: Restricting pipeline ingress access to your authorized camera Sender.

4Destinations (Target Cloud Storage Routing)

The Destinations section routes video clips to your target cloud storage provider. Linking your configured Data Store routes all received footage directly to your Wasabi Hot Cloud bucket (cctv-axis-recordings). Video files are committed on-the-fly via parallel multipart S3 PUTs without intermediate disk caching.

Rilavek Dashboard · Pipes > Pipeline Settings > Destinations

Destinations

This is where we send your files to.

1 destination added

Axis Storage (Wasabi Hot Cloud)

Primary

Target Bucketcctv-axis-recordingsProviderWasabi Hot CloudStatusActive (Ready for camera ingress)

Fig 7: Routing incoming camera footage directly into your S3-compatible cloud bucket.

Camera Connection Parameters (Enter in Step 6):Reference Values

Server Hostftp.rilavek.com

Port21

Usernamecam_p3245v@p_cctv9x

06

Configure FTP, Motion Detection & Linkage Method in Axis P3245-V HDTV 1080p Dome Camera Firmware

Open your camera's web configuration page in your browser at its local LAN IP address and complete the steps below:

Step 6AConfigure FTP Streaming Credentials

Click System > Events > Recipients.

Navigate to Events > Recipients and click 'Add...' to open the Recipient Setup dialog. Name the recipient 'Recipient_FTP', set Type to 'FTP', enter your Rilavek Ingestion Host, port 21, scoped username, and device password. Ensure 'Use passive mode' is checked as indicated below.

AXIS P3245-V Network Camera

Recipients

?

Recipients List

Name	Type	Address	Upload path	User name
Recipient_FTP	FTP	ftp.rilavek.com	/axis-p3245/	cam_p3245v@p_cctv9x

1 recipient configured

Recipient Setup

?

Name:

Type:

▼

Network address:

↳Rilavek Ingestion Gateway: Direct S3 gateway endpoint for your Wasabi Hot Cloud bucket.

Upload path:

Port number:

Login Credentials

User name:

↳Scoped Rilavek User: cam_p3245v@p_cctv9x (Sender@Pipe).

Password:

The FTP password associated with the camera license (Device password from Step 3)

Advanced Settings

Use passive mode

Use temporary mode

Test

Test the connection to the specified FTP server S3 Ingestion Gateway verified

Step 6BConfigure Action Rule Trigger (VMD 4 / Motion Analytics)

Click Events > Action Rules > Add.

Navigate to Events > Action Rules and click 'Add...'. Check 'Enable rule', name it 'FTP_Motion_Upload', and configure Condition > Trigger to 'Applications' with 'VMD 4: Any Profile' (Axis Video Motion Detection) so camera recording triggers on motion.

AXIS P3245-V Network Camera

Action Rules

?

Action Rule List

Name	Trigger	Schedule	Action	Recipient
SFTP-Upload	Time - Recurrence	Continuous-Uploading	Send Video Clip	SFTP: ftp.cameraftp.com

1 action rule configured

Action Rule Setup

?

General

Enable rule

Name:

Condition

Trigger:

▼

Start condition only

▼

Active:

Yes

No

↳Axis Motion Trigger: Uses VMD 4 (Video Motion Detection) application profile so recording triggers only on detected movement.

Schedule:

▼

Additional conditions

None

▲▼

Wait at leastbefore re-running the rule (max 23:59:59)

Step 6CLink Action Rule to FTP Recipient (Image & Video Upload)

Click Events > Action Rules > Actions.

Under Actions in the Action Rule Setup dialog, set Type to 'Send Images' (or 'Send Video Clip'), configure Stream profile and frequency, select 'Recipient_FTP' as Recipient, and check 'Add date/time suffix' for Base file name. Click OK to start streaming.

AXIS P3245-V Network Camera

Action Rule Setup

?

Actions

Type:

▼

Stream profile:

▼

Image frequency:

frame(s) per

▼

Duration:

Pre-trigger timesecond(s)

While the rule is active

Post-trigger timesecond(s)

Limit:

Send only the firstimages

Recipient:

▼

*Create folder:

*Base file name:

Add date/time suffix

Add sequence number suffix (no maximum value)

Add sequence number suffix up to 10 and then start over

Overwrite/Use own file format.

*See help for more information

↳Action Linkage: Streams motion events directly into your Wasabi Hot Cloud storage bucket with UTC timestamps.

07

Verify Ingestion

Click Test in your camera's FTP settings or trigger a test recording transfer. In your Rilavek dashboard, navigate to Pipes > your pipeline > Transfers tab to inspect incoming files as video clips stream into Wasabi Hot Cloud.

Rilavek Dashboard · Pipes > Transfers

Overview

Transfers

Refresh

FILE	SENDER	SIZE	DATE	STATE
axis/p3245-v/2026-09-10/ch01_143000.mp4	cam_p3245v	18.4 MB	Sep 10, 14:30	Success
axis/p3245-v/2026-09-10/ch01_142500.mp4	cam_p3245v	21.2 MB	Sep 10, 14:25	Success
axis/p3245-v/2026-09-10/ch01_142000.mp4	cam_p3245v	19.7 MB	Sep 10, 14:20	Success

Showing 3 of 3 transfers

Fig 8: Transfers log confirming incoming camera recordings streaming directly into cloud storage.

Direct S3 Ingest VerifiedIncoming surveillance streams are committed on-the-fly directly to your Wasabi Hot Cloud bucket with zero local buffering and no intermediate disk storage.

08

Configure Wasabi Hot Cloud Bucket Lifecycle & Retention Rules (Optional)

Optional: Prevent runaway storage costs by configuring automated bucket expiration rules. Select your retention window below and apply the generated JSON lifecycle policy or CLI command to your Wasabi Hot Cloud bucket. If you prefer to keep footage indefinitely or purge clips manually, feel free to skip this step.

Wasabi Hot Cloud Retention Window

Select timeline to generate policy

Applying lifecycle expiration is optional. If you want automated retention, apply this configuration to your Wasabi Hot Cloud bucket to automatically purge or transition clips older than 30 days, preventing runaway storage bills.

cctv-lifecycle.json (30-day retention for /axis-p3245/)

{
  "Rules": [
    {
      "ID": "axis-p3245-v-cctv-retention-policy",
      "Status": "Enabled",
      "Filter": {
        "Prefix": "axis-p3245/"
      },
      "Expiration": {
        "Days": 30
      }
    }
  ]
}

Apply via AWS / S3 CLI

aws s3api put-bucket-lifecycle-configuration \
  --bucket my-cctv-surveillance-bucket \
  --lifecycle-configuration file://cctv-lifecycle.json

Wasabi Hot Cloud vs other cloud storage for Axis P3245-V HDTV 1080p Dome Camera

How Wasabi Hot Cloud compares with the other providers Rilavek can stream into.

Provider	Billing model	Egress fees	Retention control
Cloudflare R2	Usage-based (storage + operations)	Free egress	S3 Lifecycle expiration & transitions
Backblaze B2	Usage-based (per GB stored)	Free up to 3x stored data/day, then metered	S3 Lifecycle expiration
Wasabi Hot Cloud	Flat-rate (no egress/API fees; minimum storage duration)	Free egress	S3 Lifecycle + 90-day minimum storage duration
IDrive e2	Low usage-based (per GB stored)	Free egress	S3 Lifecycle expiration
DigitalOcean Spaces	Flat base (storage + egress allowance), then per-GB	Included allowance, then metered	S3 Lifecycle expiration
AWS S3	Usage-based (storage + requests + egress)	Metered per GB	S3 Lifecycle expiration, transitions & Glacier archiving
Self-Hosted S3	Self-hosted (your hardware/power)	Your own network	Depends on your S3 server's lifecycle support

How to Backup Axis P3245-V HDTV 1080p Dome Camera to Wasabi Hot Cloud

High-performance enterprise dome with Lightfinder 2.0 and encrypted FTPS/SFTP. Follow our step-by-step setup guide below to stream footage directly into AWS S3, Cloudflare R2, or Backblaze B2 via FTP, FTPS, or SFTP with Rilavek as the pipe, zero on-prem NVR required.

Get Started Free10 GB/mo free ingest included

Jump to:Advantages Data Flow Setup Steps Comparison FAQ

Zero NVR Vulnerability

Your Axis P3245-V uploads footage offsite in real time. Intruders cannot steal or destroy evidence by seizing on-prem recorder hardware.

S3-Native Retention

Store Axis P3245-V recordings on your own terms. Apply automated bucket lifecycle rules to roll over or archive clips after 30, 90, or 365 days.

Direct Streaming Bridge

Rilavek ingests native FTP, FTPS, and SFTP streams from your Axis P3245-V and writes them directly into multipart S3 PUTs with zero disk writes.

Axis P3245-V HDTV 1080p Dome Camera

FTP/FTPS/SFTP

Rilavek Bridge

S3 API

Wasabi Hot Cloud

Step-by-Step Setup Guide for Axis P3245-V HDTV 1080p Dome Camera

Follow these 8 steps to select your cloud provider, provision your object storage, configure Rilavek’s Data Store, Sender, and Ingestion Pipe, enter your camera firmware settings, verify ingestion, and establish automated S3 retention rules.

Step 1Select Cloud Step 2Bucket & Keys Step 3Data Store Step 4Camera Sender Step 5Ingestion Pipe Step 6Camera Setup Step 7Verify Ingest Step 8 · OptionalLifecycle Policy

01

Select Your Cloud Storage Provider

Choose where you want to store your Axis surveillance footage. Selecting a provider customizes the bucket setup steps, endpoint URLs, and API key instructions in Step 2.

02

Set Up Your Wasabi Hot Cloud Bucket & Generate API Keys

Configure your target bucket and API credentials inside Wasabi Hot Cloud so Rilavek can stream motion clips and continuous video directly into your storage.

1

Create a Wasabi Hot Cloud Storage Bucket

Log into the Wasabi Console and select Create Bucket . Choose your preferred datacenter region and assign a unique bucket name.

2

Generate an API Access Key

Go to Access Keys in the left sidebar and click Create New Access Key . Create a sub-user key or standalone key with permissions restricted to your surveillance bucket.

3

Save API Credentials & Endpoint URL

Download the credentials file or copy your API Key and Secret Key. Wasabi regional endpoints use https://s3.<region>.wasabisys.com (for example, https://s3.us-east-1.wasabisys.com).

Official Wasabi Hot Cloud Documentation

Bucket Setup & Regions

Official guide for bucket provisioning, tiers, and privacy

API & Access Keys Guide

Generate and scope Access Key & Secret Key pairs

03

Add Your Data Store in Rilavek

In your Rilavek dashboard, navigate to Data Stores > New Data Store, select your provider, and enter your S3 credentials. Rilavek verifies the connection with an automated write-probe before saving.

Grant minimal S3 permissions only.Rilavek needs minimal, write-focused actions and nothing more.

Read our S3 Permissions Guide

Rilavek Dashboard · Data Stores > New S3 Data Store

Add New Data Store

S3 Compatible

Data Store Name *

Axis Surveillance Storage

Endpoint *

https://s3.<region>.wasabisys.com

Access Key ID *

AKIAIOSFODNN7EXAMPLE

Secret Access Key *

••••••••••••••••••••••••••••••••

Bucket Name *How to create →

cctv-axis-recordings

Region *

us-east-1

Automatically executes multipart write-probe test before saving.Save Data Store

Fig 1: Add New S3 Data Store configuration in the Rilavek console.

04

Create a Camera Sender in Rilavek

Go to Senders in the Rilavek sidebar and click New Sender. A Sender represents the hardware identity of your Axis P3245-V HDTV 1080p Dome Camera and generates a dedicated device-level password.

Rilavek Dashboard · Senders > Create New Sender Modal

Create New Sender

Display Name *

Axis P3245-V HDTV 1080p Dome Camera

Username *

cam_p3245v

Must be at least 6 characters, lowercase, start with a letter/underscore, and contain only letters, numbers, hyphens, or underscores.

Email (Optional)

security@axis-cctv.local

Secure credentials will be automatically generated for this sender.

CancelCreate Sender

Fig 2: Create New Sender modal assigning dedicated camera hardware identity.

Rilavek Dashboard · Senders > Generated Device Credentials

Sender Credentials

Make sure to copy your password now as you will not be able to see it again.

Username

cam_p3245v

PasswordSave for Step 6

••••••••••••

Done

Fig 3: Generated device-level username and one-time password for camera authentication.

05

Create & Configure Your Ingestion Pipe in Rilavek

Go to Pipes in the sidebar and click Create Pipe. Configure the 4 core sections of your pipeline: General (Pipe ID), Inputs (FTP), Access Control (Sender permission), and Destinations (Data Store).

1General Settings (Pipe ID)

Every pipeline in Rilavek is assigned an immutable, globally unique Pipe ID (e.g. p_cctv9x). This ID acts as an isolated ingestion channel that segregates audit logs, real-time transfer metrics, and storage routing. It also forms the second half of your scoped camera FTP login username (username@p_cctv9x).

Rilavek Dashboard · Pipes > Pipeline Settings > General

Pipe ID

p_cctv9x

Use this ID to identify this pipe in logs. Combine it with the sender username for complete authentication details.

Fig 4: General settings displaying the unique Pipe ID used for authentication.

2Inputs (FTP / FTPS Ingress)

The Inputs configuration defines how camera files enter Rilavek. Enabling the FTP Ingress input provides a persistent, high-availability ingestion server (ftp.rilavek.com) compatible with active and passive FTP modes, explicit TLS negotiation, and standard CCTV firmware video push routines.

Rilavek Dashboard · Pipes > Pipeline Settings > Inputs

Inputs

Enable inputs to receive data.

1 input enabled

FTP

SFTP

FTP Ingress

Endpoint enabled. Connect using your Sender credentials.

Host

ftp.rilavek.com

Port

21

Username

<sender>@p_cctv9x

Example: cam_p3245v@p_cctv9x

Password

••••••••••••

Use the password configured for the specific Sender.

Fig 5: Enabling the FTP Ingress endpoint for incoming surveillance video streams.

3Access Control (Sender Authorization)

Access Control prevents unauthorized uploads by enforcing a zero-trust boundary on the ingestion pipe. Only explicitly authorized Senders (such as Axis P3245-V HDTV 1080p Dome Camera) can authenticate and stream video into this pipe. Any requests with unassigned credentials are rejected at the network edge.

Rilavek Dashboard · Pipes > Pipeline Settings > Access Control

Access Control

Restricts who can upload to this pipe.

1 sender allowed

1Individuals

Groups

Individual Senders

Grant or revoke pipe access for specific individual senders.

Axis P3245-V HDTV 1080p Dome Camera

cam_p3245v@p_cctv9x

Fig 6: Restricting pipeline ingress access to your authorized camera Sender.

4Destinations (Target Cloud Storage Routing)

The Destinations section routes video clips to your target cloud storage provider. Linking your configured Data Store routes all received footage directly to your Wasabi Hot Cloud bucket (cctv-axis-recordings). Video files are committed on-the-fly via parallel multipart S3 PUTs without intermediate disk caching.

Rilavek Dashboard · Pipes > Pipeline Settings > Destinations

Destinations

This is where we send your files to.

1 destination added

Axis Storage (Wasabi Hot Cloud)

Primary

Target Bucketcctv-axis-recordingsProviderWasabi Hot CloudStatusActive (Ready for camera ingress)

Fig 7: Routing incoming camera footage directly into your S3-compatible cloud bucket.

Camera Connection Parameters (Enter in Step 6):Reference Values

Server Hostftp.rilavek.com

Port21

Usernamecam_p3245v@p_cctv9x

06

Configure FTP, Motion Detection & Linkage Method in Axis P3245-V HDTV 1080p Dome Camera Firmware

Open your camera's web configuration page in your browser at its local LAN IP address and complete the steps below:

Step 6AConfigure FTP Streaming Credentials

Click System > Events > Recipients.

Navigate to Events > Recipients and click 'Add...' to open the Recipient Setup dialog. Name the recipient 'Recipient_FTP', set Type to 'FTP', enter your Rilavek Ingestion Host, port 21, scoped username, and device password. Ensure 'Use passive mode' is checked as indicated below.

AXIS P3245-V Network Camera

Recipients

?

Recipients List

Name	Type	Address	Upload path	User name
Recipient_FTP	FTP	ftp.rilavek.com	/axis-p3245/	cam_p3245v@p_cctv9x

1 recipient configured

Recipient Setup

?

Name:

Type:

▼

Network address:

↳Rilavek Ingestion Gateway: Direct S3 gateway endpoint for your Wasabi Hot Cloud bucket.

Upload path:

Port number:

Login Credentials

User name:

↳Scoped Rilavek User: cam_p3245v@p_cctv9x (Sender@Pipe).

Password:

The FTP password associated with the camera license (Device password from Step 3)

Advanced Settings

Use passive mode

Use temporary mode

Test

Test the connection to the specified FTP server S3 Ingestion Gateway verified

Step 6BConfigure Action Rule Trigger (VMD 4 / Motion Analytics)

Click Events > Action Rules > Add.

Navigate to Events > Action Rules and click 'Add...'. Check 'Enable rule', name it 'FTP_Motion_Upload', and configure Condition > Trigger to 'Applications' with 'VMD 4: Any Profile' (Axis Video Motion Detection) so camera recording triggers on motion.

AXIS P3245-V Network Camera

Action Rules

?

Action Rule List

Name	Trigger	Schedule	Action	Recipient
SFTP-Upload	Time - Recurrence	Continuous-Uploading	Send Video Clip	SFTP: ftp.cameraftp.com

1 action rule configured

Action Rule Setup

?

General

Enable rule

Name:

Condition

Trigger:

▼

Start condition only

▼

Active:

Yes

No

↳Axis Motion Trigger: Uses VMD 4 (Video Motion Detection) application profile so recording triggers only on detected movement.

Schedule:

▼

Additional conditions

None

▲▼

Wait at leastbefore re-running the rule (max 23:59:59)

Step 6CLink Action Rule to FTP Recipient (Image & Video Upload)

Click Events > Action Rules > Actions.

Under Actions in the Action Rule Setup dialog, set Type to 'Send Images' (or 'Send Video Clip'), configure Stream profile and frequency, select 'Recipient_FTP' as Recipient, and check 'Add date/time suffix' for Base file name. Click OK to start streaming.

AXIS P3245-V Network Camera

Action Rule Setup

?

Actions

Type:

▼

Stream profile:

▼

Image frequency:

frame(s) per

▼

Duration:

Pre-trigger timesecond(s)

While the rule is active

Post-trigger timesecond(s)

Limit:

Send only the firstimages

Recipient:

▼

*Create folder:

*Base file name:

Add date/time suffix

Add sequence number suffix (no maximum value)

Add sequence number suffix up to 10 and then start over

Overwrite/Use own file format.

*See help for more information

↳Action Linkage: Streams motion events directly into your Wasabi Hot Cloud storage bucket with UTC timestamps.

07

Verify Ingestion

Click Test in your camera's FTP settings or trigger a test recording transfer. In your Rilavek dashboard, navigate to Pipes > your pipeline > Transfers tab to inspect incoming files as video clips stream into Wasabi Hot Cloud.

Rilavek Dashboard · Pipes > Transfers

Overview

Transfers

Refresh

FILE	SENDER	SIZE	DATE	STATE
axis/p3245-v/2026-09-10/ch01_143000.mp4	cam_p3245v	18.4 MB	Sep 10, 14:30	Success
axis/p3245-v/2026-09-10/ch01_142500.mp4	cam_p3245v	21.2 MB	Sep 10, 14:25	Success
axis/p3245-v/2026-09-10/ch01_142000.mp4	cam_p3245v	19.7 MB	Sep 10, 14:20	Success

Showing 3 of 3 transfers

Fig 8: Transfers log confirming incoming camera recordings streaming directly into cloud storage.

Direct S3 Ingest VerifiedIncoming surveillance streams are committed on-the-fly directly to your Wasabi Hot Cloud bucket with zero local buffering and no intermediate disk storage.

08

Configure Wasabi Hot Cloud Bucket Lifecycle & Retention Rules (Optional)

Optional: Prevent runaway storage costs by configuring automated bucket expiration rules. Select your retention window below and apply the generated JSON lifecycle policy or CLI command to your Wasabi Hot Cloud bucket. If you prefer to keep footage indefinitely or purge clips manually, feel free to skip this step.

Wasabi Hot Cloud Retention Window

Select timeline to generate policy

Applying lifecycle expiration is optional. If you want automated retention, apply this configuration to your Wasabi Hot Cloud bucket to automatically purge or transition clips older than 30 days, preventing runaway storage bills.

cctv-lifecycle.json (30-day retention for /axis-p3245/)

{
  "Rules": [
    {
      "ID": "axis-p3245-v-cctv-retention-policy",
      "Status": "Enabled",
      "Filter": {
        "Prefix": "axis-p3245/"
      },
      "Expiration": {
        "Days": 30
      }
    }
  ]
}

Apply via AWS / S3 CLI

aws s3api put-bucket-lifecycle-configuration \
  --bucket my-cctv-surveillance-bucket \
  --lifecycle-configuration file://cctv-lifecycle.json

Wasabi Hot Cloud vs other cloud storage for Axis P3245-V HDTV 1080p Dome Camera

How Wasabi Hot Cloud compares with the other providers Rilavek can stream into.

Provider	Billing model	Egress fees	Retention control
Cloudflare R2	Usage-based (storage + operations)	Free egress	S3 Lifecycle expiration & transitions
Backblaze B2	Usage-based (per GB stored)	Free up to 3x stored data/day, then metered	S3 Lifecycle expiration
Wasabi Hot Cloud	Flat-rate (no egress/API fees; minimum storage duration)	Free egress	S3 Lifecycle + 90-day minimum storage duration
IDrive e2	Low usage-based (per GB stored)	Free egress	S3 Lifecycle expiration
DigitalOcean Spaces	Flat base (storage + egress allowance), then per-GB	Included allowance, then metered	S3 Lifecycle expiration
AWS S3	Usage-based (storage + requests + egress)	Metered per GB	S3 Lifecycle expiration, transitions & Glacier archiving
Self-Hosted S3	Self-hosted (your hardware/power)	Your own network	Depends on your S3 server's lifecycle support

Frequently Asked Questions about Axis P3245-V Cloud Storage

Does the Axis P3245-V HDTV 1080p Dome Camera require an on-site NVR to stream to cloud storage?

No. The Axis P3245-V HDTV 1080p Dome Camera has built-in FTP / SFTP client firmware. It connects directly to Rilavek's cloud bridge on port 21, streaming video chunks into your S3 bucket without requiring an on-prem NVR or dedicated PC.

Which cloud storage providers work with P3245-V?

Rilavek supports any provider with an S3-compatible API, including Cloudflare R2, Backblaze B2, AWS S3, Wasabi, IDrive e2, and self-hosted MinIO or RustFS instances.

How does video retention work?

You define retention policies (such as 30, 60, or 90 days) directly on your S3 bucket using lifecycle expiration rules. Your recordings are under your 100% control with zero vendor lock-in.

How to Backup Axis P3245-V HDTV 1080p Dome Camera to Cloud Storage

Create your free Rilavek ingestion pipe in seconds. No NVR hardware, no proprietary camera cloud subscriptions, and 100% data ownership in your private storage bucket.

Get Started Free View All Camera Models

Free plan includes 10GB of transfer. No credit card required.