Runtimes

Runtimes represent execution environments hosting agent microservices and framework runners (such as Google Agent Engine or Cloud Run API services).

Aegis connects to runtimes via standard Discovery contract endpoints, allowing platform administrators to discover deployed agents, monitor container health, and inspect runtime versions centrally.

---

Supported Runtime Types

Aegis supports the following runtime types during registration:

Runtime Type	UI Label	Code Identifier	Description
Agent Engine	Agent Engine	agent-engine	Managed Google Cloud Agent Engine execution environment.
API Container	API	cloud-run	Cloud Run or HTTP API container service exposing Aegis discovery contracts.

---

Supported Environments

When registering a runtime, assign one of the following target environments:

• Development (dev)
• Staging (staging)
• Production (prod)

---

Registering a Runtime (4-Step Wizard)

1. Navigate to Agent Workspace > Runtimes in the Aegis Console.
2. Click + Register Runtime to open the wizard:

Step 1: Basic Info

• Name (Slug): Unique identifier (lowercase letters, numbers, hyphens, 2-63 chars, e.g. agent-engine-prod).
• Display Name: Friendly title (e.g. Production Agent Engine).
• Type: Select Agent Engine (agent-engine) or API (cloud-run).
• Environment: Select dev, staging, or prod.

Step 2: Connection Settings

• Base URL: Service base URL (must start with http:// or https://, e.g., https://my-runtime-xxxx.a.run.app).
• Health Check Path: Endpoint path for health probes (default /health).
• Agents Discovery Path: Path to agent metadata contract (leave empty if not supported).
• Authentication:
  • GCP Service Account OIDC (gcp-sa): Enter Service Account Email.
  • API Key (api-key): Enter API Key / Secret (stored securely in Secret Manager).
  • None (none): Public or unauthenticated endpoint.

Step 3: Test Connection

Aegis verifies the Base URL, checks latency, and validates the Aegis Runtime Contract.

Step 4: Confirm & Import Agents

Review runtime summary (version, latency, authentication status) and select auto-discovered agents to import into your Aegis workspace.

---

Health Status Monitoring

Aegis background probes periodically check registered runtimes:

Status	Color	Description
Healthy	Green	Health probes respond HTTP 200 OK and discovery contract is valid.
Degraded	Yellow	High latency or partial agent discovery warnings.
Unreachable	Red	Connection timeout or HTTP 5xx error from runtime service.