Golang aws sdk v2 cannot upload to supabase storage

[hmhuan]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

I got issue while using golang aws sdk v2 (github.com/aws/aws-sdk-go-v2) to integrate with supabase storage. The document said I should check again the error SignatureDoesNotMatch but I set access key id / access secret key / region that are all correct

operation error S3: PutObject, https response error StatusCode: 403, RequestID: , HostID: , api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Go to '…'
2. Click on '…'
3. Scroll down to '…'
4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• Version of Go go 1.22.0

Additional context

Add any other context about the problem here.

[hmhuan]

I try to use Golang aws sdk v1, and I could upload object normally

[encima]

Hi there, thanks for opening. We cannot guarantee compatibility across all SDKs and libraries that support S3, thanks for reporting that v1 does work and that v2 does not!

For now, I would suggest using v1 if possible!

[mercuryyy]

@encima the issue is livekit pushed a mandatory change to v2 and so have others lately and we can not revert back to v1

#569

Can your team possibly take a look and see if this can be updated to support v2 ?

[fenos]

Hello the issue seems related to the new go SDK, I'll open an issue on their end and see what they think.

For now a workaround that seem to work, is to remove the DisableAcceptEncodingGzip middleware which is on by default in the new SDK

func removeDisableGzip() func(*middleware.Stack) error {
	return func(stack *middleware.Stack) error {
		_, err := stack.Finalize.Remove("DisableAcceptEncodingGzip")
		return err
	}
}

func main() {
	ctx := context.Background()

	endpoint := "https://tenant.supabase.co/storage/v1/s3"
	accessKeyId := ""
	secretAccessKey := ""
	region := "ap-southeast-1"

	sdkConfig := aws.Config{
		Region:       region,
		BaseEndpoint: &endpoint,
		Credentials:  credentials.NewStaticCredentialsProvider(accessKeyId, secretAccessKey, ""),
		APIOptions:  []func(*middleware.Stack) error{removeDisableGzip()},
	}

	s3Client := s3.NewFromConfig(sdkConfig)
	
	result, err := s3Client.ListBuckets(ctx, &s3.ListBucketsInput{})
}

[fenos]

Related aws/aws-sdk-go-v2#2848

[hmhuan]

Thanks for your sharing

[frostbyte73]

I'm hesitant to use the workaround, since we don't know which provider(s) our end users are using or whether that would break compatibility with those. V1 is also deprecated and we started seeing other issues with it, so staying on it isn't really an option

https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-go-v1-on-july-31-2025/

[ramikalai]

Would be great to get support for V2. Livekit uses this and therefore is now not compatible with Supabase storage. I'm sure lots of other services will be migrating and this will become more of a compatibility issue.

[SwarmStorm]

Confirmed on my end with Supabase as well, and am getting the same problem

[pi0]

Hi there. We recently introduced s3 driver for unstorage (used by Nuxt, Nitro and more frameworks!) and was curious if we can support/document Supabase out of the box.

I ran our tests against a superbase sandbox and hit this issue. (implementation uses aws4fetch).

[a29paul]

Getting the same issue when using with Livekit. Have to now explore an alternative solution, but would be great to have this fixed. Goal of using Supabase for me is that I don't need to use a bunch of other services, so if we can fix this issue, I'd be able to consolidate which would be awesome.