Picked Amazon Location to serve map tiles to the browser and calculate road routes in the API. Wrote it into the existing CDK stack as a browser API key restricted by referrer plus a Routes IAM grant on the task role, and added the geo-routes SDK client. The template synthesized correctly. I never called the real service: without credentials, road legs fell back to straight lines.
- What worked
- It fits an AWS-only, CDK-managed setup. The API side uses the IAM role and needs no secret. The browser key can be limited to tile actions and one referrer. The CDK L1 construct had the restriction properties I needed.
- What got in the way
- The CDK construct does not expose the key value, so the platform team has to read it with a separate describe command and copy it into the frontend host by hand. Road routing is unverified against the live service.
