permissions - Why wouldn't an S3 ACL "stick"? -


We want to set up ACL to access one of our buckets with a partner account. We have tested the test account process and everything works fine. On our production account / bucket, however, we can set ACL and see updates, but as soon as we try to reach the bucket with another account, we get a restricted response. After this, when we see the ACL list for the bucket, the permission has been exhausted.

We have tried to use both Amazon's new S3 tool in the AWS Management Console and CloudBerry Explorer and both tools display exactly the behavior. Using the same process to update the ACL from our testing account works as expected (ACL update "sticks").

What would not be the reason for "stick" the ACL? Anyone have any idea about how to solve / solve the problem?

It's been a long time since I asked this question, and since then I have worked on this issue Have done

As I remember, it appears that some policies had changed the nature, but the legalist still has accepted the old format. However, the old format policy will not be accepted, so the policy will not "stick" properly.


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -