
Jin
Thanks Tom, I'll check that out. My use case is that Im looking to give s3 bucket access to several members of a startup team some of whom may not be technical at all. I would like them to be able to login easily with their own permissioned access key and be able to access some files periodically while in the field. I thought s3drive could be that interface for them since it is available on all platforms and mobile as well. I guess I am confused about the current intended use case scenario for the app, where the login vs access key login are completely different profiles. If you could, please help me understand
I know it may be little confusing, but that's because we support multiple platforms, use-cases and user bases.
In principle, S3Drive connects directly to S3 endpoint (we call it profile) which is identified and authorized by the couple details (Key ID, secret, gateway, bucket name, region etc.). These details are something we don't manage, can't access nor store on our servers. Our software makes a connection to these details and it's up to the user to configure S3Drive so it knows where to connect.
To the best extent we make some guesses (e.g. we allow user to select existing buckets) or we auto-detect region, but still at the very minimum Key ID, secret and S3 provider name/gateway would be required.
Some of the app features are behind the paywall (that's how we can support development of S3Drive). On mobile you can buy such features through in-app purchase. Since there is no single unified payment mechanism for all platforms we've built one, so you can buy "all-platforms" package on our website. These are assigned to an e-mail/password account that we manage which is used by S3Drive to determine if you can use paid features (in the future account may be used by couple other features, e.g. online sync between devices, but let's not complicate it for now).
Additionally when you login using e-mail/password managed by us, you can access test 10GB+ account to test the app's functionality. Behind the scenes it's S3 credentials, but we generate and supply them for you based on your e-mail/password.
In the future we will be providing managed accounts (e.g. 100GB, 500GB, 2TB etc.), which will be expansion of our current model.
We aim to remain 100% S3 compatible and allow user to connect to external S3 endpoint (they may buy it from some S3 cloud/provider or they even might host S3 on their own using MinIO, SeaweedFS, Garage, OpenStack Swift, Ceph etc.)
I hope that helps you to understand how it works and why we support different account types.
... (edited)