lift VS aws-apigateway-integrations

The template utilizes the lift plugin to leverage AWS CDK and expand Serverless' functions to avoid all the yak-shaving at the beginning. One can always tweak the parameters afterward, be it from the serverless.yml configuration file or directly from the AWS console.

Such implementation opens up a lot of new possibilities: a functionless RESTful API where the only code is configuration-only IaC is not out of reach anymore and can help team achieve cheaper, more robust code base with minimal efforts. Such implementation is currently under discussion within Lift project where your feedbacks on the implementation are highly valued.

Not yet, we're considering this: https://github.com/getlift/lift/pull/52 Any feedback on this is appreciated, ideally in the pull request -> we use that to measure interest. We try to judge which features to implement based on community feedback.

One way to improve this is to allow the use of imperative language and tools people are used to in the triptych serverless stack to generate such template. With this goal in mind, I started a CDK Construct library, called aws-apigateway-integrations, aiming at simplifying AWS service integration definition, following @aws-cdk/aws-apigatewayv2-integrations module footsteps.