MinIO Immutability Setup

[NorthGuard]

I am setting up Minio as a s3 compatible immutable repo for Veeam v12 and have run into an issue. When I go to add the bucket in Veeam and tick the option for immutability, I get a message:

selected object storage does not support s3 object lock feature

I am guessing it maybe has something to do with either the underlying file structure ( which is xfs ) or how I create the bucket?

I create the bucket the web gui with the following options:

Bucket Name: bucket01
Object Locking: Enabled - this also auto-enabled Versioning without any other settings

Then I create the bucket.

Any thoughts on what I am missing?

[tjurgens-s2d]

What version of Minio are you trying?
I've done this multiple times. Provided you have the correct access policy and your bucket is created as you say, it should work just fine.

[sfirmes]

@NorthGuard have you tried creating the bucket from the aws cli? I've seen many times that the vendor's gui will sometimes add information to the bucket that we can't use. I wrote a blog post about this topic and hopefully it might help you.

[NorthGuard]

I have not tried using a CLI as the gui appeared to be much more straight foward.

[NorthGuard]

Is there anyone using minio, immutability, and Veeam?

[tjurgens-s2d]

What version of Minio are you trying?
I've done this multiple times. Provided you have the correct access policy and your bucket is created as you say, it should work just fine.

Many times.

[NorthGuard]

I totally missed your post tjurgens!

Version is: minio_20230816201730.0.0_amd64.deb
Running on Ubuntu 22.04
Drive that houses buckets is formatted as xfs

Bucket is configured as stated above.

Policy looks like this:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "BucketAccessForUser",
"Effect": "Allow",
"Action": [
"s3:ListBucket",
"s3:PutObject",
"s3:DeleteObject",
"s3:GetObject"
],
"Resource": [
"arn:aws:s3:::bucket01",
"arn:aws:s3:::bucket01/*"
]
}
]
}

[NorthGuard]

UPDATE:

I changed the policy to this and it seems to be working now!

{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "s3:ListAllMyBuckets",
"Resource": "arn:aws:s3:::*"
},
{
"Effect": "Allow",
"Action": "s3:*",
"Resource": [
"arn:aws:s3:::bucket01",
"arn:aws:s3:::bucket01/*"
]
}
]
}

[tjurgens-s2d]

If you want to be specific about the permissions you provide to your buckets, I suggest following this KB: https://www.veeam.com/kb3151
You missed a few in your original policy.