Description
AgentCore Gateway HTTP runtime targets support an optional API schema. However, AWS documentation states that HTTP runtime agents are required provide this schema when using guardrails.
The CLI exposes --schema for gateway targets, but currently rejects it for --type http-runtime. Consequently, users cannot configure policy guardrails correctly for HTTP runtime targets.
Steps to Reproduce
Reproduce --schema validation rejection
- create HTTP runtime with a policy engine
- Add an HTTP runtime target while passing
--schema flag
Reproduce deploy failure
- create HTTP runtime with a policy engine
- Add an HTTP runtime target without passing
--schema flag
- Deploy the target and apply guardrail policies
- Attempt to invoke the target
Expected Behavior
- The CLI should accept a schema for HTTP runtime targets
- benign requests permitted by policy should succeed
Actual Behavior
- CLI rejects
--schema for HTTP runtime targets
- benign requests permitted by policy are rejected due to missing schema
CLI Version
No response
Operating System
macOS
Additional Context
- Accept and validate
--schema for http-runtime in CLI
- persist schema source in agentcore.json
- persist schema through deploy
Description
AgentCore Gateway HTTP runtime targets support an optional API schema. However, AWS documentation states that HTTP runtime agents are required provide this schema when using guardrails.
The CLI exposes --schema for gateway targets, but currently rejects it for
--type http-runtime. Consequently, users cannot configure policy guardrails correctly for HTTP runtime targets.Steps to Reproduce
Reproduce
--schemavalidation rejection--schemaflagReproduce deploy failure
--schemaflagExpected Behavior
Actual Behavior
--schemafor HTTP runtime targetsCLI Version
No response
Operating System
macOS
Additional Context
--schemafor http-runtime in CLI