1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
|
===============
Bucket Policies
===============
.. versionadded:: Luminous
The Ceph Object Gateway supports a subset of the Amazon S3 policy
language applied to buckets.
Creation and Removal
====================
Bucket policies are managed through standard S3 operations rather than
radosgw-admin.
For example, one may use s3cmd to set or delete a policy thus::
$ cat > examplepol
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Principal": {"AWS": ["arn:aws:iam::usfolks:user/fred:subuser"]},
"Action": "s3:PutObjectAcl",
"Resource": [
"arn:aws:s3:::happybucket/*"
]
}]
}
$ s3cmd setpolicy examplepol s3://happybucket
$ s3cmd delpolicy s3://happybucket
Limitations
===========
Currently, we support only the following actions:
- s3:AbortMultipartUpload
- s3:CreateBucket
- s3:DeleteBucketPolicy
- s3:DeleteBucket
- s3:DeleteBucketWebsite
- s3:DeleteObject
- s3:DeleteObjectVersion
- s3:DeleteReplicationConfiguration
- s3:GetAccelerateConfiguration
- s3:GetBucketAcl
- s3:GetBucketCORS
- s3:GetBucketLocation
- s3:GetBucketLogging
- s3:GetBucketNotification
- s3:GetBucketPolicy
- s3:GetBucketRequestPayment
- s3:GetBucketTagging
- s3:GetBucketVersioning
- s3:GetBucketWebsite
- s3:GetLifecycleConfiguration
- s3:GetObjectAcl
- s3:GetObject
- s3:GetObjectTorrent
- s3:GetObjectVersionAcl
- s3:GetObjectVersion
- s3:GetObjectVersionTorrent
- s3:GetReplicationConfiguration
- s3:IPAddress
- s3:NotIpAddress
- s3:ListAllMyBuckets
- s3:ListBucketMultipartUploads
- s3:ListBucket
- s3:ListBucketVersions
- s3:ListMultipartUploadParts
- s3:PutAccelerateConfiguration
- s3:PutBucketAcl
- s3:PutBucketCORS
- s3:PutBucketLogging
- s3:PutBucketNotification
- s3:PutBucketPolicy
- s3:PutBucketRequestPayment
- s3:PutBucketTagging
- s3:PutBucketVersioning
- s3:PutBucketWebsite
- s3:PutLifecycleConfiguration
- s3:PutObjectAcl
- s3:PutObject
- s3:PutObjectVersionAcl
- s3:PutReplicationConfiguration
- s3:RestoreObject
We do not yet support setting policies on users, groups, or roles.
We use the RGW ‘tenant’ identifier in place of the Amazon twelve-digit
account ID. In the future we may allow you to assign an account ID to
a tenant, but for now if you want to use policies between AWS S3 and
RGW S3 you will have to use the Amazon account ID as the tenant ID when
creating users.
Under AWS, all tenants share a single namespace. RGW gives every
tenant its own namespace of buckets. There may be an option to enable
an AWS-like 'flat' bucket namespace in future versions. At present, to
access a bucket belonging to another tenant, address it as
"tenant:bucket" in the S3 request.
In AWS, a bucket policy can grant access to another account, and that
account owner can then grant access to individual users with user
permissions. Since we do not yet support user, role, and group
permissions, account owners will currently need to grant access
directly to individual users, and granting an entire account access to
a bucket grants access to all users in that account.
Bucket policies do not yet support string interpolation.
For all requests, condition keys we support are:
- aws:CurrentTime
- aws:EpochTime
- aws:PrincipalType
- aws:Referer
- aws:SecureTransport
- aws:SourceIp
- aws:UserAgent
- aws:username
We support certain s3 condition keys for bucket and object requests.
.. versionadded:: Mimic
Bucket Related Operations
~~~~~~~~~~~~~~~~~~~~~~~~~~
+-----------------------+----------------------+----------------+
| Permission | Condition Keys | Comments |
+-----------------------+----------------------+----------------+
| | s3:x-amz-acl | |
| | s3:x-amz-grant-<perm>| |
|s3:createBucket | where perm is one of | |
| | read/write/read-acp | |
| | write-acp/ | |
| | full-control | |
+-----------------------+----------------------+----------------+
| | s3:prefix | |
| +----------------------+----------------+
| s3:ListBucket & | s3:delimiter | |
| +----------------------+----------------+
| s3:ListBucketVersions | s3:max-keys | |
+-----------------------+----------------------+----------------+
| s3:PutBucketAcl | s3:x-amz-acl | |
| | s3:x-amz-grant-<perm>| |
+-----------------------+----------------------+----------------+
.. _tag_policy:
Object Related Operations
~~~~~~~~~~~~~~~~~~~~~~~~~~
+-----------------------------+-----------------------------------------------+-------------------+
|Permission |Condition Keys | Comments |
| | | |
+-----------------------------+-----------------------------------------------+-------------------+
| |s3:x-amz-acl & s3:x-amz-grant-<perm> | |
| | | |
| +-----------------------------------------------+-------------------+
| |s3:x-amz-copy-source | |
| | | |
| +-----------------------------------------------+-------------------+
| |s3:x-amz-server-side-encryption | |
| | | |
| +-----------------------------------------------+-------------------+
|s3:PutObject |s3:x-amz-server-side-encryption-aws-kms-key-id | |
| | | |
| +-----------------------------------------------+-------------------+
| |s3:x-amz-metadata-directive |PUT & COPY to |
| | |overwrite/preserve |
| | |metadata in COPY |
| | |requests |
| +-----------------------------------------------+-------------------+
| |s3:RequestObjectTag/<tag-key> | |
| | | |
+-----------------------------+-----------------------------------------------+-------------------+
|s3:PutObjectAcl |s3:x-amz-acl & s3-amz-grant-<perm> | |
|s3:PutObjectVersionAcl | | |
| +-----------------------------------------------+-------------------+
| |s3:ExistingObjectTag/<tag-key> | |
| | | |
+-----------------------------+-----------------------------------------------+-------------------+
| |s3:RequestObjectTag/<tag-key> | |
|s3:PutObjectTagging & +-----------------------------------------------+-------------------+
|s3:PutObjectVersionTagging |s3:ExistingObjectTag/<tag-key> | |
| | | |
+-----------------------------+-----------------------------------------------+-------------------+
|s3:GetObject & |s3:ExistingObjectTag/<tag-key> | |
|s3:GetObjectVersion | | |
+-----------------------------+-----------------------------------------------+-------------------+
|s3:GetObjectAcl & |s3:ExistingObjectTag/<tag-key> | |
|s3:GetObjectVersionAcl | | |
+-----------------------------+-----------------------------------------------+-------------------+
|s3:GetObjectTagging & |s3:ExistingObjectTag/<tag-key> | |
|s3:GetObjectVersionTagging | | |
+-----------------------------+-----------------------------------------------+-------------------+
|s3:DeleteObjectTagging & |s3:ExistingOBjectTag/<tag-key> | |
|s3:DeleteObjectVersionTagging| | |
+-----------------------------+-----------------------------------------------+-------------------+
More may be supported soon as we integrate with the recently rewritten
Authentication/Authorization subsystem.
Swift
=====
There is no way to set bucket policies under Swift, but bucket
policies that have been set govern Swift as well as S3 operations.
Swift credentials are matched against Principals specified in a policy
in a way specific to whatever backend is being used.
|
