Skip to main content

Migration guide

0.4.0​

Intro​

In this version we fix compatibility with the Amazon SNS/SQS Extended Client Library. The bug was that when uploading content to S3, the JSON format of the message sent to the broker was incompatible with the Amazon's Extended Client.

  • Legacy format
{"s3BucketName": "bucket", "s3Key": "key"}
  • Correct format
["software.amazon.payloadoffloading.PayloadS3Pointer", {"s3BucketName": "bucket", "s3Key": "key"}]

How to migrate​

  1. Deploy the new version of the library in all consumers (replace usingS3Proxy with usingS3ProxyForBigPayload). The new consumer is compatible with both formats.
  2. Deploy the new version of the library in all producers (replace usingS3Proxy with usingS3ProxyForBigPayload). The new producer will send the message in the correct format.
  3. If you are having scenario where an application is both consumer and producer, then for consuming follow point 1 and for producing use firstly usingS3ProxyLegacyEncoding and then in the next release migrate to usingS3ProxyForBigPayload