sam local invoke - AWS Serverless Application Model

sam local invoke

Invokes a local AWS Lambda function once and quits after invocation completes. To invoke a function of a nested application or stack, you can provide the application or stack logical ID along with the function logical ID using the format StackLogicalId/FunctionLogicalId.

The sam local invoke command is useful for developing serverless functions that handle asynchronous events, such as Amazon Simple Storage Service (Amazon S3) or Amazon Kinesis events. It can also be useful if you want to compose a script of test cases. You can pass in the event body using the --event parameter. The runtime output (for example, logs) is output to stderr, and the Lambda function result is output to stdout.

Note

If there is more than one function defined in your AWS SAM template, you must provide the FUNCTION_LOGICAL_ID of the function you want to invoke.

Usage:

sam local invoke [OPTIONS] [FUNCTION_LOGICAL_ID]

Options:

Option Description
-e, --event PATH The JSON file that contains event data that's passed to the Lambda function when it's invoked. If you don't specify this option, no event is assumed. To input JSON from stdin, you must pass in the value '-'.
--no-event Invokes the function with an empty event.
-t, --template PATH The AWS SAM template file [default: template.[yaml|yml]].
-n, --env-vars PATH The JSON file that contains values for the Lambda function's environment variables. For more information about environment variable files, see Environment variable file.
--parameter-overrides (Optional) A string that contains AWS CloudFormation parameter overrides encoded as key-value pairs. Uses the same format as the AWS Command Line Interface (AWS CLI). For example: 'ParameterKey=KeyPairName, ParameterValue=MyKey ParameterKey=InstanceType, ParameterValue=t1.micro'.
-d, --debug-port TEXT When specified, starts the Lambda function container in debug mode and exposes this port on the local host.
--debugger-path TEXT The host path to a debugger that's mounted into the Lambda container.
--debug-args TEXT Additional arguments to pass to the debugger.
-v, --docker-volume-basedir TEXT The location of the base directory where the AWS SAM file exists. If Docker is running on a remote machine, you must mount the path where the AWS SAM file exists on the Docker machine and modify this value to match the remote machine.
--docker-network TEXT The name or ID of an existing Docker network that Lambda Docker containers should connect to, along with the default bridge network. If this isn't specified, the Lambda containers connect only to the default bridge Docker network.
--container-env-vars (Optional) Pass environment variables to the Lambda function image container when debugging locally.
-l, --log-file TEXT The log file to send runtime logs to.
--layer-cache-basedir DIRECTORY Specifies the location of the base directory where the layers that your template uses are downloaded to.
--skip-pull-image Specifies whether the AWS SAM CLI should skip pulling down the latest Docker image for the Lambda runtime.
--force-image-build Specifies whether the AWS SAM CLI should rebuild the image used for invoking Lambda functions with layers.
--profile TEXT The specific profile from your credential file that gets AWS credentials.
--region TEXT The AWS Region to deploy to. For example, us-east-1.
--config-file PATH The path and file name of the configuration file containing default parameter values to use. The default value is "samconfig.toml" in the root of the project directory. For more information about configuration files, see AWS SAM CLI configuration file.
--config-env TEXT The environment name specifying the default parameter values in the configuration file to use. The default value is "default". For more information about configuration files, see AWS SAM CLI configuration file.
--debug Turns on debug logging to print debug messages that the AWS SAM CLI generates, and to display timestamps.
--help Shows this message and exits.