Hello,

I recently found out that "s3cmd info" returns error 405 when running version 2. Same command on the same bucket returns correct results in 1.6.0.

There are Get* and List* permissions on that bucket.

Is this a bug? Cloud this have started from a change AWS did?

Thanks!

Update:
Just realized this happens when trying to get the bucket policy. It only happens when trying it on a bucket that's located on a different AWS account. Anyone knows if it requires other permissions on cross-account access?

Update 2:
So after talking to AWS support, they say that policy cannot be retrieved cross account. This raised an important question; If this isn't possible, howcome it worked on version 1.6? After testing s3cmd 1.6 in same-account access and cross-account access, it appears that policy was not retrieved on cross-account access - BUT is didn't fail:

same-account:

s3cmd info s3://BUCKET-NAME
s3://BUCKET-NAME/ (bucket):
   Location:  us-east-1
   Payer:     BucketOwner
   Expiration Rule: none
   policy:    {"Version":"2012-10-17","Statement":[{"Sid":"","Effect":"Allow","Principal":{"AWS":"*************"},"Action":["s3:List*","s3:Get*"],"Resource":["arn:aws:s3:::BUCKET-NAME/*","arn:aws:s3:::BUCKET-NAME"]}]}
   cors:      none
   ACL:       ********: FULL_CONTROL

cross-account:

s3cmd info s3://BUCKET-NAME
s3://BUCKET-NAME/ (bucket):
   Location:  us-east-1
   Payer:     BucketOwner
   Expiration Rule: none
   policy:    none
   cors:      none
   ACL:       ********: FULL_CONTROL

Did 1.6 had an error-ignore mechanism that is no longer in 2.0?