This project has been generated using the aws-nodejs-typescript template from the Serverless framework.
For detailed instructions, please refer to the documentation.
Depending on your preferred package manager, follow the instructions below to deploy your project.
Requirements: NodeJS For Windows:
lts/fermium (v.14.15.0)and for Linux:v.18.4.0. If you're using nvm, runnvm useto ensure you're using the same Node version in local and in your lambda's runtime.
- Run
npm ito install the project dependencies - Run
npx sls deployto deploy this stack to AWS
- Run
yarnto install the project dependencies - Run
yarn sls deployto deploy this stack to AWS
This template contains a single lambda function triggered by an HTTP request made on the provisioned API Gateway REST API /hello route with POST method. The request body must be provided as application/json. The body structure is tested by API Gateway against src/functions/hello/schema.ts JSON-Schema definition: it must contain the name property.
- requesting any other path than
/hellowith any other method thanPOSTwill result in API Gateway returning a403HTTP error code - sending a
POSTrequest to/hellowith a payload not containing a string property namednamewill result in API Gateway returning a400HTTP error code - sending a
POSTrequest to/hellowith a payload containing a string property namednamewill result in API Gateway returning a200HTTP status code with a message saluting the provided name and the detailed event processed by the lambda
⚠️ 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.
In order to test the hello function locally, run the following command:
npx sls invoke local -f hello --path src/functions/hello/mock.jsonif you're using NPMyarn sls invoke local -f hello --path src/functions/hello/mock.jsonif you're using Yarn
Check the sls invoke local command documentation for more information.
Copy and replace your url - found in Serverless deploy command output - and name parameter in the following curl command in your terminal or in Postman to test your newly deployed application.
curl --location --request POST 'https://myApiEndpoint/dev/hello' \
--header 'Content-Type: application/json' \
--data-raw '{
"name": "Frederic"
}'
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
│ │ ├── hello
│ │ │ ├── handler.ts # `Hello` lambda source code
│ │ │ ├── index.ts # `Hello` lambda Serverless configuration
│ │ │ ├── mock.json # `Hello` lambda input parameter, if any, for local invocation
│ │ │ └── schema.ts # `Hello` 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
- 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.bodyproperty, originally passed as a stringified JSON, to its corresponding parsed object - @serverless/typescript - provides up-to-date TypeScript definitions for your
serverless.tsservice file
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
Staging implementation for selecting slack user ids (through an environment variable) who will receive all the messages sent by daily or weekly messages.
For use in staging environment/ develop branch use the STAGING_IDS environment variable. If this variable does not exist or is empty the program runs normally. Copy the variable and add it (STAGING_IDS=<slackid>) to the .env file.
Multiple ids must be divided by , for example STAGING_IDS=xxxxxxx,xxxxxxx,xxxxxxx
- Click on a user profile within Slack.
- Click on "View full profile" in the menu that appears.
- Click the ellipses (three dots).
- Click on
Copy Member ID.