[Golang] PutObject Failing with StatusCode: 501 (NotImplemented)
Hello everyone :wave:
I hope you are having a good end to the week. Me, on the other hand, I went on an S3 scavenger hunt :sweat_smile:
For context, my production code works fine but I haven't run any deployments or dependency upgrades in a few days. Today, I was working on a feature on my local machine and after upgrading my deps (
I tried connecting to a different bucket, changing permissions etc. but with no luck – and the error message isn't very clear as to what is not implemented. However, I came across the AWS S3 Go SDK changelog for v1.73.0:
So it seems that the checksum calculation is causing errors on Tigris' side. I fixed the error by requesting the checksum be calculated only when required:
I am not sure if this is a robust solution as I haven't tested
Hope this helps :love_you_gesture:
I hope you are having a good end to the week. Me, on the other hand, I went on an S3 scavenger hunt :sweat_smile:
For context, my production code works fine but I haven't run any deployments or dependency upgrades in a few days. Today, I was working on a feature on my local machine and after upgrading my deps (
go get -u ./…go mod tidyI tried connecting to a different bucket, changing permissions etc. but with no luck – and the error message isn't very clear as to what is not implemented. However, I came across the AWS S3 Go SDK changelog for v1.73.0:
Feature: S3 client behavior is updated to always calculate a checksum by default for operations that support it (such as PutObject or UploadPart), or require it (such as DeleteObjects). The checksum algorithm used by default now becomes CRC32.
So it seems that the checksum calculation is causing errors on Tigris' side. I fixed the error by requesting the checksum be calculated only when required:
I am not sure if this is a robust solution as I haven't tested
DeleteObjectHope this helps :love_you_gesture:
Solution
Hi, you are indeed right, there are breaking changes in the newer versions of the AWS S3 SDKs.
We have captured the details in our blog post: If you've upgraded boto3 or the JavaScript S3 client in the last week, uploading files won't work. Here's how to fix it.
We are actively working on addressing this.
We have captured the details in our blog post: If you've upgraded boto3 or the JavaScript S3 client in the last week, uploading files won't work. Here's how to fix it.
We are actively working on addressing this.
If you've recently upgraded boto3 or the JavaScript S3 client, file uploads may fail due to a required Content-Length header. Downgrade boto3 to version 1.35.x and the JavaScript client to v3.728.0 to resolve this issue until Tigris releases an update for compatibility with new versions.
