S3 PUT Presigned URL with metadata encoded as query params

[xstex]

Describe the Feature

with v1 it was possible to create an S3 presigned URL having metadata encoded in query params.
I can't find this option on V2, so metadata can be set only through http headers (which I would avoid, since it puts more logic on the client side of my architecture)

Proposed Solution

I quickly checked the code, it seems that right now metadata is hardcoded as header as specified in PutObjectRequest:
METADATA_FIELD has MarshallLocation.HEADER (instead of QUERY_PARAM)

• I may be able to implement this feature request

Your Environment

• AWS Java SDK version used: v2.15.42
• JDK version used: 1.8
• Operating System and version: any

[debora-ito]

@xstex You can use AwsRequestOverrideConfiguration to add query params to the PutObjectRequest:

AwsRequestOverrideConfiguration override = AwsRequestOverrideConfiguration.builder()
        .putRawQueryParameter("x-amz-acl", "private")
        .build();

PutObjectRequest putObjectRequest = PutObjectRequest.builder()
        .bucket(BUCKET)
        .key(KEY)
        .overrideConfiguration(override)
        .build();

PutObjectPresignRequest request = PutObjectPresignRequest.builder()
        .signatureDuration(Duration.ofMinutes(5))
        .putObjectRequest(putObjectRequest)
        .build();

[xstex]

A little hidden, but doable. Thanks!

[debora-ito]

I'll work to add this example to our docs, you're not the first person to ask about this.

[ddierickx]

@debora-ito , thanks for your code sample. This works but I noticed something which might be an issue (or just my misunderstanding).

Using the SDK v2 and the example code, it is not allowed to change the added metadata, so using the example, modifying the URL to x-amz-acl=public is rejected by S3 (403).

But, when I append the same query parameter to the URL, resulting in x-amz-acl=private&x-amz-acl=public, the request will succeed and the acl metadata property will hold the concatenated value private,public. It appears only the first query parameter value is part of the signature and subsequent values are not?

Is there some way in the SDK to prevent repeating signed query parameters?

[debora-ito]

@ddierickx generally speaking, request headers and query params with the same name and different values are valid. So no, the SDK does not prevent it.