Edit on github
Here is a list of all available properties in serverless.yml when the provider is set to aws.
serverless.yml
aws
service: name: myService awsKmsKeyArn: arn:aws:kms:us-east-1:XXXXXX:key/some-hash…
service: name: myService awsKmsKeyArn: arn:aws:kms:us-east-1:XXXXXX:key/some-hash
Variables allow users to dynamically replace config values in serverless.yml config.
They are especially useful when providing secrets for your service to use and when you are working with multiple stages.
If you are using AWS as a provider for your Service, all Resources are other AWS infrastructure resources which the AWS Lambda functions in your Service depend on, like AWS DynamoDB or AWS S3.
A Plugin is custom Javascript code that creates new or extends existing commands within the Serverless Framework. The Serverless Framework is merely a group of Plugins that are provided in the core. If you or your organization have a specific workflow, install a pre-written Plugin…
After the 0.5.6 release of Serverless we sat down with many contributors and users of the Framework to discuss the next steps to improve Serverless.
If you are using AWS as a provider, all functions inside the service are AWS Lambda functions.
All of the Lambda functions in your serverless service can be found in serverless.yml under the functions…
functions
The Serverless Framework needs access to your cloud provider’s account so that it can create and manage resources on your behalf.
This guide is for the Amazon Web Services (AWS) provider, so we’ll step through the process of setting up credential for…
The Serverless Framework was designed to provision your AWS Lambda Functions, Events and infrastructure Resources safely and quickly. It does this via a couple of methods designed for different types of deployments.
Every AWS Lambda function needs permission to interact with other AWS infrastructure resources within your account. These permissions are set via an AWS IAM Role which the Serverless Framework automatically creates for each Serverless Service, and is shared by all of your Functions. The…
Using the Serverless CLI tool, you can package your project without deploying it to AWS. This is best used with CI / CD workflows to ensure consistent deployable artifacts.
While the Serverless Architecture introduces a lot of simplicity when it comes to serving business logic, some of its characteristics present challenges for testing. They are:
A service is like a project. It's where you define your AWS Lambda Functions, the events that trigger them and any AWS infrastructure resources they require, all in a file called serverless.yml.
service
events
resources
Serverless is a Node.js CLI tool so the first thing you need to do is to install Node.js on your machine.
Go to the official Node.js website, download and follow the installation instructions to install Node.js…
Check out the following links for tutorial walkthroughs:
Or follow the steps below for creating & deploying a simple service and learning some…
Quick recommendations and tips for various processes.
serverless deploy
Simply put, events are the things that trigger your functions to run.
If you are using AWS as your provider, all events in the service are anything in AWS that can trigger an AWS Lambda function, like an S3 bucket upload, an SNS topic, and HTTP endpoints…