A city open-data team needs a partner system to pull a bulk GIS feed with rate limits, while citizens still sign in to a separate account portal. Which auth approach fits each audience?
Select an answer to reveal the explanation.
Short Explanation
Partners pulling bulk open data are machines—API keys plus usage plans throttle them cleanly. Citizens logging into the portal are people—Cognito owns that identity. Do not mash the two patterns together.
Full Explanation
API Gateway API keys with usage plans suit machine-to-machine or partner bulk access where identity is the calling system and quotas matter. End-user citizen authentication remains Cognito (or similar IdP) flows. IAM passwords for browsers, one shared flyer key, or forcing interactive Cognito for batch jobs confuse user auth with system access controls.