Triggering an AWS Lambda from the Command-Line

Featured image for sharing metadata for article

As I'm starting to get more involved with playing with AWS Lambdas, I wondered if there was a better way to test the deployed Lambda without using the AWS UI.

It turns out this is well documented by AWS, and we can use the AWS CLI, but it depends on which AWS CLI version you're using:

$ aws --version
# if version 1
$ aws lambda invoke --function-name my-function --payload '{ "key": "value" }' response.json
# if version 2
$ aws lambda invoke --function-name my-function --invocation-type RequestResponse --payload '{ "key": "value" }' --cli-binary-format raw-in-base64-out response.json

This outputs information about whether the operation was a success to stdout, and the Lambda's response to response.json.

Remember that if you're using different AWS accounts/profiles, you'll need to specify the AWS profile before you run the above command.

Written by Jamie Tanna's profile image Jamie Tanna on , and last updated on .

Content for this article is shared under the terms of the Creative Commons Attribution Non Commercial Share Alike 4.0 International, and code is shared under the Apache License 2.0.

#blogumentation #aws #command-line.

This post was filed under articles.

Interactions with this post

Interactions with this post

Below you can find the interactions that this page has had using WebMention.

Have you written a response to this post? Let me know the URL:

Do you not have a website set up with WebMention capabilities? You can use Comment Parade.