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%3DtrjT6jjlB7plKd8OZPNsvTNgE3xD51K7ykuNWBrW/queryId%3Da675763c-c1b2-4ad1-8156-822981e73851/part-00000-519f1770-9e08-497e-b63d-4fa4e31ec6aa-c000.json.gz
?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"?>
AccessDenied
No AWSAccessKey was presented.
ZB6DEMQY9Z7HZCCC
IrFltsFPr8fQz1N+32EiLVL5jOHdWyaVJzEU/BabsVOCa5QG7I2xEGyWZt0nCLHpq8gJsMjQLBKQTWdGrOZRJ+FAU0RbIKXpxevXwfAxBNc=
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.
