[RESOLVED] External Account Issue: 403 - the difference between the request time and the current time is too large.

[#1]

I have some issues with the configuration of an external account with Amazon S3.

At the moment I have this errors in upload and download:

- CRL-290162 S3 upload request, received 403 http response code from AWS.

- CRL-290151 HTTP response received from S3 403. The difference between the request time and the current time is too large.

The actual configuration:

What could be the problem?

I think it could be the istance time synch (the istance has a differente time zone than our here in Europe) but I don’t know how solve it. Can someone help me?

Thanks

Miriam

EDIT FOR ALL THOSE WHO HAD THE SAME PROBLEM:
the issue was solved restarting the time sync daemon of the istance.

[mfiorenti]

Hello @mfiorenti ,

403 error means you do not have access to either read/write or whatever action your are performing to the s3 bucket.

The solution will be to check the access to the s3 path or the credentials.
Here are few link that can help you in the troubleshooting:
https://aws.amazon.com/premiumsupport/knowledge-center/s3-403-forbidden-error/
https://aws.amazon.com/premiumsupport/knowledge-center/s3-troubleshoot-403/

Thanks,
Manoj

[mfiorenti]

Hi @manojk62306941,

I think it's really strange because I have all the permissions. 

[mfiorenti]

Hi @manojk62306941,

the issue was solved restarting the time sync daemon of the istance.

[manojk62306941]

Can you check the path URL of the s3 bucket? If the path and Access keys you are using are correct then you should not get not authorized error.

[mfiorenti]

Hi @mfiorenti,

I believe you are using transfer file activity to upload/download files. Did you try change the timezone under execution options of transfer file activity? and see how that's doing.

Thanks!

SK

[mfiorenti]

Hi @SatheeskannaK and thanks a lot for the reply!
I've already tested several time options, but sadly the error remains the same.

[mfiorenti]

Hi @SatheeskannaK, the issue was solved restarting the time sync daemon of the istance.