Cloud: AWS Improves the Trigger Functions for Amazon SQS
The improved AWS feature allows users to trigger Lambda functions from an SQS queue.
The AWS team improves the trigger functions for the simple queue services and discusses how these trigger functions can be utilized across AWS accounts.
AWS users can now trigger functions from queues of other AWS accounts.
Queues can be triggered within a zone only.
The new feature added is at no extra cost to customers.
The feature requires permissions to be granted across accounts to perform successfully.
On the 30th of September, 2021, the AWS team announced the release of the new feature via their blog, allowing users to trigger functions from Amazon's Simple Queue Service (SQS) even from queues of other AWS accounts. This upgrade would only enable users to access functions from within an account.
Customers use the feature to process messages in the Amazon SQS. The Lambda function provides support to standard queues and the FIFO queues. It scans the queues and gathers the functions with events containing queue messages simultaneously.
Existing and prospective customers welcomed the initial release of this function because the function had features that improved the already existing retry logic by retaining messages that weren't successful. It also has a reduced cost of operations when compared to other workarounds.
The team at Amazon has made this function available in regions that the SQS provided by Amazon is functional. Customers would be provided with the service at the exact cost, which means that the customers would not be required to pay any extra charges to access this feature.
The function can trigger events in different accounts, but the function and the queues must exist in the same region. Customers would no longer need to replicate events sources in each account that the queue is to be used.
The feature which is easy to implement would require the customers first to appoint the Amazon SQS as the event source whenever they want to add a trigger for the Lambda function, which would be followed by users providing the resource name for their SQS queue, but the resource name can be from any account in the same region. Users would then provide grant permissions to the lambda functions to manage the queues. Finally, users would need the SQS queue to grant permission across accounts to process messages successfully.
The function has been accessible since the 30th of September, 2021, and the team is working on more features to accommodate the changing trends in cloud infrastructure daily.
Get similar news in your inbox weekly, for free
Share this news:
Documentation gives the information about projects, and it informs a contributor or user on what …