Test on-demand Lambda functions - AWS IoT Greengrass

Test on-demand Lambda functions

An on-demand Lambda function is similar in functionality to a cloud-based AWS Lambda function. Multiple invocations of an on-demand Lambda function can run in parallel. An invocation of the Lambda function creates a separate container to process invocations or reuses an existing container, if resources permit. Any variables or preprocessing that are defined outside of the function handler are not retained when containers are created.

  1. On the group configuration page, choose Lambdas.

  2. For the Greengrass_HelloWorld_Counter Lambda function, choose Edit Configuration.

                            Screenshot with Lambdas and Edit Configuration
  3. Under Lambda lifecycle, choose On-demand function, and then choose Update.

                            Screenshot with the On-demand function radio button
  4. On the group configuration page, from Actions, choose Deploy.

                Screenshot of the Group page with the Deploy action 

    This deploys the group configuration to your AWS IoT Greengrass core device. For troubleshooting help, see Troubleshooting AWS IoT Greengrass.

  5. After your deployment is complete, return to the AWS IoT console home page and choose Test.

  6. Configure the following fields:

    • For Subscription topic, enter hello/world/counter.

    • For Quality of Service, choose 0.

    • For MQTT payload display, choose Display payloads as strings.


                            Screenshot of Subscriptions test page.
  7. Choose Subscribe to topic.


    You should not see any messages after you subscribe.

  8. To test the on-demand lifecycle, invoke the function by publishing a message to the hello/world/counter/trigger topic. You can use the default message.

    1. Choose Publish to topic three times quickly, within five seconds of each press of the button.

                            Screenshot showing the Publish to topic button, which must be
                                clicked rapidly three times.

      Each publish invokes the function handler and creates a container for each invocation. The invocation count is not incremented for the three times you triggered the function because each on-demand Lambda function has its own container/sandbox.

                            Screenshot showing Invocation Count fixed at 1.
    2. After approximately 30 seconds, choose Publish to topic. The invocation count should be incremented to 2. This shows that a container created from an earlier invocation is being reused, and that preprocessing variables outside of the function handler were stored.

                            Screenshot showing Invocation Count now at 2.

You should now understand the two types of Lambda functions that can run on the AWS IoT Greengrass core. The next module, Module 4, shows you how devices can interact in an AWS IoT Greengrass group.