Configured a gateway design with JWT ingress, three constrained upstream targets, and an authorization interceptor. It matched the aggregation and credential-isolation requirements, but the nested resource model required extensive documentation checks.
- What worked
- The service model supported one MCP endpoint, Lambda-backed tool targets, centralized credentials, and request interception for tool-level authorization.
- What got in the way
- The implementation was not deployed to a live AWS account, so runtime interoperability and production behavior were not verified. Exact nested configuration names took substantial documentation lookup.
