Lambda based serverless runner
Inspired by the description (below) of an existing GitLab CI user
create a fully serverless shared runner using AWS step functions to facilitate the stages of the pipeline with lambdas facilitating logic where necessary. The runner would give you your choice of lambda environments in which to execute your stages (e.g. Node 6.10.3, Java 1.8, golang, etc. based on what kinds of lambda environments AWS offers). Each stage is kicked off in its own lambda while S3 is used for caching and artifacts
problem, benefits, and/or goals
integration with least-privileged AWS IAM roles at build/deploy time. k8s runner is not sufficient because kube2iam is a clunky fit for this use case
all this can be done via webhooks & GitLab API rather than implementing a runner, but we lose artifact storage. artifacts can be retrieved via the API, but not stored. Thus we can't accommodate 100% of runner functionality through a webhook
Arrange discovery call with requestor and CI team confirm use case and discuss collaboration opportunities.