> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudthinker.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Infrastructure Management

> Unified infrastructure management — resources, topology, cost, security, and compliance across AWS, GCP, and Azure

CloudThinker's Infrastructure module gives you a unified operational picture of every cloud resource you own — and the AI agents to act on it. Instead of switching between AWS Console, CloudWatch, Terraform state, and spreadsheets, you get one place to discover, analyze, optimize, and govern your entire cloud estate.

***

## The Problem

Modern cloud infrastructure sprawls across multiple accounts, regions, and providers. Teams have no single source of truth for what's running, what it costs, whether it's secure, or how it's connected. The result:

| Problem                       | Reality                                                                         |
| ----------------------------- | ------------------------------------------------------------------------------- |
| **Invisible resources**       | Resources provisioned for projects that ended — still running, still billed     |
| **No dependency map**         | When something breaks at 3 AM, nobody knows what depends on what                |
| **Reactive security**         | Misconfigurations discovered in audits or breach notifications, not proactively |
| **Point-in-time assessments** | Well-Architected reviews happen once a year, findings go stale immediately      |
| **Manual operations**         | Engineers spend hours on repetitive cost reviews, security checks, and tagging  |

***

## What's Included

<CardGroup cols={2}>
  <Card title="Resources" icon="cubes" href="/guide/infrastructure/resources">
    Live inventory of every cloud asset — discover, filter, tag, and act on resources across AWS, GCP, and Azure
  </Card>

  <Card title="Topology" icon="diagram-project" href="/guide/infrastructure/topology">
    Live dependency map of your infrastructure — trace service relationships for faster incident root cause analysis
  </Card>

  <Card title="CloudKeepers" icon="radar" href="/guide/infrastructure/cloudkeepers">
    Autonomous CostOps and SecurityOps pilots that run 24/7 — catch drift, waste, and misconfigurations before they become incidents
  </Card>

  <Card title="Assessment" icon="clipboard-check" href="/guide/infrastructure/assessment">
    Automated Well-Architected assessment across all 6 pillars — findings with implementation steps, not just scores
  </Card>

  <Card title="Analytics" icon="chart-mixed" href="/guide/infrastructure/analytics">
    Unified health, performance, and cost signals correlated across all connected clouds
  </Card>

  <Card title="Plan" icon="list-check" href="/guide/infrastructure/plan">
    Turn assessment findings and agent recommendations into tracked, actionable work items
  </Card>
</CardGroup>

***

## How the Pieces Fit Together

<Steps>
  <Step title="Discover">
    [Resources](/guide/infrastructure/resources) continuously scans your connected cloud accounts and builds a live inventory of everything running — EC2, RDS, Lambda, GKE, Azure VMs, and 58+ resource types. Nothing is invisible.
  </Step>

  <Step title="Map">
    [Topology](/guide/infrastructure/topology) builds a live dependency graph from your discovered resources — showing which services call which databases, which load balancers front which clusters, and what the blast radius of any failure would be.
  </Step>

  <Step title="Monitor continuously">
    [CloudKeepers](/guide/infrastructure/cloudkeepers) runs autonomous [CostOps](/guide/infrastructure/cloudkeepers) and [SecurityOps](/guide/infrastructure/cloudkeepers) pilots on a daily schedule — surfacing new drift, waste, and misconfigurations with plain-language findings and remediation playbooks.
  </Step>

  <Step title="Assess deeply">
    [Assessment](/guide/infrastructure/assessment) runs an automated Well-Architected review across Cost, Security, Reliability, Performance, Operational Excellence, and Sustainability — producing prioritized findings with implementation steps.
  </Step>

  <Step title="Analyze trends">
    [Analytics](/guide/infrastructure/analytics) correlates utilization, performance, and cost signals across all clouds — answering questions like "is this latency spike cost-related or resource-contention-related?" without switching tools.
  </Step>

  <Step title="Track and act">
    [Plan](/guide/infrastructure/plan) captures findings from Assessments and CloudKeepers into a tracked work list — so recommendations move from identified to implemented with approval workflows and audit trails.
  </Step>
</Steps>

***

## The Agents Behind Infrastructure

| Agent                              | Infrastructure Role                                                                |
| ---------------------------------- | ---------------------------------------------------------------------------------- |
| [**Alex**](/guide/agents/alex)     | Cost analysis, right-sizing, reserved capacity, multi-cloud optimization           |
| [**Oliver**](/guide/agents/oliver) | Security posture, IAM audits, compliance evidence, misconfiguration detection      |
| [**Kai**](/guide/agents/kai)       | Kubernetes cluster health, pod efficiency, autoscaling, node optimization          |
| [**Tony**](/guide/agents/tony)     | Database performance, query optimization, connection pool analysis                 |
| [**Anna**](/guide/agents/anna)     | Cross-domain coordination — combines findings from all agents into unified reports |

All agents operate on the same connected infrastructure, so [Alex](/guide/agents/alex) and [Oliver](/guide/agents/oliver) can correlate a cost spike with a security misconfiguration in the same investigation.

***

## Quick Start

```bash theme={null}
# Discover all resources across your cloud accounts
@alex show me all resources in production

# Get a current health overview
@alex #dashboard infrastructure health across all accounts

# Run continuous guardrails
@alex configure CostOps pilot to run daily at 9 AM

# Assess your architecture
@alex run Well-Architected assessment on production environment

# Investigate a dependency
@anna show topology for payment-service with health overlay
```

***

## What's Next

<CardGroup cols={2}>
  <Card title="Connect Your Cloud" icon="plug" href="/guide/connections/overview">
    Link AWS, GCP, Azure, Kubernetes, and databases to activate all infrastructure capabilities
  </Card>

  <Card title="CloudKeepers" icon="radar" href="/guide/infrastructure/cloudkeepers">
    Start with continuous autonomous guardrails — the fastest path to ongoing visibility
  </Card>

  <Card title="Cost Optimization" icon="piggy-bank" href="/guide/cost-optimization/overview">
    Deep dive into the cost analysis and recommendation engine
  </Card>

  <Card title="Deep Response Engine" icon="triangle-exclamation" href="/guide/incident/overview">
    Use topology and analytics together for faster root cause analysis during incidents
  </Card>
</CardGroup>