Over the past year, the Serverless Application Repository (SAR) service has improved a lot. I have grown to enjoy it more and more, and have contributed a few applications myself:
- lambda-janitor: cron job to delete old, unused versions of all Lambda functions in the region to free up storage space.
- auto-subscribe-log-group-to-arn: subscribes new and existing CloudWatch log groups to a Lambda function, Kinesis stream, or Firehose delivery stream by ARN.
- auto-set-log-group-retention: updates the retention policy for new and existing CloudWatch log groups to a specified number of days to reduce CloudWatch Logs cost.
However, CloudFormation does not natively support the
AWS::Serverless::Application resource type. Until recently, I had to use the SAM deployment framework in order to include a SAR app in my stack. That is, until the 1.41.0 release of the Serverless framework.
In this release, the Serverless framework has added support for CloudFormation’s Transform directive. This means we can use the same magic source (CloudFormation macros) that powers SAM!
To add a Serverless Repository app to your
serverless.yml you will need to:
Transform: AWS::Serverless-2016–10–31to the
resourcessection of your
serverless.yml. This enables a global macro that will run over the whole CloudFormation stack and transform special resources as necessary. In this case, it’ll transform
AWS::Serverless::Applicationresources into nested CloudFormation stacks.
- Add Serverless Repository apps as additional CloudFormation resources. These should have the resource type
For example, to include the
auto-subscribe-log-group-to-arn app as part of a serverless.yml, I will need the following:
And that’s it, that’s how you can include Serverless Repository apps in your
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Come learn about operational BEST PRACTICES for AWS Lambda: CI/CD, testing & debugging functions locally, logging, monitoring, distributed tracing, canary deployments, config management, authentication & authorization, VPC, security, error handling, and more.
You can also get 40% off the face price with the code ytcui.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong