Pre-signed GetObject requests with Range header throws SignatureDoesNotMatch exception

[josiahmann]

Describe the bug

We've uploaded some large files to AWS and are trying to build a "preview" feature which will only show the first 1MB of the already uploaded file.

The AWS documentation suggests the Range header, but when that param is added a SignatureDoesNotMatch error is thrown.

Expected Behavior

I expected to get back the first 1Mb of the uploaded file.

Current Behavior

SignatureDoesNotMatch error is thrown.

Reproduction Steps

const client = new S3({region}); const command = new GetObjectCommand({ Bucket: bucket, Key: key, Range: "bytes=0-10000", }); const url = await getSignedUrl(client, command, { expiresIn: 3600 });

Code works as expected without the Range param.

Possible Solution

No response

Additional Information/Context

No response

SDK version used

3.209

Environment details (OS name and version, etc.)

Mac OS Ventura 13.4

[yenfryherrerafeliz]

Hi @josiahmann, thanks for opening this issue. The reason why you are getting this error is because the Range header is being signed but not provided when executing the request. At this time, the only option you have here is to provide the range header when actually executing the request. For example:

import {GetObjectCommand, S3Client} from "@aws-sdk/client-s3";
import {getSignedUrl} from "@aws-sdk/s3-request-presigner";

const client = new S3Client({
    region: 'us-east-2'
});
const url = await getSignedUrl(client, new GetObjectCommand({
    Bucket: process.env.TEST_REGION,
    Key: process.env.TEST_KEY,
    Range: "0-19"
}));
const response = await fetch(url, {
    method: 'GET',
    headers: {
        "range": "0-19"
    }
});

console.log(response.status)
console.log(await response.text())

Note: the range parameter works fine when doing a GetObject request without using presigned urls, because the header is injected at execution time, but when working with s3 presigned urls, the header values sometimes are include in the query string parameters, but in this case the parameter range as header is not supported by the s3 service.

I hope this helps!

Thanks!

[josiahmann]

Thank you! That is super helpful!

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.