Skip to main content

AI Assistant

The AI Assistant is powered by Amazon Bedrock AgentCore, enabling you to analyze and manage AWS infrastructure using natural language.

AI Assistant

Architecture

AI Intent Routing

11-Route Classification

The AI Assistant analyzes questions and automatically routes them to the most appropriate destination.

Routing Table

PriorityRouteGatewayToolsDescription
1code--Python code execution, calculations, visualization
2networkNetwork17VPC, TGW, VPN, Flow Logs, Reachability
3containerContainer24EKS, ECS, Istio troubleshooting
4iacIaC12CDK, CloudFormation, Terraform
5dataData24DynamoDB, RDS, ElastiCache, MSK
6securitySecurity14IAM, policy simulation, security summary
7monitoringMonitoring16CloudWatch, CloudTrail
8costCost9Cost analysis, forecasting, budgets
9datasource-7 DSExternal observability (Prometheus/Loki/Tempo/ClickHouse/Jaeger/Dynatrace/Datadog) — natural language → query
10aws-dataOpsSQLResource lists/status (Steampipe SQL)
11generalOps9General AWS questions, documentation search

Route Details

1. code - Code Interpreter

Used when Python code execution is required.

Example questions:

  • "Visualize AWS cost data as a chart"
  • "Calculate random number statistics"
  • "Create code to parse JSON data"

2. network - Network Gateway

Used for VPC networking, Transit Gateway, VPN, and traffic analysis.

Key tools:

  • list_vpcs, get_vpc_network_details, describe_network
  • list_transit_gateways, get_tgw_routes, get_all_tgw_routes
  • list_vpn_connections, list_network_firewalls
  • analyze_reachability, query_flow_logs

Example questions:

  • "Analyze TGW routes"
  • "Diagnose VPN connection status"
  • "Check if EC2 instances can communicate"
  • "Query denied traffic from VPC Flow Logs"

3. container - Container Gateway

Used for EKS, ECS, and Istio service mesh troubleshooting.

Key tools:

  • list_eks_clusters, get_eks_vpc_config, get_eks_insights
  • ecs_resource_management, ecs_troubleshooting_tool
  • istio_overview, list_virtual_services, check_sidecar_injection

Example questions:

  • "Diagnose EKS cluster status"
  • "Check if ECS service is healthy"
  • "Check Istio sidecar injection status"

4. iac - IaC Gateway

Used for Infrastructure as Code related tasks.

Key tools:

  • validate_cloudformation_template, check_cloudformation_template_compliance
  • search_cdk_documentation, cdk_best_practices
  • SearchAwsProviderDocs, terraform_best_practices

Example questions:

  • "Tell me CDK best practices"
  • "Analyze CloudFormation stack error"
  • "Search for Terraform VPC module"

5. data - Data Gateway

Used for AWS database and streaming services.

Key tools:

  • list_tables, describe_table, query_table, dynamodb_data_modeling
  • list_db_instances, describe_db_instance, execute_sql
  • list_cache_clusters, elasticache_best_practices
  • list_clusters (MSK), msk_best_practices

Example questions:

  • "Show DynamoDB table details"
  • "Check RDS instance status"
  • "Tell me ElastiCache best practices"

6. security - Security Gateway

Used for IAM and security-related analysis.

Key tools:

  • list_users, list_roles, list_policies
  • list_access_keys, simulate_principal_policy
  • get_account_security_summary

Example questions:

  • "Show IAM user list with Access Key status"
  • "Simulate if this role can access S3"
  • "Give me an account security summary"

7. monitoring - Monitoring Gateway

Used for CloudWatch and CloudTrail analysis.

Key tools:

  • get_metric_data, analyze_metric, get_active_alarms
  • describe_log_groups, execute_log_insights_query
  • lookup_events, lake_query

Example questions:

  • "Show EC2 CPU usage trends"
  • "Query recent IAM events from CloudTrail"
  • "Show active alarm list"

8. cost - Cost Gateway

Used for cost analysis and optimization.

Key tools:

  • get_cost_and_usage, get_cost_and_usage_comparisons
  • get_cost_forecast, get_pricing
  • list_budgets

Example questions:

  • "Analyze this month's costs"
  • "Compare costs by service"
  • "Forecast next month's costs"

9. datasource - External observability (natural language → query)

Used for questions about connected external observability platforms (Prometheus/Loki/Tempo/ClickHouse/Jaeger/Dynatrace/Datadog).

How it works:

  1. Claude converts the natural-language question into the platform's query language (PromQL/LogQL/TraceQL/SQL)
  2. Runs the query against datasources that pass the SSRF allowlist
  3. Analyzes the result and responds

Example questions:

  • "Show the 5xx trend for the payment service" (Prometheus)
  • "Find error logs in the last hour" (Loki)
  • "Analyze slow traces" (Tempo/Jaeger)

10. aws-data - Bedrock + Steampipe SQL

Used for resource lists, status, and count queries.

Processing flow:

  1. Claude Sonnet generates SQL from the question
  2. Query executes directly on Steampipe pg Pool
  3. Bedrock analyzes results and generates response

Example questions:

  • "Show EC2 instance list"
  • "Check how many S3 buckets we have"
  • "Analyze VPC network configuration"
  • "Summarize all resources"

11. general - Ops Gateway

Used for general AWS questions, documentation search, and best practices.

Key tools:

  • search_documentation, read_documentation
  • recommend, list_regions, get_regional_availability

Example questions:

  • "Check if this service is available in Seoul region"
  • "What's the difference between ECS and EKS?"
  • "Recommend a serverless architecture"

Multi-Route

When a single question spans multiple domains, it's classified into up to 3 routes for parallel processing.

Examples:

"Analyze VPC security groups and costs"
→ ["network", "cost"]

"Do a security check and verify IAM users"
→ ["security"]
Multi-Route Response

During multi-route processing, responses from each Gateway are synthesized into a single unified answer.

SSE Streaming

Responses are streamed via Server-Sent Events (SSE).

Progress Indicator

Analyzing question...
→ Calling Network Gateway...
→ Generating response...

Streaming Events

EventDescriptionData
statusProgress status messages{ step, message }
chunkReal-time text streaming{ delta: string }
doneComplete response data{ content, route, usedTools, ... }
errorError messages{ message }

Streaming Modes

Three streaming modes are automatically selected based on the response path:

ModeApplied PathMethod
Real StreamingMulti-route synthesisBedrock Converse API — token-level immediate delivery
Simulated StreamingSingle Gateway response50-char chunks + 15ms delay — typing effect
Direct Streamingaws-data (Steampipe+Bedrock)Bedrock native streaming
Multi-Route Synthesis Streaming

When synthesizing results from 2-3 parallel routes, the Bedrock Converse Stream API (ConverseStreamCommand) streams the synthesis process in real-time. Users can see the synthesized results as they are generated.

Tool Usage Display

MCP tools used are displayed at the bottom of the response.

Tools: list_vpcs, get_vpc_network_details, analyze_reachability
Queried: aws_vpc, aws_vpc_subnet, aws_vpc_security_group

Conversation History

Session Context

The current session's conversation is maintained, enabling follow-up questions.

User: "Show VPC list"
AI: (VPC list response)

User: "Tell me details about the default VPC from that list"
AI: (References previous context to provide default VPC details)

Saved History

Conversation history is saved per user and can be viewed in the panel at the bottom of the screen.

  • Saved info: Question, response summary, route, response time, timestamp
  • Retention period: 365 days
  • Search: Search previous conversations by keyword

Session Statistics

Current session statistics are displayed at the bottom of the screen.

5 queries  │  avg 3.2s  │  100%  │  aws-data:3  security:1  network:1
  • queries: Total question count
  • avg: Average response time
  • Success rate: Ratio of successful responses
  • Route distribution: Call count by route

Related follow-up questions are suggested by route after each response.

RouteExample Suggestions
security"Show IAM user list with Access Key status"
network"Show VPC subnets and route tables"
container"Check EKS node CPU/memory usage"
cost"Compare costs by service"

Next Steps