pre-signed S3 putObject URLs don't allow tags

[RingOfStorms]

Is your feature request related to a problem? Please describe.
Essentially reopening this issue because it is not solved: #1313

Summary:
It is impossible to enforce Tags and their value with just a signed url. The only thing that you can do is allow a client to provide headers. This is not usable when you do not have control over the client and still want tags to be set.

Describe the solution you'd like

I'd like the S3.getSignedUrl method to allow an additional param: TagSet which matches other TagSet params throughout the API. This would result in a signed url that can have data put to it and the resulting S3 object will have the tags defined in the getSignedUrl params.

s3.getSignedUrl('putObject', {
    Bucket: bucket,
    Key: key,
    Expires: 60, // seconds
    Metadata: {
      testMetaKey: 'test meta value'
    },
    TagSet: [
      { Key: 'testTagKey1', Value: 'test1' }
    ]
  });

// PUT into signed url

const { TagSet } = s3.getObjectTagging({ Key: key, Bucket: bucket });

assert(TagSet, [{ Key: 'testTagKey1', Value: 'test1' }]) // should be true

[ashishdhingra]

Unsure if the AWS JavaScript SDK v2 (version 2.1586.0) is producing the correct PreSigned Url when executing the below code:

const AWS = require("aws-sdk");

const region = "us-east-2";
const bucketName = "testbucket-temp";
const key = "testingJSSDK.txt";
const signedUrlExpireSeconds = 60 * 5;

AWS.config.update(region);

AWS.config.getCredentials(function (err) {
    if (err) console.log(err.stack);
    // credentials not loaded
    else {
        const s3 = new AWS.S3();
        const presignedUrl = s3.getSignedUrl("putObject", {
            Bucket: bucketName,
            Key: key,
            Expires: signedUrlExpireSeconds,
            Tagging: 'sem=somethingSemantic'
        });

        console.log("Presigned URL: " + presignedUrl);
    }
});

It generates presigned URL like below:

https://testbucket-issue1880.s3.amazonaws.com/testingJSSDK.txt?AWSAccessKeyId=ASIASA6NRDFT3VRPG6JS&Expires=1711562720&Signature=j11RZvXFXGjDyyy0Jd5rBZS%2BPTg%3D&x-amz-security-token=IQoJb3JpZ2luX2VjEKr%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMSJGMEQCIE01KXmzRNlZs5TAAkh9ctqXvkMdwi1N8%2BQuUeu%2F3Se7AiBRur5%2BAj%2BUalX9PntnV%2Bv89W01hUamJXgn88x%2BzAhjBiqmAgjD%2F%2F%2F%2F%2F%2F%2F%2F%2F%2F8BEAIaDDEzOTQ4MDYwMjk4MyIM6RChlrX1Pm3CD1O0KvoBK%2Fi4aTEMteujYE5XRKI2SnOx%2F6ZRN%2FIFgFcxNKEY5HnbRe%2BF1Z%2F9ht9rJfyL1AOr2NxVO9q70v2i0Z5K2eXkx499upSEQyfZ4ZSq50BH9lhzulSPNpEcAwazkZgMl4BOZMf3u0G%2BrKkZZoVjbWvJdkKcgmmQK87sihv1UPCs1JIQ1xF1XWllGbZXygNzG0%2FN83P9UbBoPeSAefos2tqwiEnoykMQ%2FImI%2B4fpSgPgXhb05%2F9a2RI7AOMCyUH3LOXFq2JX5dL2W2E0bTqfJVhkh7R14nDd4bvYJXH5BcMbXH1MRXPPaaK3efRUL2j6ac6npEpXck%2Fdxgd8VzCrvZGwBjqeASoJlBD7bwm%2FikDwEjRIIcqown5R48KuMKGxmF4cHMMkFU2VLlZaf4GRzN3F7h%2BLfYLtTBHDUrBkUzD16k0haDBFFmHItxhXzx2Qe753lUjloCnZF%2Fn3KcSDbnNDJIOEK8T8cOo51%2FtOqMQqqV7KM01ci91kc8tFWTnIMcr3AJZfHXOdD8JDT8LGUz2hipHFEQEc2nzFYVHbxeKoOZ60&x-amz-tagging=sem%3DsomethingSemantic

It is missing X-Amz-SignedHeaders query string parameter and instead includes x-amz-tagging query string parameter.

Using it to upload file is returning 400 Bad Request error.

Transferring it to aws\aws-sdk-js repo for review.

Also refer aws/aws-sdk-net#1696 (comment) for guidance provided for using tags with presigned URL.

[aBurmeseDev]

Thanks for reaching out and sorry for the long wait.

During my investigation, I found out that there might be ongoing bug on service S3 side that affects across-SDKs but the expected behavior here is to include x-amz-tagging header when sending your request. It is also noted in the documentation as

.....Tagging must be provided as headers when sending a request. If you are using pre-signed URLs to upload from a browser and need to use these fields, see createPresignedPost().

Here are some resources that I found indicates the known issue on the service side:

• service/s3: presigned PutObject with Tagging set does not add tagging to object in S3 bucket. aws-sdk-ruby#2762
• Aws::S3::PresignedPost does not support tagging field aws-sdk-ruby#2919

Let us know if issue persists with x-amz-tagging as header.

[github-actions]

This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.