Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

ACS file transfer with Amazon S3

rafikb63477949
Level 2
Level 2

Hello

I am trying to do a file transfer using S3 protocol,, but i am receiving this error message:

CRL-290151 HTTP response received from S3 400

Which bucket policy should I use? Please advise considering this error log above.

Thank you

1 Accepted Solution
rafikb63477949
Correct answer by
Level 2
Level 2
11 Replies
Adhiyan
Employee
Employee

Hi ,

Can you please share the screenshot of the external account for S3 . Ideally you just need to give the Server address like this :

https://aam-outbound.s3.amazonaws.com/<org_name>

and then providing the Access key and Secret key would do the job

Regards,
Adhiyan

rafikb63477949
Correct answer by
Level 2
Level 2
florentlb
Level 10
Level 10

Hi,

Were you able to get this to work? Here are the recommendations for S3 external accounts: Adobe Campaign Help | External accounts

Florent

euniceh49251924
Level 1
Level 1

Hi

Could you please tell how do you solve this problem?

I have set the external account as your attachment, but still got the error "CRL-290151 HTTP response received from S3 400" in using transfer file.

ramon_bisswanger
Employee
Employee

Error 400 at S3 mostly referes to using the wrong region when connecting to a bucket.

Can you verify if you set that correctly?

euniceh49251924
Level 1
Level 1

Could you share your setting on transfer file?

This is my log messages.

1758239_pastedImage_0.png

DavidKangni
Community Advisor
Community Advisor

Your config should be like

external_accounts_2

chan2111
Level 4
Level 4

This is the same issue I am facing "CRL-290151 HTTP response received from S3 0". Any update on this request.

chan2111
Level 4
Level 4

I have added the right region and it fixed the issue.

LeonieSwart
Level 3
Level 3

I experienced an Access Denied 403 error from S3 after a build upgrade to V7 9032.

The issue was resolved by changing S3 in the server url to s3.