api-gateway-http-api

Project rules for building AWS HTTP APIs with API Gateway version 2, a service that routes web requests to backend code. They cover CDK setup, JWT or Lambda authentication, request formats, routes, CORS, and request parameters.

In plain words
What is it for?
They are for creating Lambda-backed APIs with AWS CDK, configuring authentication and routes, handling query strings and path parameters, and setting cross-origin access.
Why use it?
They help developers choose the documented HTTP API setup and use matching request types and configuration. This reduces mistakes when connecting API Gateway to Lambda functions.

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/api-gateway-http-api
Clone the repo
git clone --depth 1 https://github.com/GoranErhartic/cursor-development-rules

Made for: Cursor.

Per session 46 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,536 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.00046 $0.01536
Opus 5 $0.00023 $0.00768
Sonnet 5 $0.00009 $0.00307
Haiku 4.5 $0.00005 $0.00154

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

Security

Grade A, and why

api-gateway-http-api 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/api-gateway-http-api.mdc · 188 lines

How it starts

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

API Gateway HTTP API (v2)

Overview

HTTP API (v2) is the recommended API Gateway type for most Lambda-backed APIs: lower cost, lower latency, and native JWT authorizers. Use payload format version 2.0 and type APIGatewayProxyEventV2 in handlers.

When to Use HTTP API vs REST API

Use HTTP API (v2) Use REST API (v1)
New APIs, JWT/Cognito auth API keys, request validation, WAF v1
Lower cost, simpler Complex request/response mapping
Real estate web app (Cognito) Legacy or specific v1 features

Dependencies

pnpm add -D @types/aws-lambda
# CDK: aws-cdk-lib (HttpApi, HttpLambdaIntegration, HttpJwtAuthorizer)

CDK HttpApi with JWT Authorizer

// cdk/lib/stacks/http-api-stack.ts

import { Stack, StackProps } from "aws-cdk-lib";
import { Construct } from "constructs";
import {
  HttpApi,
  HttpMethod,
  PayloadFormatVersion,
  HttpRouteKey,
} from "aws-cdk-lib/aws-apigatewayv2";
import { HttpLambdaIntegration } from "aws-cdk-lib/aws-apigatewayv2-integrations";
import { HttpJwtAuthorizer } from "aws-cdk-lib/aws-apigatewayv2-authorizers";
import { StandardLambda } from "../constructs/lambda-function";
import { Table } from "aws-cdk-lib/aws-dynamodb";

interface HttpApiStackProps extends StackProps {
  dataTable: Table;
  idempotencyTable: Table;
  userPoolId: string;
  userPoolClientId: string;
}

export class HttpApiStack extends Stack {
  public readonly httpApi: HttpApi;

  constructor(scope: Construct, id: string, props: HttpApiStackProps) {
    super(scope, id, props);

    const jwtAuthorizer = new HttpJwtAuthorizer("JwtAuthorizer", props.userPoolId, {
      identitySource: ["$request.header.Authorization"],
      jwtAudience: [props.userPoolClientId],
    });

    this.httpApi = new HttpApi(this, "RealEstateHttpApi", {
      apiName: "real-estate-http-api",
      corsPreflight: {
        allowOrigins: [process.env.CORS_ORIGIN ?? "https://app.example.com"],
        allowMethods: [HttpMethod.GET, HttpMethod.POST, HttpMethod.PUT, HttpMethod.DELETE],
        allowHeaders: ["Content-Type", "Authorization", "X-Correlation-Id"],
        allowCredentials: true,
      },
    });

    const getPropertyHandler = new StandardLambda(this, "GetProperty", {
      entry: "src/functions/get-property/handler.ts",
      handler: "handler",
      memorySize: 256,
      timeoutSeconds: 10,
      environment: { DYNAMODB_TABLE_NAME: props.dataTable.tableName },
    });
    props.dataTable.grantReadData(getPropertyHandler);

    // Public route (no auth)
    this.httpApi.addRoutes({
      path: "/properties/{propertyId}",
      methods: [HttpMethod.GET],
      integration: new HttpLambdaIntegration(
        "GetPropertyIntegration",
        getPropertyHandler,
        { payloadFormatVersion: PayloadFormatVersion.V2_0 }
      ),
    });

    // Protected route (JWT required)
    const createListingHandler = new StandardLambda(this, "CreateListing", {
      entry: "src/functions/create-listing/handler.ts",
      handler: "handler",
      memorySize: 512,
      timeoutSeconds: 30,
      environment: {
        DYNAMODB_TABLE_NAME: props.dataTable.tableName,
        IDEMPOTENCY_TABLE_NAME: props.idempotencyTable.tableName,
      },
    });
    props.dataTable.grantReadWriteData(createListingHandler);
    props.idempotencyTable.grantReadWriteData(createListingHandler);

    this.httpApi.addRoutes({
      path: "/listings",
      methods: [HttpMethod.POST],
      integration: new HttpLambdaIntegration(
        "CreateListingIntegration",
        createListingHandler,
        { payloadFormatVersion: PayloadFormatVersion.V2_0 }
      ),
      authorizer: jwtAuthorizer,
    });
  }
}

Read the full file on GitHub · 188 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 · 188 lines · 46 tokens per session scan A 5a2b1d26c49a

Subscribe to this mod's changes

api-gateway-http-api is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 1,536 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.