lambda-handlers

A set of patterns for structuring AWS Lambda functions, which are small cloud programs run in response to events, using Middy middleware and AWS tooling.

In plain words
What is it for?
Use it when building or reviewing Node.js 22 Lambda handlers for API Gateway, including request parsing, CORS, error handling, and observability.
Why use it?
It helps keep handlers consistent while addressing startup time, memory, time limits, event formats, errors, logging, tracing, and metrics.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/goranerhartic/cursor-development-rules/lambda-handlers
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,952 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.01952
Opus 5 $0.00020 $0.00976
Sonnet 5 $0.00008 $0.00390
Haiku 4.5 $0.00004 $0.00195

Measured 2d ago against content hash ee753980a2f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

lambda-handlers scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/languages/aws-lambda/lambda-handlers.mdc · 297 lines

How it starts

The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lambda Handler Patterns

Overview

AWS Lambda functions require specific patterns to handle cold starts, memory constraints, timeouts, and concurrent executions efficiently.

Dependencies

Use Middy v7 and Node.js 22 runtime. Middy v7 has breaking changes from v5 (see upgrade guide).

pnpm add @middy/core@^7 @middy/http-json-body-parser@^7 @middy/http-error-handler@^7 @middy/input-output-logger@^7 @middy/http-cors@^7
pnpm add @aws-lambda-powertools/logger @aws-lambda-powertools/tracer @aws-lambda-powertools/metrics
pnpm add -D @types/aws-lambda esbuild

Base Handler Structure

Simple Handler

// src/functions/get-property/handler.ts

import type { APIGatewayProxyHandler, APIGatewayProxyResult } from "aws-lambda";
import { logger } from "@/shared/logger";

export const handler: APIGatewayProxyHandler = async (event, context) => {
  // Disable waiting for event loop to empty (faster cold starts)
  context.callbackWaitsForEmptyEventLoop = false;

  const propertyId = event.pathParameters?.propertyId;

  if (!propertyId) {
    return {
      statusCode: 400,
      body: JSON.stringify({ message: "Property ID is required" }),
    };
  }

  try {
    const property = await propertyService.findById(propertyId);

    if (!property) {
      return {
        statusCode: 404,
        body: JSON.stringify({ message: "Property not found" }),
      };
    }

    return {
      statusCode: 200,
      body: JSON.stringify(property),
    };
  } catch (error) {
    logger.error({ err: error, propertyId }, "Failed to get property");
    return {
      statusCode: 500,
      body: JSON.stringify({ message: "Internal server error" }),
    };
  }
};

Middleware Stack Setup

// src/shared/middleware/index.ts

import middy from "@middy/core";
import httpJsonBodyParser from "@middy/http-json-body-parser";
import httpErrorHandler from "@middy/http-error-handler";
import inputOutputLogger from "@middy/input-output-logger";
import httpCors from "@middy/http-cors";
import { injectLambdaContext } from "@aws-lambda-powertools/logger/middleware";
import { captureLambdaHandler } from "@aws-lambda-powertools/tracer/middleware";
import { logger } from "@/shared/logger";
import { tracer } from "@/shared/tracer";
import { correlationIdMiddleware } from "./correlation-id";
import { validationMiddleware } from "./validation";

export function createHandler<TEvent, TResult>(
  handler: (event: TEvent, context: Context) => Promise<TResult>
) {
  return middy(handler)
    .use(injectLambdaContext(logger, { clearState: true }))
    .use(captureLambdaHandler(tracer))
    .use(correlationIdMiddleware())
    .use(httpCors({ origin: "*", credentials: true })) // Real estate web app: allow frontend origin
    .use(inputOutputLogger({
      logger: (request) => logger.debug(request),
      awsContext: true,
    }))
    .use(httpJsonBodyParser())
    .use(httpErrorHandler({ logger: (error) => logger.error({ err: error }) }));
}

Read the full file on GitHub · 297 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 297 lines · 41 tokens per session scan A ee753980a2f0

Subscribe to this mod's changes

lambda-handlers is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 1,952 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.