Team C: Agent Card 설계

분석 대상

config.yaml — Agent Card 설정, /.well-known/agent-card.json 스키마

Agent Card란?

A2A 프로토콜에서 에이전트의 "명함"입니다. 다른 에이전트가 이 카드를 조회하여 어떤 에이전트에게 어떤 요청을 보낼지 결정합니다.

Connectivity Agent Card (config.yaml)

agent_card_info:
  agent_arn: arn:aws:bedrock-agentcore:us-east-1:xxx:runtime/agent-xxx
  agent_tags:
  - connectivity
  - troubleshooting
  - aws
  - dns
  - network-analysis
  - agentcore

agent_metadata:
  name: Connectivity_Troubleshooting_Agent
  description: "Routes requests to a Bedrock AgentCore runtime that provides
    DNS resolution and connectivity analysis capabilities"
  capabilities:
    push_notifications: true
    streaming: true
  supported_content_types:
  - text/plain
  version: 1.0.0

agent_skills:
  - id: dns_connectivity_troubleshooting
    name: "DNS Resolution and Connectivity Troubleshooting"
    description: "Resolves DNS hostnames to EC2 instance IDs and analyzes
      network connectivity with automated fix capabilities"
    examples:
    - "Check connectivity between app-frontend and app-backend using TCP on port 80"
    - "Resolve DNS hostname database.internal.com to instance ID"
    - "Fix connectivity issues by updating security group rules"
    tags:
    - dns-resolution
    - connectivity-analysis
    - network-troubleshooting
    - security-groups
    - automated-fixes

executor_config:
  stream: true
  request_timeout_s: 900  # 15분 타임아웃

server:
  default_host: 0.0.0.0
  default_port: 10003

Performance Agent Card

agent_metadata:
  name: Performance_Agent
  description: "Analyzes AWS network performance issues, sets up monitoring
    infrastructure, and provides insights"
  capabilities:
    push_notifications: true
    streaming: true

agent_skills:
  - id: analyze_network_performance
    name: "Network Performance Analysis"
    description: "Analyzes VPC Flow Logs, CloudWatch metrics, traffic mirroring,
      TCP performance, and network flow monitoring"
    examples:
    - "Analyze network performance for application with retransmission issues"
    - "Set up traffic mirroring for deep packet inspection"
    - "Fix the retransmission issues on the bastion server"
    tags:
    - performance
    - network-monitoring
    - vpc-flow-logs
    - traffic-mirroring
    - tcp-analysis

server:
  default_port: 10006

Agent Card 비교

항목	Connectivity Agent	Performance Agent
name	Connectivity_Troubleshooting_Agent	Performance_Agent
포트	10003	10006
스킬	DNS + 연결성 분석	성능 모니터링 + 수정
태그	dns, connectivity, security-groups	performance, vpc-flow-logs, tcp
타임아웃	900초	900초

/.well-known/agent-card.json 엔드포인트

# A2A 서버에서 자동 생성
# GET http://alb-url/.well-known/agent-card.json

# Collaborator Agent가 조회하는 방법:
card_resolver = A2ACardResolver(client, address)
card = await card_resolver.get_agent_card()
# card.name → "Connectivity_Troubleshooting_Agent"
# card.description → "Routes requests to..."
# card.skills → [{ id, name, description, tags }]

라우팅에서의 사용

# Collaborator의 시스템 프롬프트에 에이전트 정보 주입
available_agents = json.dumps({
    "name": card.name,
    "description": card.description
})
# → LLM이 이 정보를 보고 라우팅 결정

Cognito 인증 설정

agent_card_info:
  client_id: 77oddlg6kat5bhkmspdpl9hm7v
  discovery_url: https://cognito-idp.us-east-1.amazonaws.com/.../openid-configuration
  scope: netops-a2a-server/gateway:read netops-a2a-server/gateway:write

토론 질문

1. Agent Card의 tags와 skills가 실제 라우팅에 사용되나요, 아니면 사람을 위한 것인가요?

2. 새로운 에이전트를 추가할 때 최소한으로 필요한 Agent Card 필드는?

3. capabilities.streaming: true와 executor_config.stream: true의 차이는?

4. 에이전트 포트 번호(10003, 10006)는 어떻게 결정되나요?