A public open-data JSON API needs API keys, throttling, and stage-based deploys in front of a simple CRUD Lambda backend. Which service should front the API?
Select an answer to reveal the explanation.
Short Explanation
Citizens need a front desk with a ticket window, rate limits, and a "dev vs prod" door—not a raw loading dock. API Gateway gives keys, throttling, and stages in front of Lambda CRUD. CloudFront or an ALB alone skip those API-management knobs; Direct Connect is the wrong front door for a public JSON API.
Full Explanation
A public open-data JSON API that needs API keys, throttling, and stage-based deploys in front of a simple CRUD Lambda backend should use Amazon API Gateway as the managed HTTP/REST front door. Gateway provides keys/usage plans, stage variables, throttling, and deployment promotion from municipal sandbox to public stages without rewriting Lambda. That is the standard developer-centric edge for HTTP APIs on AWS.
CloudFront alone with no API management layer caches and distributes but does not replace API key usage plans and stage-oriented API lifecycle the stem requires. An ALB pointed at Lambda lacks the same first-class API key/stage product features for public developer APIs. Direct Connect terminating citizen traffic into a private NLB is networking for hybrid connectivity, not a public open-data API front door.
Exam caveat: HTTP APIs versus REST APIs differ in features/cost; pick based on whether you need usage plans, API keys, and specific integrations. Throttling protects backends from scrape storms on popular datasets.
Operational check: put API Gateway in front of CRUD Lambda; issue API keys/usage plans for partners; deploy via stages; load-test throttles; and monitor 429s separately from 5xx application faults.