-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make s3 aiori that uses the official s3 c api #442
Comments
Sounds great, indeed! Will work on it in time. |
The library dependencies are an absolute atrocity. |
That's too bad. Should we close this or leave it on the backlog? |
I actually started to work on it: aws-s3-branch
I would be, of course, happy if someone had time to proceed - I will try to do it in Q1, as S3 is very important to me. |
I am currently very interested in this feature, and may pick up the work on it myself if nobody else is pursuing it. @JulianKunkel , I assume your branch is the place to start? |
@matthewcurry that sounds great, I didn't have the need to proceed in Q1. |
Thank you so much for your work on this, it’s greatly appreciated. I’m currently working on a project that requires running IOR on Amazon S3. I was wondering if the branch aws-s3-branch is ready for use? If so, could you please clarify which version of IOR and which backend I should compile IOR with to enable this functionality? If the branch is not functional yet, do you know which previous version of IOR and which backend might work for this use case? Currently, I am using IOR 4.4.0 with the latest libs3. While the configuration and compilation of IOR complete successfully, S3 does not appear as a valid API option. Thank you in advance for your guidance! |
Hi @candiceT233 , I haven't made any progress on this yet. The main branch still has S3 support, but only for old versions of libs3 (and its dependencies). It could be possible to get these to work by building old versions of the libraries, but I'm unsure which version you would need to use. |
It looks like both our S3 backends use libraries that are no longer being maintained. Fortunately, AWS now has an "official" C API: https://github.com/awslabs/aws-c-s3
For sustainability, we should probably migrate to that and retire out the other two flavors of S3 support at some point.
The text was updated successfully, but these errors were encountered: