Amazon SQS Connector Release Notes - Mule 4
Support Category: Select
Anypoint Connector for Amazon SQS (SQS Connector) provides an easy way to interface with the Amazon SQS API, allowing users to manage SQS queueing services without having to interact with the API directly.
Starting with SQS Connector v.4.0.0, the connector is licensed commercially with Anypoint Platform in the Select support category. Prior versions remain freely available to the community.
Guide: Amazon SQS Connector
Reference: Amazon SQS Connector Reference
5.11.11
September 29, 2023
Compatibility
Software | Version |
---|---|
Mule |
4.3.0 and later |
Anypoint Studio |
7.1 and later |
Amazon SQS REST API |
v2 |
Fixed Issues
Issue Resolution | ID |
---|---|
The Jackson library is upgraded from version 2.15.0 to 2.15.2. |
W-13844865 |
The |
W-13844865 |
The Improper Certificate Validation security vulnerability in the Netty Handler 4.1.94.Final component is fixed. |
W-13844851. |
5.11.10
5.11.7
5.11.4
5.11.3
5.9.0
January 14, 2021
Compatibility
Application/Service | Version |
---|---|
Mule |
4.1 and later |
AWS SDK for Java |
1.11.816 |
OpenJDK |
8 and 11 |
Features
-
Added the Default Wait time and Wait time fields, which enable you to a set a polling wait time for the Read operation and Receive messages source. This change enables you to use long polling, which is now enabled by default.
-
Added the Number of consuming threads field to the Receive messages source, which enables you to set the number of polling threads.
-
The Receive messages source now behaves like a standard polling source with start delay and polling frequency parameters. (SE-18866)
5.6.1
July 28, 2020
Fixed Issues
-
If you did not specify a value for the`Test Queue Arn` field when using the
Test Connection
functionality, the test connection failed and an error displayed in the console when the associated operation was invoked". (CONN-6570)
Now, you still must specify a value for theTest Queue Arn
field when you test the connection. However, if you don’t specify this value, the console displays a warning instead of an error when the associated operation is invoked, and the connection validation is not performed. -
Some of the operations did not take into account the default global queue URL in the configuration. This is now fixed, and you can use the default global queue URL for all the operations.
5.6.0
July 8, 2020
Features
-
The connector now supports running on all cluster nodes by default. This behavior was present in version 5.4.3, but it was accidentally removed in version 5.5.0. For this reason, version 5.5.0 is deprecated. (SE-16536)
For information about how to run on the primary node only, see Upgrade to Version 5.6.