api error InvalidSignatureException: Credential should be scoped to a valid region, not ''. " about s3-upload-proxy HOT 8 CLOSED

😍😍😍😍😍😍 THANK YOU SO MUCH!!!!!!!!!! IT WORKS!!!!!!!

from s3-upload-proxy.

Nice! I'll close this, but feel free to open new issues if you run into other issues.

from s3-upload-proxy.

Hmm it looks like we're not detecting the region from the config file. I'll push a fix soon.

In the meantime, can you try setting the environment variable AWS_REGION?

from s3-upload-proxy.

Actualyl nevermind I see that you have that environment variable set 🤔

from s3-upload-proxy.

The issue is specifically for doing a PUT to the container. The full message (with the personal info removed) is

INFO[0000] listening on [::]:8080 ERRO[0004] failed to upload file bucket={my bucket name} contentType= error="operation error MediaStore Data: PutObject, https response error StatusCode: 403, RequestID: {ID}, api error InvalidSignatureException: Credential should be scoped to a valid region, not ''. " objectKey=live_video_init.m4s

from s3-upload-proxy.

When you export your environment variable for the region, do you use single quotes, double quotes, or no quotes? I feel like I have tried all combinations with no success, but it's worth to double check.

from s3-upload-proxy.

When you export your environment variable for the region, do you use single quotes, double quotes, or no quotes? I feel like I have tried all combinations with no success, but it's worth to double check.

Hmm the shell should take either. I'll give it a shot later today.

from s3-upload-proxy.

@CaitlinOCallaghan can you try with latest master? Here's my test:

env AWS_REGION=us-west-2 BUCKET_NAME=franciscotest UPLOAD_DRIVER=mediastore HTTP_PORT=8080 ./s3-upload-proxy

Then from another terminal:

％ curl -X POST --data-binary file1.ts localhost:8080/file/file1.ts
OK

I gave up on aws-sdk-go-v2, tired of being an early adopter of that lol

from s3-upload-proxy.