Amazon authentication change?

[lmsstaff]

I'm stumped, but wondering if AWS made a token authentication change recently?  

All of my data pulls using the URL provided from the API are failing for a "No AWSAccessKey was presented" error.  These are from a cURL call on the command line, for example (with params broken out for reading):

https://data-access-platform-output-prod-iad.s3.amazonaws.com/output/rootAccountId%3DtrjT6jjlB7plKd8...

?X-Amz-Security-Token={{token}}

&X-Amz-Algorithm=AWS4-HMAC-SHA256

&X-Amz-Date=20230626T155559Z

&X-Amz-SignedHeaders=host

&X-Amz-Expires=3600

&X-Amz-Credential={{cred}}

&X-Amz-Signature={{sig}}

This URL is of course now expired but if I paste this URL into a browser it works, from "curl --location GET {url}", I get this error:

<?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>AccessDenied</Code>
<Message>No AWSAccessKey was presented.</Message>
<RequestId>ZB6DEMQY9Z7HZCCC</RequestId>
<HostId>IrFltsFPr8fQz1N+32EiLVL5jOHdWyaVJzEU/BabsVOCa5QG7I2xEGyWZt0nCLHpq8gJsMjQLBKQTWdGrOZRJ+FAU0RbIKXpxevXwfAxBNc=</HostId>
</Error>

This was not happening a couple weeks ago.  The DAP works fine but for my purposes at present, I need it working in cURL.  I'm missing something. Any thoughts anyone?

Thanks.  Appreciate the help.

[jdh132]

Besides to make sure you put the {url} within quotes when using curl. If it works from a browser it should work from curl.

[IanGoh · Accepted solution]

Just tried, this worked for me

curl "dap-object-url" --output some.gz

I had to double quote the dap-object-url

This was fine too.

curl --location "dap-object-url" --output some.gz

[lmsstaff]

Thanks dudes.  I'll try it again.  Maybe just bad timing?  I don't know.