Hi, anyone ever come across `An error occurred (Ac...
# ask-metaflow
b
Hi, anyone ever come across
An error occurred (AccessDenied) when calling the PutObject operation: Access Denied
when using the
S3.put_many
? It could be AWS policy, but just for the sake of testing, I am using the root user, which means this issue should not be related to policy, right?
1
v
it could be a policy issue still depending on the bucket you use. Maybe the bucket is in a different account?
b
No its the same account @victorious-lawyer-58417
I even ran a script testing access programmatically using
boto
and it was fine
How can I check actually? In the same account of the bucket, I see
which must be the bucket from metaflow/outerbounds
i
Verify that there isn't a bucket policy blocking it?
v
metaflow.S3
uses
boto
under the hood so if
boto
works, it should work 🤔 Are you testing them in the same environment with the same credentials etc?
b
Yea, same credentials, so I realized when I tested with boto, I was using the equivalent to
s3.push
for some reason
s3.push_many
triggers an Access Denied
v
do other calls work, e.g
get
?
b
push
works, I haven't tried get, I can try that and get back to you here
👍 1
i
I'm thinking you must mean
put
and
put_many
instead of
push
. The other thing that comes to mind is whether or not you have ListBucket permissions since there is an
overwrite
param which would depend on it.
The easiest way to troubleshoot this is to look in CloudTrail for the failed calls by this user and see what call is getting the AccessDenied
this 1