AWS Lambda
Developer Guide

Step 2.3: Create the Lambda Function and Test It Manually

In this section, you do the following:

  • Create a Lambda function by uploading the deployment package.

  • Test the Lambda function by invoking it manually. Instead of creating an event source, you use sample Amazon SQS message data.

In the next section, you create an Amazon SQS queue and test the end-to-end experience.

Step 2.3.1: Create a Lambda Function (Upload the Deployment Package)

In this step, you upload the deployment package using the AWS CLI.

At the command prompt, run the following Lambda CLI create-function command using the adminuser profile. If you have not created this profile, see Set Up an AWS Account.

You need to update the command by providing the .zip file path and the execution role ARN.

$ aws lambda create-function \ --region us-east-1 \ --function-name ProcessSQSRecord \ --zip-file fileb://file-path/ \ --role role-arn \ --handler ProcessSQSRecord.handler \ --runtime runtime-value \ --profile adminuser

For more information, see CreateFunction. AWS Lambda creates the function and returns function configuration information.

Optionally, you can upload the .zip file to an Amazon S3 bucket in the same AWS region, and then specify the bucket and object name in the preceding command. You need to replace the --zip-file parameter by the --code parameter, as shown following:

--code S3Bucket=bucket-name,S3Key=zip-file-object-key

Step 2.3.2: Test the Lambda Function (Invoke Manually)

In this step, you invoke your Lambda function manually using the invoke AWS Lambda CLI command and the following sample Amazon Simple Queue Service event.

  1. Copy the following JSON into a file and save it as input.txt.

    { "Records": [ { "messageId": "c80e8021-a70a-42c7-a470-796e1186f753", "receiptHandle": "AQEBJQ+/u6NsnT5t8Q/VbVxgdUl4TMKZ5FqhksRdIQvLBhwNvADoBxYSOVeCBXdnS9P+erlTtwEALHsnBXynkfPLH3BOUqmgzP25U8kl8eHzq6RAlzrSOfTO8ox9dcp6GLmW33YjO3zkq5VRYyQlJgLCiAZUpY2D4UQcE5D1Vm8RoKfbE+xtVaOctYeINjaQJ1u3mWx9T7tork3uAlOe1uyFjCWU5aPX/1OHhWCGi2EPPZj6vchNqDOJC/Y2k1gkivqCjz1CZl6FlZ7UVPOx3AMoszPuOYZ+Nuqpx2uCE2MHTtMHD8PVjlsWirt56oUr6JPp9aRGo6bitPIOmi4dX0FmuMKD6u/JnuZCp+AXtJVTmSHS8IXt/twsKU7A+fiMK01NtD5msNgVPoe9JbFtlGwvTQ==", "body": "{\"foo\":\"bar\"}", "attributes": { "ApproximateReceiveCount": "3", "SentTimestamp": "1529104986221", "SenderId": "594035263019", "ApproximateFirstReceiveTimestamp": "1529104986230" }, "messageAttributes": {}, "md5OfBody": "9bb58f26192e4ba00f01e2e7b136bbd8", "eventSource": "aws:sqs", "eventSourceARN": "arn:aws:sqs:us-west-2:594035263019:NOTFIFOQUEUE", "awsRegion": "us-west-2" } ] }
  2. Execute the following invoke command.

    $ aws lambda invoke \ --invocation-type RequestResponse \ --function-name ProcessSQSRecord \ --region us-east-1 \ --payload file://file-path/input.txt \ --profile adminuser \ outputfile.txt

    Note that the invoke command specifies RequestResponse as the invocation type, which requests synchronous execution. For more information, see Invoke.

  3. Verify the output in the outputfile.txt file.

    You can monitor the activity of your Lambda function in the AWS Lambda console.

    • The AWS Lambda console shows a graphical representation of some of the CloudWatch metrics in the Cloudwatch Metrics at a glance section for your function. Sign in to the AWS Management Console at

    • For each graph you can also click the logs link to view the CloudWatch logs directly.

Next Step

Step 3: Add an Event Source (Create an Amazon SQS Queue and Associate It with Your Lambda Function)