- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hi Phil, {iot:thingName}
is a supported GGv2 recipe variables, but to use recipe variables in Component Configuration you need to set the Greengrass nucleus Configuration option interpolateComponentConfiguration
to true as explained here
As an alternative to a GGv2 Lambda you can also use directly the Greengras IPC SDK (python, C++, Java ) in your component code to publish/subscribe to messages as described in the AWS IoT Greengrass documentation or here in the 5.2 Subscriber Implementation section of the AWS Greengrass V2 workshop.
Hi Jan,
Thanks for the quick response. I can confirm this now works after revising the deployment and setting the aws.greengras.Nucleus configuration to merge to:
{
"interpolateComponentConfiguration": "true"
}
and redeploying my lambda component with
"pubsubTopics": {
"0": {
"topic": "plugin/config/{iot:thingName}",
"type": "IOT_CORE"
}
Why is IPC preferred over lambda's? Lambdas have a a very easy interface to set up event sources and currently my lambda runtime is nodejs14.x and the javascript SDK doesn't support IPC.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
You have a perfect valid case for using Lambdas on GGv2. Lambda on GGv2 make sense :