S3Drive - Sharing v1 objects detected

Hey looking for some pointers on how to setup a sharing link. When I do it using none of the check boxes I get this error "exception: v1 objects detected (null) please migrate them to V2. I have the v2 option enabled in my client. I'm using I drive

This message tells that at least one of the objects that you've selected is encrypted using V1 cipher, which doesn't support Secure sharing. Enabling V2 cipher affects only objects uploaded after enabling that option, but doesn't automatically migrate the existing ones. These are already "encrypted" and materialized using V1 cipher. In order for share to work in your case. We would need to fallback to insecure V1 sharing for all objects (even those encrypted with V2), but we didn't want to mix V1 "insecure" approach when V2 mode is selected. In such case in order to share these objects you would either need to migrate them to V2 (reupload) or disable V2 mode temporarily, which will use insecure V1 approach for sharing. In the future we may provide additional tools to ease migration from V1 to V2. (edited)

It would be great if a tool existed for it as I have a few TBs that would need to be reuploaded

Objects need to be re-uploaded no matter what. The whole content needs to be encrypted using different encryption key (generated from your master key), question is whether this can be done "in-place" (without help of additional bucket or storage) If you use "paid" S3, the "easiest" way at the moment, might be creating new bucket and then migrating data to it. You could do that from In such case you would configure it in S3Drive, enable encryption key and enable V2 cipher. You would then use "Sync" tool, select existing bucket as a source and new bucket as a destination. This would migrate all your objects from old bucket to new one. Old bucket could then be deleted. If you would like to keep existing bucket this approach would create one more unnecessary migration, because first one would "Sync" it to intermediary one (as in the above example), then second migration would copy these objects back. If you have multiple TB, be careful for any "egress" charges that your provider might bill. Some of them give enough allowance, so it might be free though. We've tested the: "in-place" migration using Rclone, but that proved to be challenging to get right with no data loss risk. We hope to make further progress on that in the short-future. Please be aware that current V2 cipher might slightly diverge in the future, as it wasn't yet merged in to official Rclone release: https://github.com/rclone/rclone/issues/7192 The risk is that additional migration might be required in order to stay 100% compatible with Rclone. S3Drive will keep supporting (and provide migration path as a result) V2 cipher (in a current form) for as long as we need to. (edited)

Thank you for all this information, it would obviously be great if it could be in place but i understand that it cant be because of how the encryption is applied. Dont have any current plans to use anything other than S3Drive so i should be good but still great to know.