Configuring and Deploying AWS Lambda: Step-by-Step Guide

1. Fork and clone this repo: https://github.com/diggerhq/gitlab-webhook-lambda.
2. If necessary, update the serverless.yml file in the cloned repository. This file contains configuration settings for the Lambda function and can be customized to suit your requirements.
3. Save the GITLAB_TOKENto the SSM (Systems Manager) parameter store. You can choose any path for storing the token, but ensure that the serverless.yml file is updated accordingly if you deviate from the default path. For example, save the GITLAB_TOKENto ssm:/gitlab-dev-webhook-handler/dev/GITLAB_TOKEN.
4. Do the same for SECRET_TOKEN, update serverless.yml if needed and save token value to ssm parameter (for example ssm:/gitlab-dev-webhook-handler/dev/SECRET_TOKEN)
5. Make sure that your AWS credentials are properly configured in the command-line interface (CLI). This ensures that you have the necessary permissions to deploy the Lambda function.
6. Run the command npm run build in the root directory of the cloned repository. This command will build the necessary artifacts for the Lambda function.
7. Finally, run the command npm run deploy in the same root directory. This will initiate the deployment process for the Lambda function using the configuration specified in the serverless.yml file.

Notes:

• Group Access Tokens (https://docs.gitlab.com/ee/user/group/settings/group_access_tokens.html) are not supported at the moment, only Project Access Tokens (https://docs.gitlab.com/ee/user/project/settings/project_access_tokens.html)
• One Lambda can handle webhooks for multiple GitLab Projects (repos)
• GITLAB_TOKEN is a JSON with a list of maps with project id and token. For example:

[
    {"project": "46465722", "token": "glpat-1212232311"}, 
    {"project": "44723537": "token": "glpat-2323232323"}
]