Quick Start

Get your first drift scan running in under 5 minutes.

TL;DR

1. Sign in with GitHub → controlinfra.com
2. Settings → Add AI API key (Anthropic or OpenAI)
3. Add Repository → Select repo → Add AWS credentials
4. Click Scan → View results

Step-by-Step

1. Sign In (30 seconds)

Go to controlinfra.com and click "Get Started". Authorize with GitHub.

2. Configure AI (1 minute)

Navigate to Settings and add your API key:

For Anthropic (Recommended):

Provider: Anthropic
API Key: sk-ant-api03-xxxxx

For OpenAI:

Provider: OpenAI
API Key: sk-xxxxx

3. Add Repository (2 minutes)

Click "Add Repository" and fill in:

Repository: your-org/terraform-infrastructure
Working Directory: /  # or /infrastructure, /terraform, etc.

# AWS Credentials
AWS Access Key ID: AKIAXXXXXXXX
AWS Secret Access Key: xxxxxxxxxxxxxxxx
AWS Region: us-east-1

4. Run Scan (1-2 minutes)

Click the Scan button on your repository. The scan will:

1. Clone your repo
2. Initialize Terraform
3. Run terraform plan
4. Detect and categorize drift
5. Analyze with AI

5. Review Results

No Drift? 🎉 Your infrastructure is in sync!

Drift Detected? Each drift shows:

• What changed
• Why it matters (AI analysis)
• How to fix it

Example Output

┌─────────────────────────────────────────────────────────┐
│ Scan Complete: 3 drifts detected                        │
├─────────────────────────────────────────────────────────┤
│ 🔴 HIGH   aws_security_group.web                        │
│    Change: Inbound rule added (port 22 from 0.0.0.0/0) │
│    Cause:  Manual console change for SSH debugging     │
│    Fix:    Remove rule or update Terraform            │
├─────────────────────────────────────────────────────────┤
│ 🟡 MEDIUM aws_instance.api                              │
│    Change: Instance type changed (t3.micro → t3.small) │
│    Cause:  Likely scaled up due to performance needs   │
│    Fix:    Update instance_type in Terraform          │
├─────────────────────────────────────────────────────────┤
│ 🟢 LOW    aws_s3_bucket.logs                            │
│    Change: Tag added (Environment: production)         │
│    Cause:  Manual tagging for cost allocation          │
│    Fix:    Add tag to Terraform configuration         │
└─────────────────────────────────────────────────────────┘

What's Next?

• Fix drift: Click on any drift to see AI-generated fix code
• Create PR: Auto-generate a pull request with fixes
• Schedule scans: Set up automatic daily/weekly scans
• Add more repos: Monitor your entire infrastructure

Need Help?

• Detailed Getting Started Guide
• Understanding Drift Detection
• Configuring AWS Credentials