Go to file
burnettk ff3936d2df
update poetry lock to allow make zip to work
2024-07-11 12:49:36 -04:00
connector_proxy_lambda_demo Docker updates (#4) 2023-04-06 13:00:46 -04:00
tests Lambda demo (#1) 2023-02-15 09:40:25 -05:00
.gitignore Docker updates (#4) 2023-04-06 13:00:46 -04:00
.tool-versions update poetry lock to allow make zip to work 2024-07-11 12:49:36 -04:00
Dockerfile Docker updates (#4) 2023-04-06 13:00:46 -04:00
LICENSE Initial commit 2023-02-14 19:16:24 -05:00
Makefile Docker updates (#4) 2023-04-06 13:00:46 -04:00
README.md Update README.md 2023-04-06 17:02:38 -04:00
deploy-integrate.md Deploying and Integrating write up (#5) 2023-04-06 17:00:10 -04:00
docker-compose.yml Docker updates (#4) 2023-04-06 13:00:46 -04:00
poetry.lock update poetry lock to allow make zip to work 2024-07-11 12:49:36 -04:00
pyproject.toml Docker updates (#4) 2023-04-06 13:00:46 -04:00

README.md

connector-proxy-lambda-demo

Demo showing how a serverless connector proxy could be deployed as an AWS Lambda Function for use by Spiff Arena.

Requires docker and docker compose.

To deploy from the AWS Lambda Console:

In the root of this project run:

make zip

Create a new lambda function with a publicly available function url. Choose upload from zip and select connector_proxy_lambda_demo.zip from the root directory of this demo. Click on the function url link above the code editor and your connector proxy is live.

For more information and details about how to integrate with SpiffArena please see the Deployment and Integration Guide.

Local Testing

make start

Will start the lambda development server locally on port 9000. Two example requests are baked in to the Makefile.

make request-index
make request-commands

These will confirm the lambda function is responding correctly locally. When done:

make stop

If you just want to build the docker image:

make build

I have not gone through the motions yet of uploading to ECR/configuring a lamba with the container image.

Some notes

This is a demo and only has an http get and post connector currently. If this were used outside of a demo it would be nice to be able to opt out of the flask portions of spiffworkflow-proxy or extract the PluginService to reduce the deployment size. It would also be beneficial to extract the lambda routing logic into its own package.