2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
I was able to work around this by making the Lambda function not async and run an async submethod using asyncio.get_event_loop().run_until_complete()
Still would be nice to get confirmation / documentation that async Lambdas are not compatible with websocket APIs.
beantwortet vor 4 Jahren
0
You might consider using boto3 Lambda.Client.invoke() and calling the WebSockets API directly with an Asynchronous Event. You marshall the data yourself into the Event object and have total control over what the other side receives. Here's a paper on using invoke() and the Asynchronous Event Design Pattern in AWS Lambdas that might help you:
beantwortet vor 23 Tagen
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
Is there a better way today?