Skip to content

Commit f2c88cf

Browse files
committed
Update doc about IAM policy docuemnt
Signed-off-by: shirady <57721533+shirady@users.noreply.github.com>
1 parent 62b3101 commit f2c88cf

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/design/IamUserInlinePolicy.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -93,3 +93,10 @@ Check the ability of the user to perform S3 operations according to the IAM poli
9393

9494
### Notes:
9595
The IAM policy (like bucket policy) is read from the account info, which is saved in the endpoint cache. Currently, the cache does not invalidate those changes immediately. For local testing, you may temporarily reduce the cache expiry in `src/sdk/object_sdk.js` by setting `expiry_ms: 1`, but this should never be committed to the repository.
96+
97+
We enforce the policy document to have an array in the field of `Statement` even though there are cases of a single item in the array (same behavior as bucket policy document in NooBaa).
98+
Although this IAM policy is legal in AWS:
99+
`{"Version":"2012-10-17","Statement":{"Effect":"Allow","Action":"*","Resource":"*"}}`.
100+
In NooBaa system it should be used with:
101+
`{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Action":"*","Resource":"*"}]}`.
102+
(notice the array in `Statement` field).

0 commit comments

Comments
 (0)