Error in configuring S3 object storage

Hi,

I am new to s3 linode storage object please help with this error.

As we followed the linode s3 configuration document and tried to configure s3 objects in our ubuntu on premises server( physical server) but it throws error like below.

root@Ubuntu-1604-xenial-64-minimal ~ # s3cmd --configure

Enter new values or accept defaults in brackets with Enter.
Refer to user manual for detailed description of all options.

Access key and Secret key are your identifiers for Amazon S3. Leave them empty for using the env variables.
Access Key: **REDACTED**
Secret Key: **REDACTED**
Default Region [US]: NJ

Encryption password is used to protect your files from reading
by unauthorized persons while in transfer to S3
Encryption password:
Path to GPG program [/usr/bin/gpg]:

When using secure HTTPS protocol all communication with Amazon S3
servers is protected from 3rd party eavesdropping. This method is
slower than plain HTTP, and can only be proxied with Python 2.7 or newer
Use HTTPS protocol [Yes]:

On some networks all internet access must go through a HTTP proxy.
Try setting it here if you can't connect to S3 directly
HTTP Proxy server name:

New settings:
Access Key: **REDACTED**
Secret Key: **REDACTED**
Default Region: NJ
Encryption password:
Path to GPG program: /usr/bin/gpg
Use HTTPS protocol: True
HTTP Proxy server name:
HTTP Proxy server port: 0

Test access with supplied credentials? [Y/n] y
Please wait, attempting to list all buckets…
ERROR: Test failed: 403 (InvalidAccessKeyId): The AWS Access Key Id you provided does not exist in our records.

while executing s3cmd command it is redirecting to aws error instead of linode

listing you the error below for your reference .

root@Ubuntu-1604-xenial-64-minimal ~ # s3cmd ls
ERROR: S3 error: 403 (InvalidAccessKeyId): The AWS Access Key Id you provided does not exist in our records.
root@Ubuntu-1604-xenial-64-minimal ~ # s3cmd ls s3://classroom
ERROR: S3 error: 403 (InvalidAccessKeyId): The AWS Access Key Id you provided does not exist in our records.

Is there any specific configuration need to be implemented on the server (physical server) ?