A simple RPC client that can be used to debug AWS lambda functions locally that are written in Go. In the AWS SDK for the Go runtime, Lambda functions support the ability to run as RPC servers, making them very easy to invoke in a multitude of different environments.
Note that when you run your AWS Lambda function locally on your machine, a huge benefit to doing it this way, is that if your Lambda uses any other AWS service clients (i.e DynamoDB, S3, Secrets Manager, etc.), you can actually debug those live deployed cloud based resources without doing anything else. No 3rd party libraries, no frameworks, no containers. The only catch is that you have to have your AWS shared credentials file updated in such a way that the session that the Lambda creates can be authenticated.
go build -ldflags=-w -o "lrpc.exe"- Must have a lambda to test against
- Must have the
_LAMBDA_SERVER_PORTenvironment variable set to a value of9988in either your local configuration or in your lambda source code beforelambda.Start(handler)is invoked (i.e.os.Setenv("_LAMBDA_SERVER_PORT", "9988")).
First, you'll need to run your lambda function by invoking the lambda.Start(handler) method (i.e. go run <module-name>), this will start the RPC server for that particular lambda function and it will begin to run as a server.
./lrpc.exe -e "./events/apigateway-authorizer.json" -o "resp.json"
LAMBDA RESPONSE:
{
"policyDocument": {
"Statement": [
{
"Action": [
"execute-api:Invoke"
],
"Effect": "Deny",
"Resource": [
"*"
]
}
],
"Version": "2012-10-17"
},
"principalId": "apigateway.amazonaws.com"
}
Event used in the above example (stored locally in "./events/apigateway-authorizer.json")
{
"type": "TOKEN",
"authorizationToken": "incoming-client-token",
"methodArn": "arn:aws:execute-api:us-east-1:123456789012:example/prod/POST/{proxy+}"
}
The following arguments can be passed to the CLI to invoke the help documentation:
-
-h
-
--h
-
-help
-
--help