Skip to content
A Gradle plugin for deploying AWS SAM Projects. You can define your serverless archetecture using AWS SAM and deploy your Gradle Lambda based serverless application projects using this plugin.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Gradle AWS SAM Deployer Plugin

This plugin allows for the convenient deployment of Serverless Application Model (SAM) CloudFormation Templates for lambda based serverless applications from within a Gradle project.

This plugin is inspired by the official AWS CLI, specifically the package (code / description) and deploy (code / description) commands which are described in AWS's Introducing Simplified Serverless Application Deployment and Management blog post.

I kept finding myself executing shell to use the CLI to execute those commands in a non-elegant manner in my gradle scripts and was motivated to create this plugin.

This plugin has 2 tasks packageSam and deploySam described below that closely mirror the AWS CLI Commands.



This task uses the tokenArtifactMap, region, s3Bucket, s3Prefix, kmsKeyId, forceUploads extension properties to upload artifacts defined in the map to s3.

If you supply a KMS CMK id via the kmsKeyId property the uploads will be configured to be encrypted with your KMS key. If you do not supply a KMS CMK id the task will configure your uploads to use the server side AES256 encryption.

This task uses MD5 hashes to name your files, so that it can detect if no changes have been made since the last upload and skip re-uploading files that have not changed. You can use forceUploads = true to always force fresh uploads.

Once uploads are complete this tasks copies your SAM Template that you defined in samTemplatePath to the build dir in the sam folders and uses ant to replace the tokens you defined in the map with the S3 URIs so that when you deploy the template CloudFormation will know where your artifacts are in S3.


This task uses the template outputted by the packageSam task and CloudFormation to create a change set to either create or update your stack using the stackName property you configured.

This task will ask CloudFormation to validate your template and get all the parameters that the template requires. The plugin then iterates over the template parameters and either uses your overrides defined in parameterOverrides or tells CloudFormation to use the previous value.


To use the plugin, include it as a dependency in your buildscript section of build.gradle:

Latest release:

Build script snippet for use in all Gradle versions:

buildscript {
  repositories {
    maven {
      url ""
  dependencies {
    classpath "[VERSION]"

apply plugin: ""

Build script snippet for new, incubating, plugin mechanism introduced in Gradle 2.1:

plugins {
  id "" version "[VERSION]"

Configure the extension properties in the aws-sam-deployer closure:

Property name Type Required Description
region String Yes The region to upload the fatJar / lambda code artifact, and execute the cloud formation in
s3Bucket String No The S3 Bucket to store the fatJar / lambda code artifact
s3prefix String No The prefix in the bucket to use when storing the fatJar / lambda code artifact
kmsKeyId String No The kms cmk id to use to encrypt the fatJar / lambda code artifact when uploading to S3, if not supplied server side AES256 will be used
samTemplatePath String Yes The file path to the SAM Yaml or JSON where you have defined your serverless application model
stackName String Yes The stack name to use for the Cloud Formation stack
parameterOverrides Map<String, String> No A map of Parameters and there values to supply the Cloud Formation template
tokenArtifactMap Map<String, String> No A map of ant style tokens ex: @@FAT_JAR_URI@@ to file paths ex: ${project.buildDir.absolutePath}${File.seperator}libs${File.seperator}my-lambda-project-fat-jar.jar, the package command uses this map to upload the files to s3 and replaces the tokens in the sam template with the S3 URIs
forceUploads boolean No By default if this is left off or set to false, to package command uses m5 hashes to skip files that have not changed since the last deploy. Set this to true to force re-uploading
logStackOutputs boolean No If set to true logs stack outputs after template execution.


Below is an example that supports using profiles to have env specific configuration

plugins {
  id "" version "[VERSION]"

apply plugin: ""

// load environment specific props from env profiles
def environment = project.hasProperty('environment') ? project.'environment' : 'default'
Properties props = new Properties()
props.load(new FileInputStream("$project.rootDir/profile/"+"$environment"+".properties"))
props.each { prop ->
    project.ext.set(prop.key, prop.value)

'aws-sam-deployer' {
    region = project.region
    s3Bucket = project.s3Bucket
    s3Prefix = "${project.getName()}-artifact-uploads"
    stackName = "${project.environment}-jvm-lambda-template"
    samTemplatePath = "${project.rootDir.absolutePath}${File.separator}application.yaml"
    tokenArtifactMap = [
            '@@CODE_URI@@': "${project.buildDir.absolutePath}${File.separator}libs${File.separator}jvm-lambda-template.jar"

Now you can execute the deploySam command ./gradlew clean shadowJar deploySam -Penvironment=development --stacktrace

Quick Start

You can clone my jvm lambda template project that has hello world for Java, Scala and Groovy and is pre-configured with this plugin to be up and running with a new SAM JVM Serverless Application.


Justin Field | @fieldju | |


The Gradle Lambda Sam Plugin is released under the Apache License, Version 2.0

You can’t perform that action at this time.