[Feature Request] Configurable Naming/Prefix for Automatically Provisioned Object Storage Buckets

[t7MevELx0]

We would like to make more use of the automatic bucket provisioning feature for object storage repositories, but the automatically generated bucket names make it difficult for us to use operationally.

Today, VBR creates buckets with generated names similar to:

Code: Select all

1dd07473e403fa3655gf23cf9b68ddfe-1781224881-aux
1dd07938e443fa3653ff23cf9b95ddfe-1781224906-aux

For a service provider or larger environment with many repositories and customers, these names provide no immediate indication of which customer or repository the bucket belongs to.

In our case, we enumerate S3 buckets through the storage platform API and use that information for internal reporting, customer assignment, capacity tracking, and billing. With manually created buckets, we can use meaningful names such as:

Code: Select all

customer-a-vbr-backup
customer-b-vbr-backup

With automatic provisioning enabled, however, the VBR-generated bucket names cannot easily be associated with the appropriate customer without introducing additional Veeam-specific mapping logic into our management platform.

It would be very helpful if VBR allowed an administrator to specify a prefix or naming template for automatically provisioned buckets while retaining whatever unique identifiers Veeam requires internally. For example:

Code: Select all

customer-a-1dd07473e403fa3655gf23cf9b68ddfe-1781224881-1781224881-aux

Or perhaps a configurable template based on the repository name:

Code: Select all

<repository-name>-<generated-name>

Even a simple administrator-defined prefix would be sufficient for our use case.

This would allow Veeam to continue handling bucket creation and uniqueness automatically while making the resulting buckets identifiable in the underlying S3 platform, monitoring systems, reporting tools, and service-provider billing platforms.

Ideally, this option would be available through the GUI, PowerShell, and REST API. The administrator should be able to define a prefix or naming template that VBR uses when automatically creating buckets.

Without some form of configurable naming, we are effectively choosing between manually creating customer-identifiable buckets or using automatic bucket provisioning and maintaining a separate mechanism to determine ownership of the generated buckets.

For service-provider environments in particular, having some way to associate an automatically provisioned bucket with a customer or repository from the bucket name itself would be very useful.

[sfirmes]

Thanks for your feedback and suggestion. This request has been noted.