Feature Request: Allow adding a custom endpoint to S3 backup repositories

[mike7891]

Hello, please consider adding the feature to the S3 repository wizard to specify a custom endpoint URL. This would allow taking advantage of things like S3 Transfer Acceleration and private endpoints. I understand that there is a way with modifying AmazonS3Regions.xml but it is a hacky workaround at best. Thank you.

[nielsengelen]

Hi,

Are you talking about a specific VBR wizard or VB for AWS?

[mike7891]

Hello, I am talking about when adding an S3 repository to VBR backup infrastructure, not VB for AWS. The current workaround is detailed here for PrivateLink but I imagine it would be applicable to transfer acceleration as well since it is just another endpoint: https://www.veeam.com/kb4226

I searched around a bit to see if it had been requested in the past and I did find one other thread from a few months ago where veremin seemingly came to the same conclusion regarding AmazonS3Regions.xml: object-storage-as-backup-target-f52/s3- ... 98104.html

It sounds like having the ability to add your own endpoints that can be used in place of the ones provided in AmazonS3Regions.xml without needing to modify that file by hand would be a good feature addition to address this.

[mike7891]

Also I now realize I should have posted this in the "Object Storage as Backup Target" section, apologies for any confusion. Did not realize this subforum is specifically for VBAWS.

[nielsengelen]

Hi Mike, I've moved it to the correct section.

[enigma361]

Hi Mike,

I'm not sure this is what you are looking for specifically but if you select S3 compatible as the repository type, you will be able to specify a custom endpoint for the S3 storage.

I can't make a screenshot of the step in the repository wizard right now but here is the section in the manual that describes this (see step 1: "Service point"):
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Hope this helps.

[mike7891]

Hi enigma361, thanks for the suggestion. I actually did think of trying this the other day, but it seems that using the transfer acceleration endpoint does not work here. At least, I could not get it to work with a few different attempts. I think there may be something unique about the transfer acceleration endpoint that is a little different from a typical custom endpoint.