Connecting S3 storage

Purpose

S3-compatible storage specifies the location for storing metadata and backup data Velero. In Kubernetes, it is represented by the resource BackupStorageLocation in the namespace velero. The location name is then indicated in the backups (the spec.storageLocation field or an equivalent in the form).

Checking in a cluster:

kubectl get backupstoragelocation -n velero

In the cluster or namespace GUI

Backup and Restore → Storages → Add Storage.

Screenshots (list, form, manifest)

List of storages

Adding storage

Advanced storage options

View storage

Storage manifest

Connection parameters (basic mode in the GUI)

ParameterRequiredDescription
Storage nameYesUnique name. Cannot be changed after saving.
BucketYesBucket where backups are stored.
DirectoryNoSubfolder in the bucket for backups.
UsernameYesS3 account.
PasswordYesAccess secret.
RegionYesStorage region.
S3 addressYesURL (FQDN or IP). Examples: http://example.com:9000, https://11.11.111.11.
Verify certificate—Whether to validate the TLS certificate.
Certificate fileNoCA certificate for verification, if needed.

If you connect without TLS, you can skip the certificate download.


Advanced options

ParameterDescription
S3ForcePathStylePath-style addressing to S3 (default - yes).
ProviderNatively supported by AWS, MinIO
Synchronization interval (backupSyncPeriod)Interval for syncing the backup catalog with object storage. Default is 2 minutes.

View and change

The status and parameters are shown on the storage page. To change a connected storage, open it from the list, update the parameters (the password is required), and save. In the form you can change Bucket, Directory, username, password, region, S3 address, certificate verification settings, and advanced options.

Storage name cannot be changed after creation. To change the BackupStorageLocation name, create a new storage and use it in new backups or schedulers.

If you edit YAML on the Manifest tab, click Check: the result appears on the right. If manifest format validation fails, checking is unavailable. Save the changes or they will not apply.

Delete a storage from the list page, the detail page (Delete), or by deleting the resource on the manifest tab. In the cluster and namespace storage lists you can delete one storage or several at once. How to select objects and confirm deletion: Bulk deletion.

Deleting backups from storage on the platform side is asynchronous and may fail. If the bucket already contained backups when the storage was connected, they may appear in the GUI after synchronization.


Example values for MinIO / S3-compatible storage

ParameterExample
Bucketvelero-backups
S3 addresshttps://minio.example.com:9000
Regionminio or AWS region (for example us-east-1)
S3ForcePathStyleYes for MinIO and many compatible servers