sam local invoke - Amazon Serverless Application Model
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

sam local invoke

This page provides reference information for the Amazon Serverless Application Model Command Line Interface (Amazon SAM CLI) sam local invoke subcommand.

The sam local invoke subcommand initiates a one-time invocation of an Amazon Lambda function locally.

Usage

$ sam local invoke <arguments> <options>
Note

If you have more than one function defined in your Amazon SAM template, provide the function logical ID that you want to invoke.

Arguments

Resource ID

The ID of the Lambda function to invoke.

This argument is optional. If your application contains a single Lambda function, the Amazon SAM CLI will invoke it. If your application contains multiple functions, provide the ID of the function to invoke.

Valid values: The resource's logical ID or resource ARN.

Options

--add-host LIST

Passes a hostname to IP address mapping to the Docker container's host file. This parameter can be passed multiple times.

Example: --add-host example.com:127.0.0.1

--beta-features | --no-beta-features

Allow or deny beta features.

--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 Amazon SAM CLI configuration file.

--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 Amazon SAM CLI configuration file.

--container-env-vars

(Optional) Pass environment variables to the Lambda function image container when debugging locally.

--container-host TEXT

Host of locally emulated Lambda container. The default value is localhost. If you want to run Amazon SAM CLI in a Docker container on macOS, you can specify host.docker.internal. If you want to run the container on a different host than Amazon SAM CLI, you can specify the IP address of the remote host.

--container-host-interface TEXT

The IP address of the host network interface that container ports should bind to. The default value is 127.0.0.1. Use 0.0.0.0 to bind to all interfaces.

--debug

Turns on debug logging to print debug messages that the Amazon SAM CLI generates, and to display timestamps.

--debug-args TEXT

Additional arguments to pass to the debugger.

--debug-port, -d 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.

--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.

--docker-volume-basedir, -v TEXT

The location of the base directory where the Amazon SAM file exists. If Docker is running on a remote machine, you must mount the path where the Amazon SAM file exists on the Docker machine and modify this value to match the remote machine.

--env-vars, -n 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.

--event, -e 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 '-'. For details about event message formats from different Amazon services, see Working with other services in the Amazon Lambda Developer Guide.

--force-image-build

Specifies whether the Amazon SAM CLI should rebuild the image used for invoking Lambda functions with layers.

--help

Shows this message and exits.

--hook-name TEXT

The name of the hook that is used to extend Amazon SAM CLI functionality.

Accepted values: terraform.

--invoke-image TEXT

The URI of the container image that you want to use for the local function invocation. By default, Amazon SAM pulls the container image from Amazon ECR Public (which are listed in Image repositories for Amazon SAM). Use this option to pull the image from another location.

For example, sam local invoke MyFunction --invoke-image amazon/aws-sam-cli-emulation-image-python3.8.

--layer-cache-basedir DIRECTORY

Specifies the location of the base directory where the layers that your template uses are downloaded to.

--log-file, -l TEXT

The log file to send runtime logs to.

Ensures the Amazon SAM CLI always mounts symlinks that are present in the files to build or invoke. This applies only to symlinks on the top level directory (that is, symlinks that are directly on the function's root). By default, symlinks are not mounted except for those needed to use build-in-source for node_modules in NodeJS.

--no-event

Invokes the function with an empty event.

--no-memory-limit

Removes the memory limitation in the container during local invoke, even when memory is configured in the Amazon SAM template.

--parameter-overrides

A string that contains Amazon CloudFormation parameter overrides encoded as key-value pairs. Use the same format as the Amazon Command Line Interface (Amazon CLI). The Amazon SAM CLI format is explicit key and value keywords, each override is separated by a space. Here are two examples:

  • --parameter-overrides ParameterKey=hello,ParameterValue=world

  • --parameter-overrides ParameterKey=hello,ParameterValue=world ParameterKey=example1,ParameterValue=example2 ParameterKey=apple,ParameterValue=banana

--profile TEXT

The specific profile from your credential file that gets Amazon credentials.

--region TEXT

The Amazon Region to deploy to. For example, us-east-1.

--runtime TEXT

Uses the specified runtime to invoke a Lambda function locally. This overrides the runtime defined in the template.yml file. This also allows testing Lambda functions with different runtimes without modifying the original function configuration.

--save-params

Save the parameters that you provide at the command line to the Amazon SAM configuration file.

--shutdown

Emulates a shutdown event after the invoke completes, in order to test extension handling of shutdown behavior.

--skip-prepare-infra

Skips the preparation stage if no infrastructure changes have been made. Use with the --hook-name option.

--skip-pull-image

By default, the Amazon SAM CLI checks Lambda's latest remote runtime environment and updates your local image automatically to keep in sync.

Specify this option to skip pulling down the latest Docker image for your Lambda runtime environment.

--template, -t PATH

The Amazon SAM template file.

This option is not compatible with --hook-name.

Note

If you specify this option, Amazon SAM loads only the template and the local resources that it points to.

--terraform-plan-file

The relative or absolute path to your local Terraform plan file when using the Amazon SAM CLI with Terraform Cloud. This option requires that --hook-name be set to terraform.

Examples

The following example uses a generated event for local testing by using an s3.json event to invoke a Lambda function locally

$ sam local invoke --event events/s3.json S3JsonLoggerFunction

The following example tests the function HelloWorldFunction using Python 3.11 runtime

$ sam local invoke --runtime python3.11 HelloWorldFunction