NoSuchTagSetError Error When Using AWS CLI v2 to Move Data in Wasabi

  • Updated on Aug 12, 2024
  • Published on Dec 14, 2023
  • 1 minute(s) read
Prev Next

Why am I getting a NoSuchTagSetError error when using AWS CLI v2 to move data in Wasabi?

Sometimes AWS CLI tries to fetch tagging from objects that do not have them when utilizing the 'mv' or 'sync' commands. This is a change from AWS CLI v1 to v2 and how it handles file properties. This error is seen when moving data from one bucket to another, or data within the same bucket but between different prefixes.

Wasabi does not currently support Object Tagging, so to ignore tagging in your command, add the --copy-props metadata-directive​ flag. This tells AWS CLI to not copy any tags, but to retain the rest of the metadata associated with the object.

For example:

aws s3 mv s3://mybucket/oldname.txt s3://mybucket/newname.txt --copy-props metadata-directive
    --endpoint-url=https://s3.wasabisys.com

For more information, review the official AWS documentation: https://docs.aws.amazon.com/cli/latest/userguide/cliv2-migration.html#cliv2-migration-s3-copy-metadata