Skip to content

an AWS Lambda function to Proxy calls to MailChimp API Subscription without exposing the "all mighty" API-Keys through the App

Notifications You must be signed in to change notification settings

spawn-guy/ait-mch-lambda

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

19 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ait-mch-lambda

an AWS Lambda function to Proxy calls to MailChimp APIv3 Subscription without exposing the "all mighty" API-Keys

The function expects application/json body payload as you would send it to MailChimp APIv3 directly. Even though the API-Gateway is configured to accept ANY HTTP methods - it is easier to attach application/json body to POST, PUT, PATCH methods

Installation

  • Install dependencies with yarn install
  • ZIP index.js, node_modules
  • Deploy AWS Lambda function with "upoad zip"
  • Configure Environment variables as shown in .env.example
MAILCHIMP_KEY=YOUR-API-KEY
MAILCHIMP_LISTID=YOUR-MAILCHIMP-LIST-ID
  • Configure triggers API Gateway: API: Create a new API, Security: Open with API Key
  • use Resulting API Endpoint with x-api-key header.

About

an AWS Lambda function to Proxy calls to MailChimp API Subscription without exposing the "all mighty" API-Keys through the App

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published