How to retarget Veeam Backup at SkyeBucket
Re-point Veeam Backup & Replication's S3-compatible repository at SkyeConnex's SkyeBucket gateway. Your existing backup jobs inherit multi-cloud sovereign storage with no SDK changes.
SkyeBucket is the S3-compatible drop-in gateway at s3.skyeconnex.com. Veeam's S3 Compatible Object Storage Repository works with it directly — re-point one endpoint and existing Veeam backup jobs inherit RS(5,2)">Reed-Solomon RS(5,2) multi-cloud RAID with no Veeam-side reconfiguration.
This procedure works for Veeam Backup & Replication 12.0+ (where the S3-compatible repository type was added). For older versions, a small upgrade is required first.
The procedure
-
STEP 01
Generate SkyeBucket credentials
In your SkyeConnex tenant, navigate to Settings → API Keys. Create a new SigV4-compatible credential pair scoped to the bucket you want Veeam to write to. The credentials include an Access Key ID and Secret Access Key in the standard S3 format. Note: SkyeBucket credentials are tied to a specific bucket; one credential per backup job is the recommended pattern.
-
STEP 02
-
STEP 03
In Veeam, add the S3-compatible repository
Open Veeam Backup & Replication console → Backup Infrastructure → Backup Repositories → Add Repository. Select 'Object Storage', then 'S3 Compatible'. In the Endpoint field, enter https://s3.skyeconnex.com. Region is left as the default; SigV4 handles region context. Credentials are the Access Key ID and Secret Access Key from step 1. Click Next.
-
STEP 04
Configure the bucket and folder
Veeam asks for the bucket name (use the bucket from step 2) and an optional folder path within the bucket. The folder path is recommended — it lets you scope backups by job within a single bucket. Click Next. Veeam tests connectivity, lists existing folders, and confirms write access.
-
STEP 05
Validate with a test backup
Create or modify a backup job to write to the new repository. Run one cycle. Confirm the backup completes and appears in the job history. Open SkyeConnex → File Browser → navigate to the bucket. You should see the Veeam backup files. Open one file's flyout: the per-file SkyeMap shows the shard placement across your seven providers. Generate a signed sovereignty report — Veeam-written objects are subject to the same per-file residency evidence as any other upload.
Common questions
Does this work with Veeam Hardened Repository?
Veeam Hardened Repository is a specific Linux-immutable repo type, distinct from the S3-compatible repository. SkyeBucket implements S3 Object Lock semantics where applicable. For genuine immutability requirements, the multi-cloud RAID topology itself provides strong write-once properties — attackers cannot encrypt or delete shards without compromising five providers.
Can I use the same bucket for multiple backup jobs?
Yes. The folder-path option in step 4 lets you scope by job within a single bucket. The credentials in step 1 can be reused across jobs that share the bucket.
What about Veeam multi-tier or Capacity Tier?
Veeam's Capacity Tier (offloading from Performance Tier to object storage) works the same way — SkyeBucket is just an S3 endpoint. Configure SkyeBucket as the Capacity Tier in the Backup Repository Scale-Out configuration.
Does Veeam encryption interact with SkyeConnex encryption?
Veeam can encrypt backup files before sending; SkyeConnex then re-encrypts at the frame level. The result is end-to-end encrypted with two independent keys. For most workloads this is overkill — turning off Veeam-side encryption simplifies the model without sacrificing security, because SkyeConnex's encryption is zero-knowledge.
Want help configuring this?
A 45-minute briefing walks through this configuration on your tenant, live.