Azcopy treats an S3 presigned File URL as folder and fails to copy

[yovelcohen]

Which version of the AzCopy was used?

10.23.0

Which platform are you using? (ex: Windows, Mac, Linux)

Mac/Linux

What command did you run?

azcopy copy "https://my-bucket.s3.us-east-1.amazonaws.com/syncheck-api-test-data/demodemo/Innocents-2-214.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=<SOMETOKEN>/20250803/us-east-1/s3/aws4_request&X-Amz-Date=20250803T062640Z&X-Amz-Expires=432000&X-Amz-SignedHeaders=host&X-Amz-Signature==<SIGNATURE>" "https://myblobaccountname.blob.core.windows.net/projects/688f1ebbafd5c5e121be94c5/688f1ebcafd5c5e121be94c6/video/video.mp4?se=2025-08-03T11:34:43Z&sp=racwdytme&sv=2025-07-05&sr=b&sig=<SIG>"

What problem was encountered?

Trying to copy a file (video) from an S3 presigned URL to azure storage using sas signed url of the target path.
Azcopy shows the following:
INFO: Scanning...

failed to perform copy command due to error: failed to initialize enumerator: cannot use directory as source without --recursive or a trailing wildcard (/*)

so for some reason, it treats the s3 presigned URL as a folder.
when I tried uploading a local file to the same geneerated sas signed url it worked fine, So the problem must be with the s3 presigned url.

[dphulkar-msft]

Currently, AzCopy cannot follow such redirects when fetching an object’s details. If this check fails, AzCopy assumes that the source path refers to a folder rather than a single file, which leads to the observed error.

To resolve this, please ensure that the pre-signed URL points directly to the file’s current location without requiring a redirect. You may need to regenerate the pre-signed URL from the correct bucket/region or verify that it is valid and up to date.

[gapra-msft]

Closing as the issue has been addressed.