Serverless - AWS Node.js Typescript
This project has been generated using the aws-nodejs-typescript
template from the Serverless framework.
For detailed instructions, please refer to the documentation.
Installation/deployment instructions
Depending on your preferred package manager, follow the instructions below to deploy your project.
Requirements: NodeJS
lts/fermium (v.14.15.0)
. If you're using nvm, runnvm use
to ensure you're using the same Node version in local and in your lambda's runtime.
Using NPM
- Run
npm i
to install the project dependencies - Run
npx sls deploy
to deploy this stack to AWS
Using Yarn
- Run
yarn
to install the project dependencies - Run
yarn sls deploy
to deploy this stack to AWS
Test your service
This template contains a single lambda function triggered by an HTTP request made on the provisioned API Gateway REST API /getCityInfo/{city}
route with GET
method.
- requesting any other path than
/getCityInfo
with any other method thanGET
will result in API Gateway returning a403
HTTP error code - sending a
GET
request to/getCityInfo
with a payload will result in API Gateway returning a403
HTTP status code
⚠️ As is, this template, once deployed, opens a public endpoint within your AWS account resources. Anybody with the URL can actively execute the API Gateway endpoint and the corresponding lambda. You should protect this endpoint with the authentication method of your choice.
Locally
In order to test the getCityInfo function locally, run the following command:
npx sls invoke local -f getCityInfo
if you're using NPMyarn sls invoke local -f getCityInfo
if you're using Yarn
Check the sls invoke local command documentation for more information.
Remotely
Copy and replace your url
- found in Serverless deploy
command output - and city
parameter in the following curl
command in your terminal or in Postman to test your newly deployed application.
curl --location --request GET 'https://myApiEndpoint/dev/getCityInfo/newyork'
Template features
Project structure
The project code base is mainly located within the src
folder. This folder is divided in:
functions
- containing code base and configuration for your lambda functionslibs
- containing shared code base between your lambdas
.
├── src
│ ├── functions # Lambda configuration and source code folder
│ │ ├── getCityInfo
│ │ │ ├── handler.ts # `getCityInfo` lambda source code
│ │ │ ├── index.ts # `getCityInfo` lambda Serverless configuration
│ │ │ ├── mock.json # `getCityInfo` lambda input parameter, if any, for local invocation
│ │ │ └── schema.ts # `getCityInfo` lambda input event JSON-Schema
│ │ │
│ │ └── index.ts # Import/export of all lambda configurations
│ │
│ └── libs # Lambda shared code
│ └── apiGateway.ts # API Gateway specific helpers
│ └── handlerResolver.ts # Sharable library for resolving lambda handlers
│ └── lambda.ts # Lambda middleware
│
├── package.json
├── serverless.ts # Serverless service file
├── tsconfig.json # Typescript compiler configuration
├── tsconfig.paths.json # Typescript paths
└── webpack.config.js # Webpack configuration
3rd party libraries
- json-schema-to-ts - uses JSON-Schema definitions used by API Gateway for HTTP request validation to statically generate TypeScript types in your lambda's handler code base
- middy - middleware engine for Node.Js lambda. This template uses http-json-body-parser to convert API Gateway
event.body
property, originally passed as a stringified JSON, to its corresponding parsed object - @serverless/typescript - provides up-to-date TypeScript definitions for your
serverless.ts
service file
Advanced usage
Any tsconfig.json can be used, but if you do, set the environment variable TS_NODE_CONFIG
for building the application, eg TS_NODE_CONFIG=./tsconfig.app.json npx serverless webpack