maintaining a live WebSocket connection in AWS Lambda for two-way communication

Question

Hello,

I hope you are all doing well. Currently, I am working with the Amazon Connect Chat API to build a Facebook connector. The purpose is to receive messages from Facebook on behalf of our agents. The process involves calling the CreateParticipantConnection API, which returns a WebSocket URL. Subsequently, I create a WebSocket connection using the "ws" module in Node.js.

However, there is an issue with the Lambda execution. After calling the APIs and establishing the WebSocket connection, the Lambda execution completes, and the WebSocket connection is closed. To facilitate two-way communication, I need to keep the WebSocket URL live.

I would like to know if this approach is correct for the task at hand. If it is, I need guidance on how to maintain a live WebSocket connection in the Lambda environment for seamless two-way communication.

Any assistance and advice on this matter would be greatly appreciated.

Thank you,

Brettski · Accepted Answer

Given the nature of Lambda - mostly that functions have a maximum runtime of 15 minutes - I'd suggest that it isn't the right service for what you're trying to do.

Instead, I'd suggest looking at [Fargate](https://aws.amazon.com/fargate/) for this instead.

maintaining a live WebSocket connection in AWS Lambda for two-way communication

Add your answer

Relevant content