Ram Vennam rvennam

Workshop: Native AWS Bedrock AgentCore Routing with Solo Enterprise Agent Gateway v2.3.0

Overview

Solo Enterprise Agent Gateway v2.3.0 introduces native AWS Bedrock AgentCore backend support — no sidecar proxy, no custom container, no extra hop. The gateway signs requests with SigV4 using the correct bedrock-agentcore service name and routes A2A traffic directly to your AgentCore runtime agents.

In this workshop you will:

Install Enterprise Agent Gateway v2.3.0 on EKS
Configure IRSA so the gateway can call AgentCore natively

Production Observability, Alerting, and Scaling

This guide covers production-readiness for Enterprise AgentGateway: a complete metrics reference, recommended Prometheus alerting rules, horizontal pod autoscaling, graceful shutdown for long-lived AI connections, pod spreading, disruption budgets, and zero-downtime upgrades.

Metrics Reference

Enterprise AgentGateway exposes metrics from three components.

Install Agentgateway (Open Source)

In this workshop, you'll deploy the open-source Agentgateway and complete hands-on labs that showcase routing, observability, and Gen AI features.

Pre-requisites

Kubernetes > 1.30
Kubernetes Gateway API
helm package manager installed

Lab Objectives

Route to a Remote A2A Agent by Hostname

Pre-requisites

This lab assumes that you have completed the setup in 001 and 002

Lab Objectives

Route to a remote A2A agent by hostname (not IP address) through AgentGateway
Preserve full A2A protocol detection, including "protocol":"a2a" and a2a.method in access logs
Handle port and path differences on the remote agent
Validate A2A connectivity and observability through the gateway

Global Rate Limiting with External Redis

Lab Objectives

Deploy an external Redis instance separate from the built-in ext-cache
Configure the Enterprise AgentGateway rate limiter to use the external Redis via a deployment overlay
Apply global rate limiting to LLM routes using RateLimitConfig and EnterpriseAgentgatewayPolicy
Verify rate limit counters are stored in the external Redis

Overview

Configure Route to Remote A2A Agent

Pre-requisites

This lab assumes that you have completed the setup in 001 and 002

Lab Objectives

Deploy a mock A2A agent and expose it as a remote service
Route to the remote A2A agent through AgentGateway
Validate A2A connectivity through the gateway
Observe A2A traffic in access logs

Solo Enterprise for Agentgateway - Feature List

A comprehensive list of functional features available in Solo Enterprise for Agentgateway, categorized by LLM and MCP capabilities.

LLM Features

Multi-Provider Routing

Route to OpenAI

	apiVersion: v1
	kind: Namespace
	metadata:
	name: egress-direct
	labels:
	istio.io/dataplane-mode: ambient
	---
	apiVersion: v1
	kind: Namespace
	metadata:

	{
	"policies": [
	{
	"key": "backend/enterprise-agentgateway/aliases-policy:ai:enterprise-agentgateway/openai",
	"name": {
	"kind": "AgentgatewayPolicy",
	"name": "aliases-policy",
	"namespace": "enterprise-agentgateway"
	},
	"target": {

	{
	"workloads": [
	{
	"workloadIps": [
	"10.20.0.28"
	],
	"protocol": "TCP",
	"networkMode": "Standard",
	"uid": "//Pod/agentcore/agentcore-a2a-proxy-546cfdb7f9-t2tzf",
	"name": "agentcore-a2a-proxy-546cfdb7f9-t2tzf",