This getting started series is written by the serverless developer advocate team @AWSCloud. It has been designed for developers who know how to code but are new to serverless. Follow along with blog posts, code samples, and practical exercises to learn how to build serverless applications from your local Integrated development environment (IDE).
This repository is split into folders. Each folder has a corresponding blog post on the AWS serverless Compute blog. Read the blogs posts and refer back to the code samples in this repository:
| Blog Post | Code |
|---|---|
| Intro to serverless Learn why developers need serverless technologies and which challenges serverless technologies help to solve. You deploy a simple serverless application to your AWS account that connects Slack to GitHub and see first-hand why serverless technologies sparks joy for developers. |
/Part_1 |
| The business logic Learn where that business logic exists within the serverless application. You see how to extend the application by editing the business logic and learn about some of the AWS services involved. |
/Part_2 |
| The front door See how to access business logic by creating a front door to your serverless application with Amazon API Gateway. You extend the example serverless application to process an additional GitHub webhook URL. Finally, you see how Serverless applications help to reduce complexity and code by decoupling business logic from routing logic. |
/Part_3 |
| Local developer workflow See how the developer workflow for building serverless applications differs to a traditional developer workflow. Use a test harness to run business logic locally before deploying to an AWS account, and test against live cloud services as you build. |
/Part_4 |
| Sandbox developer account How to deploy your business logic to a Lambda function in a sandboxed developer account. You are introduced to IAM policies, which control precisely what each Lambda function can do within the AWS Cloud. You learn that CloudWatch provides a unified view of logs for all AWS resources. |
/Part_5 |
By the end of this 3-part series you will have built a serverless application that connects GitHub and Slack together. The app will post a message to Slack when a GitHub repository has been starred or a push made. The final output of which looks like the following:
 |
 |
|---|
To deploy this application, you need:
- The AWS Serverless Application Model (AWS SAM CLI) installed with an AWS account set up.
- A GitHub account, and a repository with admin permissions.
- A Slack account with the ability to create apps.
Refer to blog post part 1 to deploy the app:
See CONTRIBUTING for more information.
This library is licensed under the MIT-0 License. See the LICENSE file.........