Knowledge Base

Create and manage knowledge bases to enhance your AI agents with organizational knowledge, documents, and procedures

Give your AI agents access to your organizational knowledge by uploading documents or crawling websites. Your agents can then reference this information to provide better, more contextual responses.

---

The problem with generic AI

Generic AI models know AWS best practices — but they don’t know your AWS environment. They don’t know that your company policy requires all S3 buckets to use SSE-KMS with a specific key ARN. They don’t know that your disaster recovery RTO is 4 hours, not the AWS-recommended 1 hour. They don’t know your incident response procedure mandates an Opsgenie alert before any remediation action.

The result: generic AI recommendations that conflict with your policies, contradict your existing documentation, or miss company-specific context that every senior engineer knows.

Knowledge Base solves this. By connecting your runbooks, policies, compliance documents, and architecture documentation, CloudThinker agents operate with your organization’s institutional knowledge — not just general cloud best practices.

---

How it compares to generic RAG

Approach	Generic AI	CloudThinker Knowledge Base
Company policies	Unknown	Indexed and referenced in every relevant response
Custom runbooks	Not available	Automatically pulled when relevant
Architecture context	Generic best practices	Your specific design decisions and constraints
Compliance requirements	Standard frameworks	Your specific audit requirements and evidence formats
Incident procedures	Generic steps	Your company’s exact escalation paths and tools

Source type	What it does
Document Upload	Add PDFs, Word docs, and text files to create knowledge repositories
Web Crawling	Automatically index websites, wikis, and documentation sites

---

Quick setup

1. Create Knowledge Base

   Go to Knowledge in CloudThinker and click “Create Knowledge Base”

2. Choose Type

   Select Document Upload or Web Crawler based on your content source

3. Configure Settings

   • Name: Give it a descriptive name
   • Description: Brief overview of the content
   • Access: Choose who can use this knowledge base
4. Add Content

   Upload documents or set up web crawling (see sections below)

---

Document upload

Supported files

• Text: TXT, Markdown, RTF
• Office: Word (.docx), PowerPoint (.pptx), Excel (.xlsx)
• PDF: Adobe PDF files
• Web: HTML, XML, JSON

How to upload

Single File

1. Click “Upload Document”
2. Choose your file (max 50MB)
3. Add title and tags
4. Click “Upload”

Multiple Files

1. Drag and drop up to 100 files
2. Or upload a ZIP file
3. Add batch metadata
4. Click “Process All”

---

Web crawling

Basic setup

1. Enter Website URL

   Provide the starting webpage URL to crawl

2. Set Limits

   • Depth: How many clicks deep (1-10)
   • Pages: Maximum pages to crawl (100-10,000)
3. Choose Schedule

   • One-time: Single crawl
   • Daily: Update every 24 hours
   • Weekly: Weekly updates
   • Manual: Only when you trigger it

Common examples

• Documentation sites (GitBook, Confluence)
• Company wikis
• Help centers and FAQs
• GitHub repositories

---

Using knowledge bases

Access modes

Mode	Behavior
Always Available (automatic)	Agents automatically use this knowledge in all conversations
Manual Search (on-demand)	Agents only use when you ask with #kb command

Agent commands

# Search any knowledge base
@alex #kb find AWS cost optimization strategies

# Search specific knowledge base
@tony #kb:database-guide PostgreSQL backup procedures

# Let agents decide when to use knowledge (Always mode)
@oliver analyze this security incident
# Oliver automatically references security procedures

Agent examples

Alex - Cloud Engineer

Knowledge Types:

• AWS documentation and guides
• Cost optimization playbooks
• Infrastructure procedures

Example:

@alex #kb find EC2 cost savings
→ References uploaded cost optimization guide
→ Provides specific recommendations

Oliver - Security Engineer

Knowledge Types:

• Security policies and procedures
• Compliance documentation
• Incident response playbooks

Example:

@oliver #kb security incident response
→ References uploaded incident procedures
→ Provides step-by-step guidance

Tony - Database Engineer

Knowledge Types:

• Database administration guides
• Performance tuning documentation
• Backup and recovery procedures

Example:

@tony #kb PostgreSQL performance tuning
→ References database optimization guide
→ Suggests specific improvements

---

Best practices

Content organization

Document structure (make it searchable):

• Use clear headings (H1, H2, H3)
• Include table of contents
• Add relevant keywords
• Use bullet points and lists

Tagging (smart organization):

• Use consistent tag names
• Include functional tags (security, database, aws)
• Add priority levels (critical, reference)
• Include department/team tags

Maintenance tips

• Review and update content monthly
• Remove outdated documents
• Monitor which content gets used most
• Test search functionality regularly

---

Quick examples

Example 1: Company procedures

Name: "Operations Procedures"
Type: Document Upload
Content: 
  - Employee handbook (PDF)
  - IT policies (Word docs)
  - Emergency procedures (PDF)
Access: Always Available
Agents: All agents can reference

Example 2: Technical documentation

Name: "AWS Documentation"
Type: Web Crawler
URL: "https://docs.aws.amazon.com/"
Schedule: Weekly updates
Access: Manual (#kb command)
Agents: Alex (primary), others as needed

Example 3: Security policies

Name: "Security Compliance"
Type: Document Upload
Content:
  - SOC 2 checklist (PDF)
  - Security policies (Multiple PDFs)
  - Incident templates (Word)
Access: Manual (sensitive content)
Agents: Oliver (full access), others (limited)

---

Getting started checklist

1. Plan Your Knowledge

   • Identify key documents and websites
   • Decide on naming conventions
   • Choose access levels for each knowledge base
2. Create Your First KB

   • Create knowledge base in CloudThinker
   • Upload 3-5 important documents OR set up web crawling
   • Add proper tags and descriptions
   • Test search functionality
3. Configure Agents

   • Set knowledge base access for each agent
   • Test manual search with #kb commands
   • Configure “Always Available” for critical knowledge
   • Train your team on usage commands
4. Monitor & Improve

   • Check which content gets used most
   • Update outdated information
   • Add new knowledge based on team needs
   • Gather feedback and optimize

---

Troubleshooting

Agents can't find information

Solutions:

• Check if agent has access to the knowledge base
• Verify knowledge base is set to “Always Available” or use #kb command
• Improve document titles and add more keywords
• Test search with different terms

Documents won't upload

Solutions:

• Check file size (max 50MB per file)
• Ensure file type is supported
• Verify document isn’t password-protected
• Try uploading one file at a time

Web crawling not working

Solutions:

• Verify the website URL is accessible
• Check if website blocks crawlers (robots.txt)
• Start with smaller page limits
• Try crawling a single page first

---

Next steps

Success Tips:

• Start small with your most important documents
• Use clear, descriptive names for everything
• Test search functionality before going live
• Train your team on the #kb command syntax

🚀 Create Knowledge Base

Get Started Now

Create your first knowledge base and start uploading content

🤖 Configure Agents

Setup AI Agents

Configure your agents to use your knowledge bases effectively