当通过aws-sdk-go

签名URL时，签名不匹配403错误我遵循了关于此问题https://github.com/aws/aws-sdk-go/issues/467的说明，其中明确记录了如何为PUT请求创建预签名url。我们的目标是presign的URL，这样我就可以直接在浏览器安全当通过aws-sdk-go

密钥和密码上传图像是当然，我是通过SDK直接PutObject要求工作电流凭证

creds := credentials.NewStaticCredentials("key", "secret", "") 

cfg := aws.NewConfig().WithRegion("us-west-2").WithCredentials(creds) 
srv := s3.New(session.New(), cfg) 

params := &s3.PutObjectInput{ 
    Bucket: aws.String("my-bucket"), 
    Key: aws.String("/local/test/filename"), 
} 
req, _ := srv.PutObjectRequest(params) 
url, err := req.Presign(15 * time.Hour) 
if err != nil { 
    fmt.Println("error signing request", err) 
} 

fmt.Println("URL", url)

```

然后我拿那个URL并做一个卷曲请求。我得到这个回应

<?xml version="1.0" encoding="UTF-8"?> 
<Error> 
    <Code>SignatureDoesNotMatch</Code> 
    <Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message> 
    <AWSAccessKeyId>redacted</AWSAccessKeyId> 
    <StringToSign>redacted</StringToSign> 
    <SignatureProvided>redacted</SignatureProvided> 
    <StringToSignBytes>redacted</StringToSignBytes> 
    <CanonicalRequest>PUT 
/local/test/filename 
X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=redacted%2Fus-west-2%2Fs3%2F%20aws4_request&amp;X-Amz-Date=20161129T012909Z&amp;X-Amz-Expires=54000&amp;X-Amz-SignedHeaders=host 
host:redacted.s3-us-west-2.amazonaws.com 

host 
UNSIGNED-PAYLOAD</CanonicalRequest> 
    <CanonicalRequestBytes>redacted</CanonicalRequestBytes> 
    <RequestId>redacted</RequestId> 
    <HostId>redacted</HostId> 
</Error>

任何想法为什么presigned URL为我提供了一个假定不匹配的签名？同样，这些相同的凭证目前正在为我的服务器上的直接PutObject命令工作

来源

2016-11-29 Quest

我的桶策略未正确配置。我不得不交叉引用我的密钥/秘密与IAM政策，并确保它们列在政策的“主体”部分中

https://aws.amazon.com/blogs/security/iam-policies-and-bucket-policies-and-acls-oh-my-controlling-access-to-s3-resources/

来源

2016-11-29 20:09:32 Quest

当通过aws-sdk-go

回答

相关问题