Supported providers
AWS
Agent:
CLI:
Services: EC2, Lambda, S3, RDS, ECS, EKS, CloudWatch, etc.
internal/aws/CLI:
awsServices: EC2, Lambda, S3, RDS, ECS, EKS, CloudWatch, etc.
GCP
Agent:
CLI:
Services: Compute Engine, Cloud Run, GKE, BigQuery, etc.
internal/gcp/CLI:
gcloudServices: Compute Engine, Cloud Run, GKE, BigQuery, etc.
Azure
Agent:
CLI:
Services: App Service, Cosmos DB, AKS, Functions, etc.
internal/azure/CLI:
azServices: App Service, Cosmos DB, AKS, Functions, etc.
Cloudflare
Agent:
CLI:
Services: Workers, KV, D1, R2, WAF, DNS, Zero Trust
internal/cloudflare/CLI:
wrangler / APIServices: Workers, KV, D1, R2, WAF, DNS, Zero Trust
How routing works
Clanker automatically detects which provider to use based on your question:Keyword detection
The routing system checks for provider-specific keywords:
- AWS:
ec2,lambda,s3,rds,cloudwatch,dynamodb - GCP:
gcloud,compute engine,cloud run,bigquery,gke - Azure:
azure,app service,cosmos db,aks,functions - Cloudflare:
cloudflare,workers,waf,dns,tunnel
LLM classification (if ambiguous)
If multiple providers are detected, an LLM classifies the question.See
internal/routing/classifier.go.Provider-specific features
AWS
The AWS agent uses the multi-agent architecture with semantic analysis:- Parallel agents: Log, Metrics, Infrastructure, Security, Performance, Cost, etc.
- Decision trees: Maps user intent to agent strategies
- Tool calling: LLM can execute AWS CLI operations directly
GCP
The GCP agent queries Google Cloud resources using thegcloud CLI:
- List Compute Engine instances
- Query Cloud Run services
- Inspect GKE clusters
- Check BigQuery datasets
- View Cloud Functions
Azure
The Azure agent queries Azure resources using theaz CLI:
- List App Services
- Query Cosmos DB accounts
- Inspect AKS clusters
- View Azure Functions
- Check storage accounts
Cloudflare
The Cloudflare agent routes to specialized sub-agents:WAF agent
WAF agent
Manages firewall rules, rate limiting, and DDoS protection.Keywords:
firewall, waf, rate limit, ddos, bot, security levelWorkers agent
Workers agent
Manages Workers, KV, D1, R2, Durable Objects, and Pages.Keywords:
worker, kv, d1, r2, pages, durable objectAnalytics agent
Analytics agent
Queries traffic, bandwidth, and performance metrics.Keywords:
analytics, traffic, bandwidth, requests, visitors, performance metricsZero Trust agent
Zero Trust agent
Manages Tunnels, Access apps, and policies.Keywords:
tunnel, access app, access policy, zero trust, cloudflared, warpDNS agent
DNS agent
Manages DNS records and zones.Keywords:
dns, record, zone, domainMaker mode: Multi-cloud plans
Maker mode supports all four providers for infrastructure automation:AWS plans
"provider": "aws" and aws CLI commands.
GCP plans
"provider": "gcp" and gcloud commands.
Azure plans
"provider": "azure" and az commands.
Cloudflare plans
"provider": "cloudflare" and wrangler commands.
Credential management
Clanker supports multiple credential sources:AWS
- AWS profiles
- Environment variables
- Backend API
Uses standard AWS profiles from
~/.aws/config:GCP
- Application Default Credentials
- Service account JSON
- Backend API
Uses
gcloud auth application-default login.Azure
- Azure CLI authentication
- Environment variables
- Backend API
Uses
az login credentials.Cloudflare
- API token
- Config file
- Backend API
Uses
CLOUDFLARE_API_TOKEN or CF_API_TOKEN env var.Force provider selection
Override automatic routing with explicit flags:Example workflows
Query across providers
Generate multi-cloud plans
Next steps
Natural language
Learn how Clanker interprets your questions
Maker mode
Generate infrastructure plans from natural language