Why i get "The Access Key Id you provided does not exist in our records." error?

Developer Discussions troubleshooting
1

I am trying to connect to your service. I use a laravel for this. In the ENV file, I set global variables and indicate the keys received in the account. I am getting error:

Aws\S3\Exception\S3Exception with message 'Error executing "ListObjects" on "https://demo-bucket.gateway.eu1.storjshare.io/?prefix=&delimiter=%2F&encoding-type=url"; AWS HTTP error: Client error: `GET https://demo-bucket.gateway.eu1.storjshare.io/?prefix=&delimiter=%2F&encoding-type=url` resulted in a `403 Forbidden` response:
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InvalidAccessKeyId</Code><Message>The Access Key Id you provided doe (truncated...)
 InvalidAccessKeyId (client): The Access Key Id you provided does not exist in our records. - <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InvalidAccessKeyId</Code><Message>The Access Key Id you provided does not exist in our records.</Message><BucketName>demo-bucket</BucketName><Resource>/</Resource><RequestId>16BB5588641A54F9</RequestId><HostId></HostId></Error>'

What am I doing wrong ?

2

Hello @heklpme ,
Welcome to the forum!

Please, configure AWS CLI first to check that your keys actually working: Quickstart - AWS CLI and Hosted Gateway MT - Storj DCS

When you confirm that they are valid keys and needed endpoint, then configure your app.

Please could you share, what parameters you have specified for the integration?

3

I use this credentials:

AWS_KEY=******mra
AWS_SECRET=****c6pc
AWS_REGION=
AWS_BUCKET=demo-bucket
AWS_URL= AWS_ENDPOINT=https://gateway.eu1.storjshare.io

4

It will not work this way. Please, specify in the configuration of your laravel to do not use a Virtual addressing style. You need to use a path-style mode or even better - the “auto”.

Perhaps it would be better if you could use a native integration GitHub - storj-thirdparty/uplink-php: Uplink library bindings for PHP instead of s3-compatible.

5

Actually I asked devs to check. The virtual style addressing still works.
Please, check your keys with AWS CLI to make sure they are valid.