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

0

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,

1回答
0
承認された回答

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 for this instead.

profile pictureAWS
エキスパート
回答済み 10ヶ月前
profile picture
エキスパート
レビュー済み 10ヶ月前
profile picture
エキスパート
レビュー済み 10ヶ月前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ