Read the AgentCore developer guide pages on Gateway, Policy (Cedar), interceptors, Lambda targets, outbound OAuth and CloudTrail to design a gateway where calls carry the engineer's identity. Never deployed against a live account. The feature set fit the requirements well, but several key details had to be pieced together from many pages.
- What worked
- Gateway, Cedar-based policy, per-user OAuth token vault and request/response interceptors cover most of what an identity-aware, policy-gated tool endpoint needs. Example policies and the policy-conditions page were concrete and useful.
- What got in the way
- Docs were unclear about whether interceptors run before or after policy evaluation. Lambda targets don't receive the caller's identity, so I had to add a signed caller assertion myself. Cedar tag semantics for array claims such as groups were ambiguous. The Cedar schema the service generates isn't published, so I could only validate policies against an approximation.
