- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hi rgrandhi,
Since your question is more about the cloud lambda side I'm going to reassign this question. What rules do you have setup to trigger your cloud Lambda, Lambda 1? Are you using wildcards?
Thanks,
KR-AWS
Hi there!
No, there are no rules triggering Lambda 1, I use StepFunctions to invoke it manually (for now).
Yes, there are wildcard subscriptions involved in this in the following format.
Lambda1 (on Cloud) --> publishes to topic --> CMD/are_you_alive/<lambda's context.aws_request_id>
Lambda1 (on Cloud) --> starts to subscribe to --> RESULT/are_you_alive/<lambda's context.aws_request_id>
Lambda2 (on GG Core device) --> with a GG subscription to topic --> CMD/are_you_alive/+
Lambda2 (on GG Core device) --> publishes its response to --> RESULT/are_you_alive/<whatever aws_request_id it received from Lambda1 as a part of request body>
I repeat my problem, if it helps with clarity:
I'm getting responses from Lambda2 despite the GG Core device is down!!!!!!??
On a side note, is there a recommended way to publish/subscribe to IoT cloud messages from Lambda1 (running on Cloud). PS: I got inspiration from PubSub example from AWS GitHub (AWSIoTPythonSDK).
Appreciate your help!
cheers,
~rg
Hello -
I found the solution to my problem.
It is not an issue with Lambda or GreenGrass as I doubted earlier.
I have a global scoped variable declared in my Lambdas, so, when AWS is reusing Lambda runtime(s) between invocations, I'm getting unwanted results in its response.
Just wanted to put an end to this thread as closure :)
cheers,
rg
Contenus pertinents
- demandé il y a 3 mois
- demandé il y a 14 jours
- Réponse acceptéedemandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans