The Serverless Framework – Build applications on AWS Lambda and other next-gen cloud services, that auto-scale and only charge you when they run. This lowers the total cost of running and operating your apps, enabling you to build more and manage less.
The Serverless Framework is a command-line tool that uses easy and approachable YAML syntax to deploy both your code and cloud infrastructure needed to make tons of serverless application use-cases. It's a multi-language framework that supports Node.js, Typescript, Python, Go, Java, and more. It's also completely extensible via over 1,000 plugins that can add more serverless use-cases and workflows to the Framework.
Actively maintained by Serverless Inc.
npm install -g serverless
The Serverless Framework deploys to your own AWS account. You'll need to enable Serverless Framework to deploy to your AWS account by giving it access. Here is a guide to help you set up your credentials securely
A "Service" is the Framework's project or app concept. You can create one from scratch or select an existing template by running.
Go through the onboarding flow and then navigate into the newly created directory.
Use this when you have made changes to your Functions, Events or Resources in
serverless.yml or you simply want to deploy all changes within your Service at the same time.
Use this to quickly upload and overwrite your AWS Lambda code on AWS, allowing you to develop faster.
serverless deploy function -f hello
Invokes an AWS Lambda Function on AWS and returns logs.
serverless invoke -f hello -l
Invokes an AWS Lambda Function on your local machine and returns logs.
serverless invoke local -f hello -l
Open up a separate tab in your console and stream all logs for a specific Function using this command.
serverless logs -f hello -t
Removes all Functions, Events and Resources from your AWS account.
We love our contributors! Please read our Contributing Document to learn how you can start working on the Framework yourself.
Serverless is licensed under the MIT License.
All files located in the node_modules and external directories are externally maintained libraries used by this software which have their own licenses; we recommend you read them, as their terms may differ from the terms in the MIT License.
You can read the v0.5.x documentation at readme.io.