How AirFrame.One stays in sync with your S3 bucket
AirFrame.One (AF.1) is designed to work on top of your existing S3 storage without ever taking ownership of it. This article explains how the platform stays in sync with your bucket and what that means for your daily workflow.
Initial indexing
When your S3 bucket is first connected, AF.1 indexes it and captures the original folder structure and filenames exactly as they exist in S3. This baseline index mirrors your existing layout and naming conventions; nothing is changed on the storage side.
Staying in sync
After the initial index, AF.1 operates in an observe mode. Any change on S3, such as new files, deletions or object updates made with your own tools, triggers a storage change notification to the AF.1 backend. AF.1 updates its internal state based on these notifications, without altering the underlying S3 data.
In practice this means:
- Files uploaded with your own tools appear in AF.1 shortly after the upload has fully completed and the notification has been processed
- Files deleted on S3 disappear from AF.1
- AF.1 never modifies, replicates or restructures folders or objects in your bucket
One important caveat: renaming files directly on S3
S3 processes a rename or move as a delete of the original object followed by the creation of a new object. AF.1 therefore sees a deleted file and a new file, and any custom metadata managed in AF.1 for the original file is permanently lost. See the article "Renaming files directly in S3 removes AF.1 metadata" for details.
Questions? Contact our support team at support@media-anywhere.com.