Repository navigation
Upgrade internal S3 library #2315
Description
Activity
Is this something still possible with Nextcloud 11? @rullzer @icewind1991
Doubt it. 12 at earliest. (aka early next year)
I wouldn't risk doing that for 11. But makes sense to do it early in the 12 cycle.
Because this is blockig S3 for AWS in Frankfurt I think this is important 😁😅
Is v2 (the current implemenetation) still supported and "secure" if we are talking about authentification ;)
Has the AWS PHP SDK changed that significantly over this time period? Or is this something that someone with only basic understanding of nexcloud app structuring can pick up?
Updated the sdk in #4410
Please spend some time testing the various s3 integrations (not with production data ofc)
Reacted by Nathan SmithOut of scope for 12 -> move to 13
MEH. Was hoping I could move my files into S3 now.
Any timeline for 13?Any timeline for 13?
~5-6 months after 12 I would say roughly.
#4410 should be ready for review.
Any help testing the changes would be greatly appreciated (and helps make sure they actually get merged 😄 )
one remark, even if maybe this is already present: it would be nice, at least in some future, that you could use AWS server side encryption for S3 objects as well. is that being done / considered or should I create another ticket?
ref: http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html
Fixed with #4410
Reacted by Nathan Smith
#60 is closed now, but the internal S3 lib is too old to support all AWS regions because of v2 vs. v4 authentication mechanisms.
So please upgrade the internal S3 connection lib to enable all regions (e.g. Frankfurt).
(ref: #768 (comment))