API Gateway and Lambda architecture

1. Map the request

Your browser sends GET /hello. A Lambda function produces the greeting.

What connects that request to the function?

An HTTP API route with a Lambda integration.

A route chooses an integration using the method and path. The function supplies the response.

GET /hello now maps to the Lambda integration in the model.

RouteKey: "GET /hello"
Target: "integrations/greeting"

2. Add an identity check

The /profile endpoint should require a valid token from your identity provider.

Which feature checks that token at an HTTP API?

A JWT authorizer configured for the expected issuer and audience.

Routing selects a destination; authorization decides whether the request may reach it.

Requests must pass the configured token checks before the integration runs.

AuthorizationType: "JWT"
JwtConfiguration: { Issuer: "https://issuer.example", Audience: ["your-app"] }

3. Fix a mismatched route

You defined GET /hello, but the client sends POST /hello. Assume there is no matching default route.

Where should you inspect first?

The request method and the API route key.

The route includes both method and path. Confirm the contract before changing the function.

The client and route agree on GET /hello.

Client: GET /hello
Route:  GET /hello
Then inspect integration logs if the request still fails.

Practice, then check your understanding

In the interactive tour, make each decision before seeing the outcome. Wrong answers receive coaching, and replay gives you a fresh attempt without duplicating earned XP.

Read the official AWS documentation for service behavior and production details.