Rewrite Jenkins Configuration in Lambda?

[PaulDuvall]

If we can run the Jenkins configuration in Lambda, we wouldn't need to launch a "transient" EC2 instance (it actually doesn't get terminated) that's not currently in a VPC. The relevant questions/resources that need be solved are:

-Passing dynamic arguments to the Lambda function
-Performing a git clone into the /tmp directory on the Lambda "instance"
-Performing a token/replace of the Jenkins configuration file in Node.js. This is currently performed in sed. It might still be performed in sed via spawnSync, etc.?
-Uploading files to S3
-Would we need the Pipeline Store anymore (probably since Lambda needs to get the information downstream somehow)?