NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
PyPI · #3938 most downloaded on PyPI
AWS SAM CLI is a CLI tool for local development and testing of Serverless applications
Last release 23 days ago
11 Sep 2026
Ships fairly regularly
a new release about every 3 weeks
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
249 releases · first in 2018
With this change, the preview local extensions APIs support subscription to the Logs API. Consuming log events locally is not yet supported.
With this change, the preview local extensions APIs support subscription to the Logs API. Consuming log events locally is not yet supported.
084c758 - chore: Improve help text for build command to highlight the ability to build individual resources (#2076) 8435b57 - ci: check PR title (#2367) b3b3f27 - feat: Update Preview init (#2372) c87c97e - chore: bump version to 1.10.0 (#2374)
SAM CLI now supports cached and parallel builds for function and layers.
SAM CLI now supports cached and parallel builds for function and layers.
sam build --cached will build functions with caching enabled. If function or layer source haven't change since the last cached build, it will just use what has been cached before. Default caching directory will be under .aws-sam/cache but this can be overriden by providing --cache-dir parameter as well. For now, custom builds with Makefile is not supported with cached builds.
sam build --parallel will build functions in parallel. Normally, SAM CLI builds each function sequentially, it starts building each function and waits for completion of that build. With --parallel option, it will trigger multiple builds at the same time, and will complete build once all of the parallel builds are done.
71be4f8 - fix: Layer Deployment Permission Issue (#2356) 754a0f0 - chore: bump version to 1.9.0 (#2358) b142160 - feat: Cached and Parallel build implementation (#2351) (#2357) d279320 - fix: Fix canary failures and update help text for build command (#2365)
One column per quarter.
a30ff71 - chore: bump version (#2340) df7dcb2 - Update AL2 Provided Build Image Src (#2339) 9d242f2 - Upgrade base & dev Dependences except pylint (#2
a30ff71 - chore: bump version (#2340) df7dcb2 - Update AL2 Provided Build Image Src (#2339) 9d242f2 - Upgrade base & dev Dependences except pylint (#2305) ede6517 - Remove six usage (#2343) 5f3e41e - refactor: get rid of hardcoded test template list (#2338) cdfd127 - fix(classifiers): Mark AWS SAM CLI as Production/Stable (#2263) 294bbaa - fix HttpApi event V2 route key (#2350) e82e54a - chore: Remove snapcraft configuration (#2349) 90ec94d - Update bug_report.md for Slack unfurl (#2276) 413c840 - feat: update sam-translator version to 1.29.0 (#2354)
cd4c061 - Log timestamps when --debug flag is presented (#2266) 48349d4 - fix: bump junit (#2296) 42fa0ad - Upgrade pylint (#2304) 5ff9781 - fix: use
cd4c061 - Log timestamps when --debug flag is presented (#2266) 48349d4 - fix: bump junit (#2296) 42fa0ad - Upgrade pylint (#2304) 5ff9781 - fix: use name instead of functionname when creating build graph (#2297) e936994 - fix: for de-dup builds, build into one of the function folder instead of temporary folder (#2309) d725db5 - chore: Manage black version in dev.txt (#2314) 346ff29 - chore: Update DEVELOPMENT_GUIDE.md (typo) (#2319) 695d8a3 - Create Event for AppSync (Direct Lambda Resolver) (#2200) ea88b90 - Support running HttpApi locally (#1942) 1bda78b - apply PayloadFormationVersion in httpapi event (#2326) b7634fd - Add integration test case to test Http Api && Rest Api in the same template (#2327) eb2e197 - fix: fail on invalid config (#2316) 7d5101a - Fix: Missing Unix Permission Bits for Artifact ZIP Created in Windows (#2193) d390a57 - Fix: relpath Fails with Different Drives (#2138) ac71571 - Fix: Make API Gateway infer Lambda function response for HttpApi with PayloadFormatVersion 2.0 (#2334) eb411a6 - chore: bump sam cli version to 1.7.0, and sam translator requirement to 1.28.1 (#2336)
Updating manifest to include preview_rapid
This release of AWS SAM CLI includes initial support for locally testing AWS Lambda Extensions – which are now available in preview. Extensions are a
This release of AWS SAM CLI includes initial support for locally testing AWS Lambda Extensions – which are now available in preview. Extensions are a new way for tools to integrate deeply into the Lambda execution environment to control and participate in Lambda’s lifecycle. To learn more about extensions and updates to the AWS Lambda execution environment, see <Introducing AWS Lambda Extensions – In Preview>(+link to blog post).
You can now use SAM CLI to locally invoke functions which use extensions. To get started, opt-in to the new execution environment using an opt-in flag – set the ENABLE_LAMBDA_EXTENSIONS_PREVIEW environment variable to “1” before you run your local tests. For example:
ENABLE_LAMBDA_EXTENSIONS_PREVIEW=1 sam local invoke
Without this opt-in flag, local testing will continue to use the previous execution environment.
Give this new execution environment a try and let us know what you think through a GitHub issue or feature request. We would love your feedback on how we can improve your local development and testing workflows with SAM CLI.
This release also introduces de-duplication build improvement which will build the functions once if they share same CodeURI/Runtime/Metadata. Custom builds (which uses Makefile) are not supported.
57ef284 - Add Local Testing Support for Lambda Extensions (#2281) 7c494e1 - chore: bump version to 1.6.0 (#2282) 2f6061f - feat: de-duplicated builds (#2232)
ef74a09 - Debugging support for dotnet3.1 (#2265) f23baa9 - Update __init__.py
47f813a - fix: use parameter overrides from configuration file or command line (#2234) cf1f869 - Add SAM_CLI_VERSION build arg to provided image (#224
0b22b17 - Cleaning empty test file. (#2204) 507a2fd - Fixing bug when validation resource with no type. (#2207) 0d05201 - fix: Force strings to be out
0b22b17 - Cleaning empty test file. (#2204) 507a2fd - Fixing bug when validation resource with no type. (#2207) 0d05201 - fix: Force strings to be outputted when string starts with 0 (#2174) 73a8255 - Added a column in print changeset to show if replacement happened (#2198) 91d9231 - feat: Add support for customized message body in generated SQS message (#2209) 2d8a368 - Add "Build All Images" Script (#2211) 449c3d0 - Fix #1392: Catch pywintypes.error when determining if docker is reachable (#2215) 1cfc1a6 - fix: displaying warning if Condition and DeploymentPreferences are using on SAM Function resource. (#2218) 98b5fbb - feat: Added the option to hide progress bars during s3 upload for sim… (#2187) 648eebe - chore: Updated Slack #samdev Invite Link (#2225) 0c77ad0 - Fix: fixed an integration test error with pull #2187 (#2226) 3edb55c - feature: Enable --config-env and --config-file to support multiple configuration environments and files (#2176) 6253d82 - fix: flaky test and ingegration tests (#2236) e026b69 - Chore: Bumped aws-sam-translator to version 1.27.0 and aws-sam-cli to version 1.3.0 (#2241)
f269fe2 - fix: md5 of directories are inconsistent without sorting the file paths
bb38454 - chore: readme update with screenshot (#2117) 3d32115 - Matdumsa/gitpod setup (#2039) 1c3753f - Update boto3 (#2130) 7c56e4e - Adding tag par
bb38454 - chore: readme update with screenshot (#2117)
3d32115 - Matdumsa/gitpod setup (#2039)
1c3753f - Update boto3 (#2130)
7c56e4e - Adding tag parser for space separated tags. (#2155)
e8cae9d - fix: add missing fields to RequestContext for local lambda invoke (#2060)
387f731 - Fix: Use Docker Python SDK Version 4.2.x Instead of 4.x (#2166)
947a967 - chore: version 1.1.0 (#2167)
58ea00e - fix: remove redundant print_deploy_args call (#2162)
3373c41 - Support wrapping in single quotes for parameter_override values (#2139)
65175f6 - Add Support for Java8 and Provided AL2 Runtimes (#2168)
42b6442 - Update Init Integ Tests (#2169)
SAM CLI v.1.0.0 is a stable version recommended for building production serverless applications.
SAM CLI v.1.0.0 is a stable version recommended for building production serverless applications.
The stable version follows the below semantic version patterns:
Previously, SAM CLI was available in beta, supported by the docker-lambda emulation images developed by Michael Hart (AWS Serverless Hero). Now, v1.0.0 is supported by AWS provided emulation images. This version also includes new build support for custom AWS Lambda runtimes and AWS Lambda Layers.
Release Candidate 2 for AWS SAM CLI general availability release.
Release Candidate 2 for AWS SAM CLI general availability release.
This release fixes a bug in which customers installing with Homebrew could not invoke a function locally (issue #2095).
All changes should be fully backwards compatible with 0.53.0 and 1.0.0rc1. Assuming no regressions or issues are identified, this will become AWS SAM CLI 1.0.0.
Release Candidate 1 for AWS SAM CLI general availability release.
Release Candidate 1 for AWS SAM CLI general availability release.
Uses amazon/aws-sam-cli* images from DockerHub for building with containers and for local testing. These images are based off the AWS Lambda execution environment.
All changes should be fully backwards compatible with 0.53.0. Assuming no regressions or issues are identified, this will become AWS SAM CLI 1.0.0.
2a0cdd3 - docs: Removing python 2 info from the development guide (#1993) a2bec59 - Adding docker info. (#1995) b5b1ec4 - fix: guided deploy doesn't u
2a0cdd3 - docs: Removing python 2 info from the development guide (#1993) a2bec59 - Adding docker info. (#1995) b5b1ec4 - fix: guided deploy doesn't update default capabilities that is provided via --capabilites option as CLI argument (#2041) 612ee73 - fix(start-api): Don't cache static files in responses (#2038) 4f12dc7 - fix(docs): md table-format for sam-build-cmd design (#1984) cd5efb0 - Adding SAM 1.25.0 Functional Test (#2048) 4c467b5 - chore: bump version to 0.53.0 (#2049) c4dbf96 - Removing hack for docker issue as it is fixed by AppVeyor. (#2050)
3ed51f2 - Fixed inline help issue in "sam local generate-event" (#2007) 5d5d81a - Fixing bug for build for layers in container. (#2008) de0633f - feat
SAM CLI now supports building provided runtimes specified in template by specifying BuildMethod : makefile in the Metadata Attribute of the Function R
provided runtimesSAM CLI now supports building provided runtimes specified in template by specifying BuildMethod : makefile in the Metadata Attribute of the Function Resource.
SAM CLI supports building via makefile for official lambda runtimes as well.
Template
Resources:
HelloRustFunction:
Type: AWS::Serverless::Function
Properties:
Handler: bootstrap.is.real.handler
Runtime: provided
MemorySize: 512
CodeUri: .
Metadata:
BuildMethod: makefile
Makefile
build-HelloRustFunction:
cargo build --release --target x86_64-unknown-linux-musl
cp ./target/x86_64-unknown-linux-musl/release/bootstrap $(ARTIFACTS_DIR)
Layers can also be built using BuildMethod : makefile
49cb854 - feat: allow a custom builder workflow selection (#1957) 39add9a - feat: adding makefile workflow for layers build. (#2000) 98be672 - chore: version v0.51.0 (#2004)
SAM CLI now supports building layers specified in template by specifying BuildMethod under a Metadata Attribute of the Layer Resource. If BuildMethod
SAM CLI now supports building layers specified in template by specifying BuildMethod under a Metadata Attribute of the Layer Resource. If BuildMethod is not specified, the layer is not built.
Resources:
HelloWorldFunction:
Type: AWS::Serverless::Function # More info about Function Resource: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#awsserverlessfunction
Properties:
CodeUri: hello_world/
Handler: app.lambda_handler
Runtime: python3.8
Layers:
- !Ref MyLayer
- !Ref MyLayer2
Events:
HelloWorld:
Type: Api # More info about API Event Source: https://github.com/awslabs/serverless-application-model/blob/master/versions/2016-10-31.md#api
Properties:
Path: /hello
Method: get
MyLayer:
Type: AWS::Serverless::LayerVersion
Properties:
Description: Layer description
ContentUri: 'my_layer/'
CompatibleRuntimes:
- python3.8
Metadata:
BuildMethod: python3.8
MyLayer2:
Type: AWS::Serverless::LayerVersion
Properties:
Description: Layer description
ContentUri: 'my_layer2/'
CompatibleRuntimes:
- python3.8
sam build MyLayer build single layer.
sam build HelloWorldFunction builds function and the layer that the function uses.
23212ef - Build for Layers (#1936) de8ad8e - Adding design doc for 'build for layers' (#1945) 24af60e - chore: version bump to 0.50.0 (#1998) 30b1016 - bug: security prompt - instrinsics in definition body (#1988)
972fa19 - refactor!: Drop support for deprecated runtimes
SamTranslatorWrapper (#1961)c3b66eaf - feat: Print warning about using deprecated runtimes
0422bcf - feat: dotnetcore3.1 support (#1908) f4e21b9 - chore: version bump to 0.47.0
3b76aff - fix: Use LogicalId for Env Vars fetching within the Env Var file (#1892) 7de8bb0 - chore: bump version to 0.46.2
91647c7 - fix(start-api): Allow invoking when a function has a FunctionName (#1886) 7af12de - chore: bump version to 0.46.1
07a3368 fix: usage of old method name '_run_command' (#1881) 9d86ab2 fix(start-api): Remove trailing slashes on endpoints (#1495) 550c1b4 feat(invoke)
07a3368 fix: usage of old method name '_run_command' (#1881) 9d86ab2 fix(start-api): Remove trailing slashes on endpoints (#1495) 550c1b4 feat(invoke): Allow invoking with function name (#1215) 68d4ae6 fix(build): Do not treat urls as local paths (#1879) 5d4fec6 fix: support 4th property in error output for lambdas (#1820) 83e70f4 fix: adding APPVEYOR_CONSOLE_DISABLE_PTY environment variable to fix random appveyor job failure. (#1875) 72280fc fix: Log warning if there is unresolved intrinsics in cors (#1874) 7bc702c fix: changing order of parameterized expand and flaky annotation. (#1873) 337093f fix: rebasing PR on github dashboard missed one method rename. (#1871) 7db771d fix: adding better logging to build_integ_test base's run of Popen command (#1869)
cc50505 - fix: removing object deletion and using same stack name for integration tests to avoid NoSuchKey errors. (#1850) 36e0f4f - fix: adding separ
cc50505 - fix: removing object deletion and using same stack name for integration tests to avoid NoSuchKey errors. (#1850) 36e0f4f - fix: adding separate bucket env var to windows appveyor file. (#1858) e7d95bd - fix: buildcmd to use same level of logging as deploy integration tests. (#1864) bb0fa2e - fix(start-api): raise concrete exceptions during parsing of lambda output (#1835) ac4d48e - chore: Version bump to 0.45.0 (#1868) e502103 - chore: bump translator version and add tests (#1859) 2bbc26a - fix(deploy): default capabilities on guided mode to be a list (#1867)
3ab3b1d - feat: update SAM dependency to v1.21.0 (#1814) b2c8d99 - fix: config_dir creation permission. Hex permissions were used instead of Oct (#181
3ab3b1d - feat: update SAM dependency to v1.21.0 (#1814) b2c8d99 - fix: config_dir creation permission. Hex permissions were used instead of Oct (#1818) af079d7 - feat: adding separate bucket based on python version for integration tests. (#1828) a71427e - fix(start-api): Return empty instead of no data when no response (#1813) a4726d5 - fix: bug around using temporary credentials in event bridge integration test. (#1829) 37b10ea - refactor: deploy integration tests to use same level of logging. (#1832) 3592272 - fix: bug introduced in deploy integ test refactoring. (#1833) 7cab71b - fix(ci): Go version to 1.13 and update patch python versions (#1837) 7531d2e - chore: Upgrade jmespath to remove SyntaxError logs (#1831) 5763a9d - chore: Upgrade aws-lambda-builders to 0.8.0 (#1849) 855ec43 - chore: bump version to 0.44.0 (#1851)
88bc1a3 - feat: Support for ruby2.7 (#1806) 7dea76a - chore: version bump to 0.43.0 (#1808) 8355c30 - fix: init integration tests - event bridge relie
…outputs text (#1788) 546d06e - fix(test): Fix deprecation warnings due to invalid escape sequences. (#1787) b422f0a - fix: config env cannot be anythi…
91c22c3 - fix: deploy help text for --template-file option. (#1774)
1c83bb0 - fix: appveyor windows job - python version (#1776)
7ba1b44 - fix(deploy): Allow all Partitions for S3 Policy on managed stack (#1784)
776f332 - fix: Handle the case for Parameters being empty strings (#1785)
fa19f22 - ux: improve deploy outputs text (#1788)
546d06e - fix(test): Fix deprecation warnings due to invalid escape sequences. (#1787)
b422f0a - fix: config env cannot be anything other than default (#1769)
b352127 - fix: display no outputs if outputs are not defined. (#1790)
e1951c0 - feat(deploy): Efficient deploy log fetching (#1768)
1225ed9 - fix(tests): Upgrade deprecated runtime nodejs6.10 to nodejs10.x (#1722)
0c69e73 - Upgrade deprecated runtime nodejs8.10 (#1719)
96c8f11 - test: run by canary (#1793)
3f4cfef - fix(readme): Remove unfortunate dash (#1796)
bfd327f - fix(package): Only package if files have changed (#1789)
1c4bf97 - Allow the characters _:./+-@= to be used in tag keys during deploy (#1798)
526f8da - fix(start-api): Options requests to properly invoke lambda function (#1649)
bdfd97f - chore: Version Bump to 0.42.0 (#1802)
a22b085 - fix: aws-serverless-function template to have python3.7 runtime (#1805)
b791e15 - fix(test): Remove package regression tests (#1807)
388408c - fix(build): Handle dot notations in the path_prop_name variables (#1550) 4e07913 - Support SAM Build with Go Modules (#1731) 34b153c - chore
388408c - fix(build): Handle dot notations in the path_prop_name variables (#1550) 4e07913 - Support SAM Build with Go Modules (#1731) 34b153c - chore: add functional test cases for sam v1.20.1 (#1680) d807f78 - deploy command help improvements (#1746) 125f0b0 - fix: cache MFA based credentials (#1744) 0c50871 - fix: Handle global value for Function CodeUri in Package (#1766) 7a170b7 - chore: version bump to 0.41.0 (#1742) ca6dfb8 - chore: version bump on aws-lambda-builders to 0.7.0 (#1771) 20ce234 - feat: boto user agent string for package and deploy (#1757)
db6fcd6 - chore: Support Python3.8 (#1519) ff04d75 - refactor: sam deploy (#1681) 2988643 - revert: boto user agent (#1707) a35819d - fix: github pull
db6fcd6 - chore: Support Python3.8 (#1519)
ff04d75 - refactor: sam deploy (#1681)
2988643 - revert: boto user agent (#1707)
a35819d - fix: github pull request template (#1687)
741d22b - fix: change permissions and remove files on rmtree (#1694)
e12db92 - fix: samconfig design accuracy (#1702)
2d71af8 - fix: botocore session cache across samcli (#1693)
175cd9c - fix: linting on ubuntu (#1710)
916be85 - chore: bump version to 0.40.0 (#1709)
d72e1ea - Revert "fix: botocore session cache across samcli (#1693)" (#1717)
a068009 - Remove nodejs8.10 Init (#1716)
This release includes support for the latest version of aws-sam-translator (1.19.1), and several bug fixes/UX improvements.
This release includes support for the latest version of aws-sam-translator (1.19.1), and several bug fixes/UX improvements.
sam init (#1678)SAM CLI now supports debugging Java11 Lambda Functions locally.
SAM CLI now supports debugging Java11 Lambda Functions locally.
AWS SAM CLI updated to include aws-sam-translator v1.19.0 which introduces support for the HTTP APIs.
AWS SAM CLI updated to include aws-sam-translator v1.19.0 which introduces support for the HTTP APIs.
SAM CLI now supports validate, build, package, deploy and local execution of SAM templates that include Lambda provisioned concurrency configurations.
SAM CLI now supports validate, build, package, deploy and local execution of SAM templates that include Lambda provisioned concurrency configurations.
This release introduces support for Amazon EventBridge schema registry. sam init now includes additional options to create an EventBridge app from scr
This release introduces support for Amazon EventBridge schema registry. sam init now includes additional options to create an EventBridge app from scratch, with a specific event schema as a trigger. This will automatically generate strongly-typed class files for the event in your serverless application, including the AWSEvent payload, a marshaller, and an EventBridge rule in your SAM template. You can easily try out the feature by using one of the existing aws.events service schemas available in the schema registry.
With this release, you can initialize SAM apps directly from a Git repository using sam init command. This allows you to copy a Github URL and run sam
With this release, you can initialize SAM apps directly from a Git repository using sam init command. This allows you to copy a Github URL and run sam init -l <url> to download it locally. Previously, sam init could initialize only from cookiecutter templates (ie. projects with cookiecutter.json file in the root).
SAM CLI, now allows you to deploy applications with a single command: sam deploy. Previously, deploying applications through SAM CLI required more tha
SAM CLI, now allows you to deploy applications with a single command: sam deploy. Previously, deploying applications through SAM CLI required more than one step and needed you to provide an Amazon S3 bucket for the Lambda deployment package. SAM CLI now creates and manages this S3 bucket for you. It also allows you to easily configure the deployment parameters, and execute subsequent deployments by running the sam deploy command without parameters.
The sam deploy command now comes with a guided interactive mode (sam deploy —guided). This mode walks you through the parameters required for deployment, provides default options, and saves your input for the given application. You can also see changes made to the application stack that will be deployed through the sam deploy command output, as well as configure the command to ask for confirmation on changes before deploying.
SAM CLI now supports a new samconfig.toml configuration file which currently will act as a passthrough for parameters to SAM CLI commands.
sam deploy also packages built artifacts (#1521)--confirm-changeset through to deploy commandsamconfig.get_all--interactive to ask for parameterssam deploy (#1565)stack-name is required on deploy (#1573)samconfig.toml file (#1581)sam deploy --guided (#1588)static bucket solution (#1589)With this release, you can now use Python3.8, Nodejs12.x, and Java11 Runtimes!
With this release, you can now use Python3.8, Nodejs12.x, and Java11 Runtimes!
SAM CLI now supports running sam package without AWS CLI installed. This release also includes user experience improvements to interactive sam init co
sam package commandSAM CLI now supports running sam package without AWS CLI installed. This release also includes user experience improvements to interactive sam init command.
sam local invoke command will no longer require an event data by default. Previously, this behavior was available by passing the --no-event parameter. To pass event data via stdin, you can use the --event parameter with a value of -.
Example: echo '{"message": "Hey, are you there?" }' | sam local invoke "HelloWorldFunction" --event -
SAM CLI now supports running sam package without AWS CLI installed. This release also includes user experience improvements to interactive sam init co
sam package commandSAM CLI now supports running sam package without AWS CLI installed. This release also includes user experience improvements to interactive sam init command.
sam local invoke command will no longer require an event data by default. Previously, this behavior was available by passing the --no-event parameter. To pass event data via stdin, you can use the --event parameter with a value of -.
Example: echo '{"message": "Hey, are you there?" }' | sam local invoke "HelloWorldFunction" --event -
This release provides an interactive workflow for the sam init command. To use the interactive init feature, just call sam init without any parameters
This release provides an interactive workflow for the sam init command. To use the interactive init feature, just call sam init without any parameters and follow the prompts!
This release also ends support for installing the AWS SAM CLI on Python 2.7 (building and invoking Python 2.7 functions for AWS Lambda is still supported).
SAM CLI now marks installations under python2.7 as deprecated with intentions to drop support for python 2.7 from next release. This release also has…
SAM CLI now marks installations under python2.7 as deprecated with intentions to drop support for python 2.7 from next release. This release also has the latest aws-sam-translator version of 1.15.1.
Changelog
SAM CLI now supports validating and parsing SAM templates that contain latest SAM capabilities such as OpenApi3, IAM Authorizers, API Key authorizers
SAM CLI now supports validating and parsing SAM templates that contain latest SAM capabilities such as OpenApi3, IAM Authorizers, API Key authorizers etc. This release also includes several bug fixes in the build and start-api commands.
2d95111 - warning: deprecation warning message - Python 2.7
SAM CLI now supports resolving more Intrinsics functions within the template, including Fn::Sub, Fn::Join, and Fn::FindInMap. In addition to this, sam local start-api will now work when your APIs are defined with AWS::ApiGateway::Methods, AWS::ApiGateway::RestApi, AWS::ApiGateway::Resource, and AWS::ApiGateway::Stage resources.
defaultNothing published for this version
Nothing published for this version
SAM CLI is adding telemetry. In addition to existing feedback, telemetry allows us to better understand our customer’s needs, common CLI scenarios and
SAM CLI is adding telemetry. In addition to existing feedback, telemetry allows us to better understand our customer’s needs, common CLI scenarios and existing issues. The information collected will include generic usage metrics, system and environment information, and errors. These generic metrics will inform our product decisions and help us continue to deliver features and enhancements that improve the customer experience.
Read #1272 for more information on the user experience and opt-out instructions.
Support users who sit behind a proxy and have configured their proxy settings in docker configuration file ~/.docker/config.json to pass their traffic
Support users who sit behind a proxy and have configured their proxy settings in docker configuration file ~/.docker/config.json to pass their traffic through proxy servers. eg: pypi proxy
We have also added some improvements:
sam local start-apisam local start-apisam local start-api now supports multiValueHeaders in response from Lambda
You can now provide the arnlambda::AmazonLinux1803 Layer in the template to invoke/build Lambda Functions. Further details can be found here about Lam
You can now provide the arn:aws:lambda:::awslayer:AmazonLinux1803 Layer in the template to invoke/build Lambda Functions. Further details can be found here about Lambda Execution Environments.
Locally invoke, test and debug your Nodejs10.x Lambda functions in SAM CLI!
Locally invoke, test and debug your Nodejs10.x Lambda functions in SAM CLI!
sam build now also supports building an individual Lambda Function by providing its Logical ID to the command. If your template file contains a lambda function resource with name HelloWorldFunction you can now build the function directly as follows.
sam build HelloWorldFunction
In addition, we have made improvements to the CLIs installation time for Brew by providing Bottles.
fix(init): Default all configuration to dotnetcore2.1 for dotnetcore (#1133) fix go-delve URL (#1142) feat(build): Build a single function (#1146) feat(layers): Layer Downloader will use AWS_CA_BUNDLE if it exists (#1143) Validate API Gateway Response Keys (#1154) chore(version): version bump to 0.16.0 (#1167) feat(nodejs10): support new nodejs10 runtime (#1175)
sam build now supports building Lambda Functions with DotNetCore 2.0 and 2.1 runtimes.
sam build now supports building Lambda Functions with DotNetCore 2.0 and 2.1 runtimes.
We have also added some improvements:
sam build --use-container (#1075)This release has a patch for the gradle based init templates.
This release has a patch for the gradle based init templates.
See https://github.com/awslabs/aws-sam-cli/releases/tag/v0.14.0 for release notes. This release fixes #1080
See https://github.com/awslabs/aws-sam-cli/releases/tag/v0.14.0 for release notes. This release fixes #1080
This release adds support for step through debugging of your Python3.7 Lambda Functions. We have some bug fixes as well:
This release adds support for step through debugging of your Python3.7 Lambda Functions. We have some bug fixes as well:
--use-container flag.You can now use the sam build command to create deployment packages for AWS Lambda functions written in Java using the Maven build tool.
You can now use the sam build command to create deployment packages for AWS Lambda functions written in Java using the Maven build tool.
In addition, sam init was expanded to support creating projects with different dependency managers. You can now create a Maven example by running sam init --runtime java --dependency-manager maven. See sam init --help for other supported values for the --dependency-manager Option.
Huge shoutout to @zoewangg for contributing the Maven builder
Changelog Chore: Bump aws-sam-translator to 1.10.0 (#1043) feat(init): gradle init support (#1040) feat(build): Support building Java8 functions through Maven (#1044) feat(publish): Add --semantic-version option to sam publish command (#1020)
You can now use the sam build command to create deployment packages for AWS Lambda functions written in Java using the Gradle build tool.
You can now use the sam build command to create deployment packages for AWS Lambda functions written in Java using the Gradle build tool.
Huge shoutout to @dagnir for contributing the Gradle builder
This release contains numerous improvements throughout the CLI, including simpler hello world quickstarts, doc updates, removing unnecessary compressi
This release contains numerous improvements throughout the CLI, including simpler hello world quickstarts, doc updates, removing unnecessary compression when building a layer image for invoking, and cleaning up build containers.
You can now use sam build to compile deployment packages for AWS Lambda functions written in supported Ruby runtimes. Huge shout-out to @awood45 for t
You can now use sam build to compile deployment packages for AWS Lambda functions written in supported Ruby runtimes. Huge shout-out to @awood45 for this contribution!
You can now also use the new sam publish command to publish your serverless application to the AWS Serverless Application Repository, a managed repository for serverless applications. The AWS Serverless Application Repository enables teams, organizations, and individual developers to store and share reusable applications, and easily assemble and deploy serverless architectures in powerful new ways. To publish an application using SAM CLI, first define necessary application details like application name, description, semantic version, and license information using the AWS::ServerlessRepo::Application Key in the Metadata section of your SAM template. Then, use the sam publish command to make your application available in the AWS Serverless Application Repository for others to consume. To learn more, please visit the sam publish documentation. Huge shout-out to @paoptu023 for this contribution!
You can now use the sam build command to compile deployment packages for AWS Lambda functions written in supported Node.js runtimes. Huge shout-out to
You can now use the sam build command to compile deployment packages for AWS Lambda functions written in supported Node.js runtimes. Huge shout-out to @gojko for this contribution!
You can now debug Lambda functions written in .NET Core using Visual Studio Code. To get started, check out the documentation: Debugging .NET Core functions. Huge shout-out to @ndobryanskyy for this contribution!
docs: Update Slack invite link (#781) fix: Create Layer Cache during building image (#823) docs: list Ruby2.5, Python3.7 and Provided as supported runtime (#822) fix: Making hello world java sample more idiomatic (#802) fix: Update to .NET Core init template (#705) fix: Stop html encoding of options for generate-event (#824) docs: Issue templates for bug and feature requests (#726) fix: Fix Makefile typo (#829) Feature: .NET Core 2.0/2.1 debugging support (#825) refactor: Move checking Docker connectivity to ContainerManager (#828) fix: Update functional tests to work (#841) Feature: Support building Node.js functions (#845)
Your coding agent can read these notes before it upgrades. Set up the MCP server →