serverless/docs/developing-plugins/building-provider-integrations.md

Building provider integrations

Integrating different infrastructure providers happens through the standard plugin system. Take a look at the "building plugins" documentation to understand how the plugin system works.

Provider specific plugins

You can add the providers name inside the constructor of your plugin. This makes it possible to only execute your plugins logic when the Serverless service uses the provider you've specified in your plugin.

Deployment

Infrastructure provider plugins should bind to specific lifecycle events of the deploy command to compile the function and their events to provider specific resources.

Deployment lifecycles

Let's take a look at the core deploy plugin and the different lifecycle hooks it provides.

The following lifecycle events are run in order once the user types serverless deploy and hits enter:

• deploy:initializeResources
• deploy:createProviderStacks
• deploy:compileFunctions
• deploy:compileEvents
• deploy:deploy

You, as a plugin developer can hook into those lifecycles to compile and deploy functions and events on your providers infrastructure.

Let's take a closer look at each lifecycle event to understand what its purpose is and what it should be used for.

deploy:initializeResources

This lifecycle should be used to load the basic resources the provider needs into memory (e.g. parse a basic resource template skeleton such as a CloudFormation template).

deploy:createProviderStacks

The purpose of the deploy:createProviderStacks lifecycle is to take the basic resource template which was created in the previous lifecycle and deploy the rough skeleton on the cloud providers infrastructure (without any functions or events) for the first time.

deploy:compileFunctions

Next up the functions inside the serverless.yaml file should be compiled to provider specific resources and stored into memory.

deploy:compileEvents

After that the events which are defined in the serverless.yaml file on a per function basis should be compiled to provider specific resources and also stored into memory.

deploy:deploy

The final lifecycle is the deploy:deploy lifecycle which should be used to deploy the previously compiled function and event resources to the providers infrastructure.

Amazon Web Services provider integration

Curious how this works for the Amazon Web Services (AWS) provider integration? Here are the steps the AWS plugins take to compile and deploy the service on the AWS infrastructure in detail.

The steps in detail

1. The serverless.yaml and serverless.env.yaml files are loaded into memory
2. A default AWS CloudFormation template is loaded (deploy:initializeResources)
3. The CloudFormation template is deployed to AWS (A S3 bucket for the service gets created) (deploy:createProviderStacks)
4. The functions of the serverless.yaml file are compiled to lambda resources and stored into memory (deploy:compileFunctions)
5. Each functions events are compiled into CloudFormation resources and stored into memory (deploy:compileEvents)
6. Old functions (if available) are removed from the S3 bucket (deploy:deploy)
7. The function code gets zipped up and is uploaded to S3 (deploy:deploy)
8. The compiled function and event resources are attached to the core CloudFormation template and the updated CloudFormation template gets redeployed (deploy:deploy)

The code

You may also take a closer look at the corresponding plugin code to get a deeper knowledge about what's going on behind the scenes.

The full AWS integration can be found in lib/plugins/aws.