v1.2.0 — Gateway Split + Deployment Stability + Performance Optimization
Expanded from 7 to 8 Gateways with major deployment stability improvements. Container responses are 54% faster (50s → 23s), achieving 104/104 test pass rate.
8 Gateways · 10 Routes · 104/104 Tests Passed · 93% Classification Accuracy · Container 54% Speed Improvement
Gateway Split: Infra → Network + Container
The v1.1.0 Infra Gateway (41 tools) contained too many tools, so it was split into Network and Container domains.
| Item | Before (Single Infra) | After (Split) |
|---|---|---|
| Gateway | 1 (Infra, 41 tools) | 2 (Network 17 + Container 24) |
| Container Response Time | ~50s | ~23s (54% improvement) |
| Tool Selection Accuracy | LLM selects from 41 | Selects from 24 |
| Route Structure | 7 Gateways, 9 Routes | 8 Gateways, 10 Routes |
Having the LLM select from 17 (Network) or 24 (Container) tools is faster and more accurate than selecting from all 41. Notably, errors where network tools were incorrectly selected for container questions have been eliminated.
Deployment Stability Improvements
Added error handling and automatic detection logic to deployment scripts.
| Script | Improvement |
|---|---|
06a-setup-agentcore-runtime.sh | run_or_fail helper + AWS credential preflight check |
06b-setup-agentcore-gateway.sh | Bulk creation of 8 Gateways (reflecting Network/Container split) |
07-setup-cloudfront-auth.sh | CloudFront auto-detection — CDK stack priority, ALB origin fallback |
| Steampipe connection | Password hardcoding → dynamic lookup via steampipe service status |
Test Results: 104/104 Passed
Out of 104 questions, all 104 passed, with route classification at 93% accuracy and content verification at 99% accuracy.
| Item | Result |
|---|---|
| Questions Passed | 104/104 (100%) |
| Route Classification Accuracy | 93% (97/104) |
| Content Verification Accuracy | 99% (103/104) |
| Average Response Time | 27s |
Key Bug Fixes
| Issue | Cause | Fix |
|---|---|---|
| EKS access entry failure | Used arn:aws:sts:: format | Converted to arn:aws:iam:: format |
| Cognito custom domain error | Missing SupportedIdentityProviders | Added parameter |
| AgentCore permission error | Insufficient permissions | Added bedrock-agentcore:* permissions |
| K8s PVC query failure | JSONB serialization error | Applied ::text casting in k8s.ts |
Returning JSONB columns (spec, status) directly from Kubernetes tables causes serialization errors.
Use SELECT spec::text or spec->>'key' for conversion.