Error after note 2884039 implementation

[SauMaris]

We implemented SAP note "2884039 - Support Amazon SigV4" and now we cannot send emails from Amazon. Error when checking config is: Error during sending: Client compression deactivated for provider class "CL_CUAN_MKT_EXEC_EMAIL_AMZN".

Provider check does not return any errors.

Outbound HTTP destination for provider sapAmazon maintained.
Outbound HTTP destination AMAZONMAIL for provider sapAmazon could be reached.
Provider adapter class CL_CUAN_MKT_EXEC_EMAIL_AMZN for provider sapAmazon.
Bounce collection for provider sapAmazon configured.
Bounce HTTP destination AMAZONBOUNCE for provider sapAmazon could be reached.
Amazon Max.SendRate: 1; Limit24Hours: 200; SentLast24Hours: 0

Shall we roll-back or is there any documentation missing what should be done after the note is applied? Like do we need to switch off SigV4, if we use data center "eu-west-1"?

Regards,

Maris

[markus_schwingel]

Hello,

the reason for the issue is very likely that you maintained the Communication Arrangement SAP_COM_0016 in a wrong way (or, in case of OnPrem, the corresponding http destination for sending emails with Amazon). Note that the path in the http connection must be empty ! With SigV3 this didn't matter but with SigV4 this is an issue leading to an invalid signature.

Have a look at the documentation:

https://help.sap.com/viewer/0f9408e4921e4ba3bb4a7a1f75f837a7/2002.500/en-US/1fec8c7e2a8546e19c943d64...

• Scenario: SAP_COM_0016

  Path: no path

Regards,

Markus

[SauMaris]

Thanks, for your response, Markus.

Path for the AMAZONMAIL destination is empty.

We rolled-back the note for now.

[SauMaris]

We got a warning from Amazon that we have to switch to Signature v4, so we again implemented the note 2884039. And again we are getting error regarding compression.

Error is raised here

It is unclear why in compression error is raised even though we are having compression disabled in SM59.

Path prefix is empty for the RFC destination "AMAZONMAIL" as suggested in the note.

[markus_schwingel]

Actually, the note is only required in case you want to use a data center that does not support SigV3 at all, such as eu-central e.g. For eu-west-1 the note doesn't provide any benefit. Nevertheless it shouldn't have caused the issue you described.

[SauMaris]

I have a suspicion that error was actually due to missing Amazon credentials after the upgrade to the version 1909. Cannot verify now, as we rolled-back the note, but anyway seems that problem was not related to the "Client compression" as the error message said.

Thanks a lot for your response!