CUAN_MKT_EXEC_BOUNCE Job is failing with API error"400" InvalidAction

[Former Member]

Hi Experts,

CUAN_MKT_EXEC_BOUNCE Job is failing with API error"400" InvalidAction to collect Bounce Detail

RFC AMAZONBOUNCE Connection Test receive an HTTP response code 404, then it means set-up is correct

Bounce HTTP destination  AMAZONBOUNCE   could be opened

RFC Detai : Target Host is "sqs.us-east-1.amazonaws.com" and prefix /xxxxxxxxxxxx/MKT_EXEC_BOUNCE

AWS Regions and Endpoints - Amazon Web Services

is prefix is correct ? did anybody did Amazon bounce email setting. Do we need to maintain seperate Access-key and Secret-key

for Amazonmail and Amazon bounce.

XML Response error :

InvalidAction

The action or operation requested is invalid. Verify that the action is typed correctly.

HTTP Status Code: 400

<?xml version="1.0"?>

-<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">

-<asx:values>

<_--5CTYPE_--3DSTRING><ErrorResponse xmlns="http://webservices.amazon.com/AWSFault/2005-15-09"> <Error> <Type>Sender</Type> <Code>InvalidAction</Code> <Message>Could not find operation ReceiveMessage for version 2012-11-05</Message> </Error> <RequestId>xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx</RequestId> </ErrorResponse> </_--5CTYPE_--3DSTRING>

</asx:values>

</asx:abap>

[Former Member · Accepted solution]

Hi,

You may check the following:

• The path prefix may be incorrect.
  Typically it looks like /1234567/my_bounce_queue. It is the part of the bounce queue URL in the AMAZON SQS cockpit after the host, typically consisting of the Account ID and the name of the queue as you specified it in Amazon SQS
• You may have configured the bounce queue in the wrong AWS region.
  Check whether you configured the bounce queue in AWS region us_east-1

There is only one pair of Access/secret key needed. The pulling from the bounce queue and the sending of emails can only be done using the same Amazon account.

Best regards,

Frank

[Former Member · Accepted solution]

Thanks Frank wittig.

We also raised OSS Message Mr.Frederik Lipowsky helped us to solve the issue.

we could solve the issue. Root cause was the wrong bounce queue path in SM59.

Once again writing the AWS account information via TR AMAZON_XS helped and now, no errors appear anymore. Also a functional test with a campaign was successful.