Aws-cli: [Feature Request] Add tagging support to s3

[mhayes14]

It would be great if we could tag S3 objects while using s3 commands such as "cp" and "sync".

Thanks!

[kyleknap]

Marking as a feature request. So something like adding a --tagging parameter to cp and sync?

[mhayes14]

Marking as a feature request.

Thanks!

So something like adding a --tagging parameter to cp and sync?

Yup, it would be great to take advantage of object tagging while using the CLI.

[kyleknap]

Thanks for clarifying. Makes sense to me.

[dinvlad]

+1, our use case is to enforce CLI users to tag their multipart uploads (through s3:RequestObjectTag/<tag-key> policy condition for PutObject, unless it doesn't work that way).

[yvele]

Did someone found a quick and simple workaround?

[dinvlad]

One workaround is to tag objects on the server side after the user uploaded their files. The main limitation to that is eventual consistency, i.e. the uploaded files may not appear in the listing right away, so you'd need to introduce an arbitrary delay before labeling (I'd also check the combined hash of all keys and ETags as a way of ensuring the listing is 'stable').

[yvele]

@dinvlad Yes I was thinking using an AWS Lambda that triggers when an S3 object is put.. But that's a bit overkill for such a basic feature.. 😄

[dinvlad]

@yvele agreed, it would be nice to have it out of the box. However, it does put more burden on the user because now they also need to remember how to apply tags appropriately.

[ASayre]

Good Morning!

We're closing this issue here on GitHub, as part of our migration to UserVoice for feature requests involving the AWS CLI.

This will let us get the most important features to you, by making it easier to search for and show support for the features you care the most about, without diluting the conversation with bug reports.

As a quick UserVoice primer (if not already familiar): after an idea is posted, people can vote on the ideas, and the product team will be responding directly to the most popular suggestions.

We’ve imported existing feature requests from GitHub - Search for this issue there!

And don't worry, this issue will still exist on GitHub for posterity's sake. As it’s a text-only import of the original post into UserVoice, we’ll still be keeping in mind the comments and discussion that already exist here on the GitHub issue.

GitHub will remain the channel for reporting bugs.

Once again, this issue can now be found by searching for the title on: https://aws.uservoice.com/forums/598381-aws-command-line-interface

-The AWS SDKs & Tools Team

This entry can specifically be found on UserVoice at: https://aws.uservoice.com/forums/598381-aws-command-line-interface/suggestions/33168343--feature-request-add-tagging-support-to-s3

[jamesls]

Based on community feedback, we have decided to return feature requests to GitHub issues.

[eikenb]

You can tag from the cli using aws s3api put-object-tagging .... I'm currently using it in combo with aws s3 mv ... to migrate some data w/ tags. It works, but I'd rather have it in one call so that if I need to interrupt the script I wouldn't have to worry about something missing the tags.

[bpo]

PR #2890 with boto/s3transfer#96 adds the support for tagging without a second call.

[AbhiPrasad]

Is this still on the table? Would be super helpful to our current workflows!

cc @osman

[trav-c]

I'd like to see this added too, it would simplify parts of our deployment workflow quite a bit.

[NoahSDS]

I want this, too!

[mwhouser]

+1 for an all-in-one "copy and tag".

Without simultaneous tagging, tagging after performing a aws s3 cp . s3://bucket --recursive is difficult.

[ckane]

Have you tried:

aws s3api put-object --bucket bucket-name --key key-name \
  --tagging "Tag_Name=Tag_Value,tag2_name=Tag2_Value" --body filename.ext

[mwhouser]

@ckane Using aws s3api put-object would lose all advantages of using aws s3 cp:

• Multiple file uploads
• Multiple simultaneous uploads, with number and bandwidth throttling
• Many others

[mwkorver]

Noting here that when testing s3 cp and s3api copy-object against small and large files, with existing tagsets, the default behavior is that the tagset gets copied only for small files not large. Guessing that, much like with metadata, the object's tagset is not copied when multi-part is used.

[jsunsch]

Upvote! This would be an excellent feature, as it would greatly enhance my experience with using Lifecycle rules on S3 objects.

[johntdyer]

Wow. I cant believe this is not supported... Please add this