Restic with wasabi repository - Issues after init and first backup

[gm1]

Thank you.

I started with a policy like yours and then following:

Append-only mode with S3 (Wasabi)

Hello, I am using Wasabi to store my backups. Here’s a basic IAM policy I use that gives the user full access to the bucket: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "s3:ListBucket", "Resource": "arn:aws:s3:::angristan-test" }, { "Effect": "Allow", "Action": [ "s3:PutObject", "s3:GetObject", "s3:DeleteObject" ], "Resource": "arn:aws:s3:::angristan-test/*" } ] } I would like…

And also following:

@lukastribus

@angristan make an additional policy allowing s3:DeleteObject only in the lock directory arn:aws:s3:::angristan-test/lock/*

I made the changes.

I could return to:

@D.O.Scott

“Action”: [
“s3:PutObject”,
“s3:GetObject”,
“s3:DeleteObject”
],

And see what happens.

Do you think that I should keep the specific?

@gm1

{ “Effect”: “Allow”, “Action”: “s3:DeleteObject”, “Resource”: “arn:aws:s3:::xxx/locks/*” }

Regarding

@D.O.Scott

Does this mean you will never do a prune?

I am still not familiar with that operation but it suggest some cleaning and that I should have a broader DeleteObject policy.