Install dependencies:
npm install -g @microsoft/rush
Initialize the project:
| .pnp.* | |
| .yarn/* | |
| !.yarn/patches | |
| !.yarn/plugins | |
| !.yarn/releases | |
| !.yarn/sdks | |
| !.yarn/versions | 
| AWSTemplateFormatVersion: "2010-09-09" | |
| Description: My example codebuild template for pull requests | |
| Parameters: | |
| VPCStackName: | |
| Type: AWS::SSM::Parameter::Value<String> | |
| Default: /cloudformation/parameters/vpc/stackname | |
| Description: The name of the parent VPC networking stack that you created. Necessary | |
| to locate and reference resources created by that stack. | 
UPDATE (2021-03-31): I've posted an improved version of this guide with newer versions of the software.
I hate when my images turn out like this:
| import {Subject} from 'rxjs/Subject'; | |
| import {BehaviorSubject} from 'rxjs/BehaviorSubject'; | |
| import {Observable, ObservableInput} from 'rxjs/Observable'; | |
| import {concatMap, switchMap} from 'rxjs/operators'; | |
| enum QueueActions { | |
| RESET = 'RESET', | |
| ADD = 'ADD', | |
| } | 
| 'use strict'; | |
| exports.handler = (event, context, callback) => { | |
| // Get request and request headers | |
| const request = event.Records[0].cf.request; | |
| const headers = request.headers; | |
| // Configure authentication | |
| const authUser = 'user'; | |
| const authPass = 'pass'; | 
Your Service Worker script will need to import in Workbox and initialize it before calling any of the routes documented in this write-up, similar to the below:
importScripts('workbox-sw.prod.v1.3.0.js');
const workbox = new WorkboxSW();
// Placeholder array populated automatically by workboxBuild.injectManifest()This cheat sheet provides a detailed overview of the exposed lifecycle events and available commands (and entrypoints) of the Serverless framework, that can be hooked by plugins (internal and external ones). The document is structured by the commands invoked by the user.
Lifecycle events are shown as the globally available outer events (all providers) and sub lifecycle events that are provider specific in the called order. Currently only the AWS provider is shown. If you have information about the other provider,
A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."
An update by Paul Johnston (paul@roundaboutlabs.com), for a Serverless Architecture scenario. This assumes something akin to AWS Lambda + API Gateway + DynamoDB (c. 2016) Function as a Service (FaaS) solution as the basis for deployment rather than a cloud-based virtual server approach which the original paper was based upon. The FaaS solution implies each function is separately scalable and the database is inherently partitioned (assuming designed/built well).
If you agree/disagree, please fork and share with me on twitter @pauldjohnston.
I'm going to walk you through the steps for setting up a AWS Lambda to talk to the internet and a VPC. Let's dive in.
So it might be really unintuitive at first but lambda functions have three states.