AWS IAM Policy for allowing s3cmd to sync to an S3 bucket

It’s a good idea to set an IAM access policy for anything that accesses AWS using your account details, I wanted to do this for s3cmd syncing a local directory to an s3 bucket. There are a number of posts on setting up the IAM policy for s3cmd already but none of the examples worked, I got a 403 permission denied error when running the s3cmd sync command.

After some digging it turns out that s3cmd now tries to set an ACL on the files it uploads, and this needs to be specifically allowed in the ACL. I’m guessing that it didn’t in the past, hence the now incorrect IAM advice. So here is the new working IAM policy, complete with the s3:PutObjectAcl permission added:

(See jrantil’s comment below on wether s3:ListAllMyBuckets is needed in this instance)

7 thoughts on “AWS IAM Policy for allowing s3cmd to sync to an S3 bucket

  1. jrantil says:

    Hm, just making sure here, why is listing all buckets required?

  2. Will Jessop says:

    It’s so long ago that I forget. It may be that s3cmd sync requires it, but if you test it and find that it isn’t I’d be happy to know.

  3. Laxman SR says:

    Hi,

    Work perfectly for me. thanks a lots.

  4. bfredit says:

    This works great with `aws s3 sync` as well!

  5. I can confirm that the policy without s3:ListAllMyBuckets works for aws s3 sync.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s