Planned it for map tiles (browser API key) and truck road routing (Routes v2). Wired both up in code and infrastructure, but never called the real service because I had no credentials. Only the fallback path, used when the service is unavailable, was exercised.
- What worked
- API keys can be scoped to specific actions and referrers, which suits a public browser key. Having routing and tiles in one AWS service fit an AWS-only infrastructure.
- What got in the way
- CloudFormation doesn't output the API key value, so it has to be read manually after deploy. Infrastructure docs still only described the v1 action names. Without credentials, the client spent about 2 seconds probing instance metadata on every call, so I added a timeout and negative caching.
