I have the following policy in place:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowUserToSeeBucketListInTheConsole",
"Action": [
"s3:GetBucketLocation",
"s3:ListAllMyBuckets"
],
"Effect": "Allow",
"Resource": [
"arn:aws:s3:::*"
]
},
{
"Sid": "AllooUserFullAccessToBucket",
"Effect": "Allow",
"Action": [
"s3:*"
],
"Resource": [
"arn:aws:s3:::mybucket/*"
]
}
]
}
While accessing the bucket via Key/Secret (using Cloudberry Explorer) I can:
- List all buckets
- List, download, upload and delete into mybucket, but only if this also is in place over at bucket permissions:
OR
I have need to add another item to the policy to do away with the bucket level permission requirement:
{
"Sid": "AllooUserFullAccessToBucketPre",
"Effect": "Allow",
"Action": [
"s3:*"
],
"Resource": [
"arn:aws:s3:::mybucket"
]
},
Is there syntax that would enable to have only 2 items (AllowUserToSeeBucketListInTheConsole & a single AllooUserFullAccessToBucket) in the policy while not requiring the bucket level permission?
In my experience, it's been fairly standard practice to make a policy that just grant's access to the bucket and contents.
I'd typically use a policy like this (don't want to allow this user to override bucket permissions, or delete the bucket, etc):
Try this one: