Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/unitedeffects/sendgrid-lambda-proxy
This is a proxy to the sendgrid API that runs as a lambda function
https://github.com/unitedeffects/sendgrid-lambda-proxy
api-gateway express-js lambda lambda-functions sendgrid sendgrid-api serverless serverless-framework
Last synced: 4 days ago
JSON representation
This is a proxy to the sendgrid API that runs as a lambda function
- Host: GitHub
- URL: https://github.com/unitedeffects/sendgrid-lambda-proxy
- Owner: UnitedEffects
- License: mit
- Created: 2019-11-17T23:46:06.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2024-03-29T11:07:17.000Z (10 months ago)
- Last Synced: 2024-11-25T20:13:34.301Z (2 months ago)
- Topics: api-gateway, express-js, lambda, lambda-functions, sendgrid, sendgrid-api, serverless, serverless-framework
- Language: JavaScript
- Size: 415 KB
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# SendGrid API Lambda Proxy
Used to proxy SendGrid API request.
## Instructions
* Copy .env_ci to .env
* Change values for .env/env.qa.json, .env/env.dev.json, and .env/env.production.json as required for your proxy
* yarn
* yarn build
* If you want to try it out locally, in src/index.js uncomment line 55 and comment line 56 (remember to undo this before deployment to aws)
* yarn start## Deploying
The environment json files configure your serverless.yaml file. The environment variable SLS_ENV determines which file is used. For example, to launch using your env.qa.json file, you would do as follows:
* SLS_ENV=qa yarn deploy
If this is the first time you're deploying, you'll need to create the custom domain in the API Gateway.
* SLS_ENV=qa sls create_domain
## Dependencies/Assumptions
* Assumes you have serverless installed
* Assumes you have serverless configured with AWS credentials to deploy lambda functions
* Assumes you have permissions to create a route53 entry, a custom domain in API Gateway, new Cloud Formation, and Lambda