NEW FEATURE : S3 Protocol Access

[UbyOne]

You already enabled the connection to "GoogleDrive" and hey men, it is really great - many thanks!
Do you plan to connect S3 CloudService (S3 Protocol) too?

[UbyOne]

news on S3 connector?

[xCSxXenon]

None

[John1234]

Hi @UbyOne

Try this free cloud drive mounting program. It will let you mount S3 cloud so you can use it with FFS.

https://www.airlivedrive.com/en/

[UbyOne]

HI @John1234
thx for your reply!
I already found a similiar product:
https://www.callback.com/s3drive
but I should admit your suggestion is better!
Anyway unfortunately it doesnt solve the problem ...
At this point I think it is a limitation in S3 resources/protocol; I try to explain you.

As TestCase I use 2 existing files in my local directory, they are NOT pesent in S3 (mapped as a drive):

File DateCreat DateMod
aaa.txt 08/04/2024 16:17 13/02/2025 18:00
bbb.txt 08/04/2024 16:18 13/02/2025 17:55
(sorry no image: I didnt manage to add it ...)

FFS execution:
correct: local ->+ s3

now in s3:
aaa.txt 13/02/2025 18:28 13/02/2025 18:28
bbb.txt 13/02/2025 18:28 13/02/2025 17:28

you can see a new timeStamp is added both as "created" as "modified".

I execute again FFS:
wrong: local <- s3

that is because the "date modified" s3 is newer than "date modified" local.

with "normal" storage (as local directories) that doesnt happen, so I strat to think is something in s3 protocol ...

what do you think?

[Plerry]

So, S3 or the protocol the tool you use to mount S3 does not support retaining dates.

If you only need to sync local => S3, you could use the Update sync variant, instead of the Mirror variant.
If you also need to sync local <= S3, then you need to find another method.