Den ons 1 nov. 2023 kl 17:51 skrev Thomas Bennett <thomas(a)tsolo.io>io>: A good idea. Generally, docs should be lots more clear about which parts are chosen by you, and which ones are inherent from some predefined role, context, your setup, your domain or whatever. It's hard enough to get all the finer points of rgw both from an admin side, and as a power-user talking over the S3 apis, and if examples "hide" things like the above as if perhaps "usfolks" is some weird predefined thing AWS has brought along or something, then it gets lots harder to grasp which parts I am supposed to replace and which must be there. Personally I would prefer colors, bold, or underlines or something to distinguish things I should replace like endpoint url domains, hostnames from the things which are not supposed to change like the whole Resource thing up until the bucket name. Looking at the example given in the docs: "Principal": {"AWS": ["arn:aws:iam::usfolks:user/fred:subuser"]}, "Resource": [ "arn:aws:s3:::happybucket/*" the arn:aws:s3::: seems to indicate you can/should change only the last part after the last : char, and then fill in the bucket name there. The arn:aws:iam on the other hand in this example is not solely the last part after the last :, but also the next-to-last one. While this probably is very obvious if you understand the AWS docs written somewhere 35 links away, it would be nice IMHO if the ceph-rgw example showed or at least hinted to me that it needs me to change two parts in the iam entry and not only the last, because then the example would not require me to also double-check the AWS reference manual to know if I should edit one or two or all of the other :::: sections there. Not saying ceph-rgw needs to fully replicate all of AWS S3 docs, but at least help us out a bit here, please. -- May the most significant bit of your life be positive.

On 12.04.2024 20:54, Wesley Dillingham wrote: This is what we are using, the second statement is so that bucket owner will have access to the object that the user is uploading. s3-policy.json { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": [ "arn:aws:iam:::<tenant>:user/<user>" ] }, "Action": [ "s3:ListBucket", "s3:GetObject", "s3:PutObject" ], "Resource": [ "arn:aws:s3:::<bucket-name>/*", "arn:aws:s3:::<bucket-name>" ] }, { "Sid": "owner_full_access", "Effect": "Allow", "Principal": { "AWS": [ "arn:aws:iam:::<owners-tenant>:user/<owner-user>" ] }, "Action": "s3:*", "Resource": "arn:aws:s3:::*" } ] } And then run s3cmd setpolicy s3-policy.json s3://<bucket-name> -- Kai Stian Olstad