petitout

@ovk, not getting your order here, why 'signing time' before 'message digest' ?

thanks @ovk, My question was more how attributes are compared for sorting purpose ? it is only about the size of the attribute ?

Same issue, that's annoying

this example is very good : https://flowerinthenight.com/blog/2021/04/30/authenticate-aws-sdk-golang-v2

```ctx := context.Background() assumecnf, _ := config.LoadDefaultConfig(...) stsclient := sts.NewFromConfig(assumecnf) cnf, _ := config.LoadDefaultConfig( ctx, config.WithRegion("{aws-region}"), config.WithCredentialsProvider(aws.NewCredentialsCache( stscredsv2.NewAssumeRoleProvider( stsclient, "{rolearn-to-assume}", )), ), ) client := s3.NewFromConfig(cnf) res, _ := client.GetObject(ctx,...

@skmcgrail, with the golang sdk, It is currently not possible to use Amazon S3 Object Integrity Features with presigned URL because of this open bug : https://github.com/aws/aws-sdk-go-v2/issues/1566

Any status on this feature @KaibaLopez ? In need for this one too. The use case is that we don't want to generate a presigned URL for each part but...

Actually @KaibaLopez and @JinnyYi , the partNumber is part of the signature ... So it is not possible to generate only 1 Presigned URL for all the parts

@jasdel looks like it is not possible to add "X-Amz-Content-Sha256" header this way. I always end up with a `SignatureDoesNotMatch` error while using the presigned URL (with the header). Note...

My guess is that on the server side, the server removes `X-Amz-Content-Sha256` header to compute the signature and throws a `SignatureDoesNotMatch` error. That would explain why on the client side,...