Regarding URL length of Presigned URL of S3 object.

[vishalghanwat321]

Hi Team,

If we generate pre-signed URL using access_key and secret_key then url length is shorten and easy to process.
If we generate pre-signed URL using role based Authentification then url do add "X-Amz-Security-Token" variable in generated URL due to which URL length gets increased.

Do we have any tool provided by AWS to shorten this URL as most of the systems are not able to process this longer length URL.

Kindly suggest an approach how to shorten this length of URL.

[bhoradc]

Hello @vishalghanwat321,

At this time, we don't have a tool as such which is readily available for shortening the S3 generated pre-signed URL. But you may want to refer to this AWS blog post to build a private URL shortener to shorten the S3 Presigned URL.

Please take a look at this post and let me know if this helps.

Regards,
Chaitanya

[tmccombs]

A traditional url shortener doesn't work, because it just redirects to the long url, and then the client complains that the url is too long.

I suppose you could work around it with a full proxy, but then you have to sacrifice a lot of the benefits of s3, and you might as well not use presigned urls at all, and just have presigned/unique urls specific to your proxy (which you kind of have to do anyway).

The inconsistency is also pretty bad.

Consider this scenario:

You test using presigned urls in development using access-key based authentication. The urls are a reasonable length so you ship using it out to a staging environment, or maybe even production.

Now it is running on ec2 and uses token based authentication, and suddenly X-Amz-Security-Token is, by itself approximately 1500 characters. Add on the hostname, path, maybe some query parameters, and oops now you're over the typical 2024 limit on the length of a url.

How is it acceptable for the token to be that long?

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.