lambda-proxy

My personal Rust proxy with AWS Lambda. You may fork this repository and follow the instructions in Setup.

Usage

POST / (returns the GET responses of the provided endpoints)

Parameters

name	type	data type	description
endpoints	required	Vec<String>	an array of GET endpoints

Responses

http code	content-type	response
200	text/plain	JSON Object
400	text/plain	No body found
400	text/plain	Error parsing body: <error>

Example cURL

curl $LAMBDA_PROXY_URL -H 'Content-Type: application/json' -d \
'{
  "endpoints": [
    "https://account.battleon.com/charpage/details?id=53251829"
  ]
}'

Example TypeScript

import { config } from '@/config'

export const get_request_with_proxy = async <T>(...endpoints: string[]): Promise<T[]> => {
  const request = await fetch(config.VITE_PROXY_ENDPOINT, {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      endpoints: endpoints
    })
  })

  const response: string[] = await request.json()
  return response.map((res) => JSON.parse(res))
}


const response = await getRequestWithProxy('https://account.battleon.com/charpage/details?id=53251829')
response.map(console.log)

Setup

The following instructions uses the GitHub and AWS CLI to setup this proxy. You only need to follow these steps once.

Role

Create a AWS role.

aws iam create-role \
  --role-name $AWS_ROLE_NAME \
  --assume-role-policy-document \
  '{"Version": "2012-10-17","Statement": [{ "Effect": "Allow", "Principal": {"Service": "lambda.amazonaws.com"}, "Action": "sts:AssumeRole"}]}'

Attach the AWSLambdaBasicExecutionRole policy to your created role.

aws iam attach-role-policy \
  --role-name $AWS_ROLE_NAME \
  --policy-arn arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole

Function

Get your AWS account ID.

aws sts get-caller-identity --query "Account" --output text

Create a AWS Lambda function with the provided.al2 runtime and x86_64 architecture. See why here.

aws lambda create-function \
  --function-name lambda-proxy \
  --handler bootstrap \
  --runtime provided.al2 \
  --role arn:aws:iam::$AWS_ACCOUNT_ID:role/$AWS_ROLE_NAME

Additional Configuration

Add a Lambda function URL and keep the output URL safe. Learn more here.

I prefer using Lambda Function URLs for speed, but you can use an API Gateway if you know what you are doing.

aws create-function-url-config --function-name lambda-proxy --auth-type NONE --cors \
'{
  "AllowMethods": ["POST"], \
  "AllowOrigins": ["*"], \ # You should be using specific origins instead
}'

Workflow

Add the LAMBDA_FUNCTION_NAME variable to the repository.

gh api /repos/$GITHUB_USERNAME/lambda-proxy/actions/variables \
  -X POST \
  -H "Accept: application/vnd.github+json" \
  -f name='LAMBDA_FUNCTION_NAME' \
  -f value='lambda-proxy'

Add the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY secrets to the repository.

gh secret set AWS_ACCESS_KEY_ID --repos lambda-proxy --body $AWS_ACCESS_KEY_ID
gh secret set AWS_SECRET_ACCESS_KEY --repos lambda-proxy --body $AWS_SECRET_ACCESS_KEY

Start the CI/CD workflow.

gh workflow run main.yml