<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=9383740&amp;fmt=gif">
Skip to content
Contact us
  • There are no suggestions because the search field is empty.

Renaming files directly in S3 removes AF.1 metadata

When files are renamed or moved directly in Amazon S3 using third-party tools (for example Cyberduck, rclone or the AWS CLI), any custom metadata created and managed within AirFrame.One (AF.1) for those files is permanently lost. This article explains why this happens and how to avoid it.

Why this happens

Amazon S3 does not support renaming objects in place. A rename or move is processed as a delete of the original object followed by the creation of a new object. As a result, AF.1 receives:

  • A delete notification for the original object
  • A create notification for the new object

AF.1 therefore treats the renamed file as a new media object. Since the original media object no longer exists from AF.1's perspective, its custom metadata cannot be retained. Moving files between folders has the same effect, because a move uses the same delete-and-create mechanism.

How to avoid losing metadata

  • Avoid renaming or moving files directly on S3 with third-party tools once they are managed in AF.1.
  • Where possible, finalize file names and folder structures before media is ingested into AF.1.
  • If a rename or move is unavoidable, contact our support team first so we can advise on the impact for your workflow.

Need help?

If you cannot find what you are looking for, or if something is unclear, please reach out to our support team at support@media-anywhere.com.