HTTP v2 API

The rest-v2 starter composes an HttpApiStack around AtfHttpApi — API Gateway’s leaner, cheaper HTTP API. The example-http-simple project is the reference: an API surface and nothing else.

The route list

All v2 routes are HttpApiLambdaConfig entries. This is the full route list from example-http-simple, included from source — all six verbs, one public route, one default-JWT route, and the greedy /{proxy+} case unique to v2:

export const httpApiConfigs: HttpApiLambdaConfig[] = [
  healthCheckConfig,
  getItemConfig,
  createItemConfig,
  updateItemConfig,
  patchItemConfig,
  deleteItemConfig,
  proxyConfig,
];

The v2 auth matrix

HTTP API v2 supports jwt | lambda | iam | none. It maps from the same authoring vocabulary as REST — cognito → jwt, custom → lambda — but has no native API keys (use a usage-plan-free pattern or a Lambda authorizer instead). The JWT authorizer needs the Cognito client id as its audience, which the stack reads from SSM (cognito/userPoolClientId).

Why choose v2

HTTP API v2 is lower-cost and lower-latency than REST v1, with a smaller feature set. Reach for it when you don’t need REST-only features (request/response validation models, API keys with usage plans, WAF-on-the-REST-stage). For the full-breadth surface, use REST v1.

Where to go next

• AtfHttpApi for props and defaults.
• The Auth Matrix for how the modes map between v1 and v2.