Adding to inventory multiple S3 Object Storage from the same account

[tgwatsdwv]

Hello everyone,

I'm currently using VEEAM B&R to backup content stored in Wasabi buckets (S3 Compatible).

Everything is going well technically, but I'm encountering a small issue that is bugging me a little.
When I try to add a new object storage in Files -> Unstructured Data, I'm only able to add 2 object storage originating from the same account.
Whenever I try to add a new one, I encounter the following message :
S3-compatible object storage [Wasabi administrator's account name] with region [region name] already exists.

I would really like to use more than 2 accounts, each dedicated to backup the data stored in a specific Wasabi bucket, but it does not seem to be possible.

I saw that a topic was created last year which was kind of similar to my issue (file-shares-and-object-storage-f57/addi ... 93661.html) but maybe things have changed since then and I haven't be able to find the necessary information by myself.

Is there a reason why the limit of object storage for buckets in the same account is 2 ? Is there any way to bypass this ? Is VEEAM able to handle this ?

Thanks a lot in advance for your answers,
Have a nice day,

[sfirmes]

@tgwatsdwv welcome to the forums.

While adding the object storage to the list of Unstructured Data, one of the following must be unique

• Owner ID
• Endpoint
• Region

You mentioned you were able to add 2 object storage sources successfully. Can you please confirm that one of the 3 items listed above was unique? Also, can you please confirm that the 3rd object storage source you couldn't add didn't have one of the 3 items unique?

Thanks

[tgwatsdwv]

@sfirmes thank you for your answer,

We tested adding multiple object storage to make sure that at least one of the 3 items you mentioned was unique each time, here are our tests results.

Bucket |Service Point |Credentials | Owner's | Targeted
Used | (Endpoint) | Used | Account | Region
-------------------------------------------------------------------------
Bucket 1 | Service Point 1 | User 1 | Owner ID 1 | Region 1
Bucket 2 | Service Point 1 | User 2 | Owner ID 2 | Region 1
Bucket 3 | Service Point 2 | User 3 | Owner ID 2 |Region 2
Bucket 4 | Service Point 1 | User 4 | Owner ID 2 | Region 1
Bucket 5 | Service Point 3 | User 5 | Owner ID 2 | Region 1

(We have two different Wasabi accounts, that's why there is two distinct Owner ID)

As you can see in our tests, Bucket 2 and 4 have the same Owner ID, Endpoint AND Region and they were able to be added both at the same time as "object storage" objects in VEEAM.
However, trying to add another object storage with the same configuration as them does not work.
We also tried and failed to :
- Add as object storage a second bucket from our first Wasabi account (same error that I described in my first post)
- Add as object storage a bucket using the alternative URL's region value (No buckets were able to be found)
- Add as object storage a bucket using a made up region value (Header error)

I can't seem to understand why one of our configuration allows 2 buckets to be added as object storage instead of one.
It's even weirder when no other configuration allows us to add more than 1 bucket (as intended by VEEAM it seems)

We would like to avoid using one account to backup all of our Wasabi buckets for security reasons.
Is anything planned regarding the use of multiple different credentials (and therefore, multiple different object storage) for the same Wasabi account ?

Thanks a lot for your time,
Have a nice day,

[sfirmes]

The fact that you are saying that your bucket #2 and bucket #4 have the same Owner ID, Endpoint, and Region; but you were able to add them successfully as object storage sources is not the behavior that I expect. Have you opened a support case with Veeam Support? If not, I recommend that you do so that we can identify why buckets 2 and 4 were allowed to be sources (more specifically #4).

Thanks

[sfirmes]

@tgwatsdwv I did some additional testing using my Wasabi account and wanted to share my results.

I typically use my root account since this is just for testing and when I do a list-buckets, they all have the same "Owner" "ID":

aws s3api list-buckets --endpoint-url https://s3.wasabisys.com
{
"Buckets": [
{
"Name": "wasabi1",
"CreationDate": "2025-08-26T18:00:19+00:00"
},
{
"Name": "wasabi2",
"CreationDate": "2025-08-26T18:00:49+00:00"
}
],
"Owner": {
"DisplayName": "veeam.steve",
"ID": "AB1027DB3AF893727E96FA811466969ZZE9A3E23AXXBA62314DA733549D94A34"
},
"Prefix": null
}

I then created a user Wasabi-Steve and created a new bucket using that user. The new bucket also has the "Owner" "ID" of the root user:
aws s3api list-buckets --endpoint-url https://s3.wasabisys.com
{
"Buckets": [
{
"Name": "wasabi1",
"CreationDate": "2025-08-26T18:00:19+00:00"
},
{
"Name": "wasabi2",
"CreationDate": "2025-08-26T18:15:29+00:00"
},
{
"Name": "wasabi-steve-1",
"CreationDate": "2025-08-26T18:30:01+00:00"
}
],
"Owner": {
"DisplayName": "veeam.steve",
"ID": "AB1027DB3AF893727E96FA811466969ZZE9A3E23AXXBA62314DA733549D94A34"
},
"Prefix": null
}


So are you using 1 account with multiple users or are you using multiple accounts? This info will help me with my testing.

Thanks