Arckit Aws Research

• Look in: projects/{project}/external/
• File types: PDF (.pdf), Word (.docx), Markdown (.md), CSV (.csv)
• What to extract: Current AWS usage, cost reports, Well-Architected review findings, migration assessments
• Examples: aws-cost-report.csv, well-architected-review.pdf, migration-assessment.docx

User prompt: If no external AWS docs found but they would improve recommendations, ask: "Do you have any existing AWS cost reports, Well-Architected reviews, or migration assessments? Place them in projects/{project}/external/ and re-run, or skip."

Important: This agent works without external documents. They enhance output quality but are never blocking.

• Citation traceability: When referencing content from external documents, follow the citation instructions in .arckit/references/citation-instructions.md. Place inline citation markers (e.g., [PP-C1]) next to findings informed by source documents and populate the "External References" section in the template.

Step 2: Read Available Documents

Find the project directory in projects/ (user may specify name/number, otherwise use most recent). Scan for existing artifacts:

MANDATORY (warn if missing):

• ARC-*-REQ-*.md in projects/{project}/ — Requirements specification
  • Extract: FR (compute/AI), NFR-P (performance), NFR-SEC (security), INT (integration), DR (data) requirements for AWS service matching
  • If missing: STOP and report that $arckit-requirements must be run first
• ARC-000-PRIN-*.md in projects/000-global/ — Architecture principles
  • Extract: Cloud policy, approved services, compliance requirements, security standards
  • If missing: warn user to run $arckit-principles first

RECOMMENDED (read if available, note if missing):

• ARC-*-STKE-*.md in projects/{project}/ — Stakeholder analysis
  • Extract: User personas, scalability expectations, compliance stakeholders

OPTIONAL (read if available, skip silently if missing):

• ARC-*-RISK-*.md in projects/{project}/ — Risk register
  • Extract: Technology risks, vendor lock-in risks, compliance risks
• ARC-*-DATA-*.md in projects/{project}/ — Data model
  • Extract: Data storage needs, data governance, retention requirements

What to extract from each document:

• Requirements: FR/NFR/INT/DR IDs for AWS service category mapping
• Principles: Cloud-first policy, approved platforms, compliance constraints
• Stakeholders: Scale expectations, compliance requirements

Detect if UK Government project (look for "UK Government", "Ministry of", "Department for", "NHS", "MOD").

Step 3: Read Template

• Read .arckit/templates/aws-research-template.md for output structure

Step 4: Extract Requirements for AWS Mapping

Read the requirements document and identify AWS service needs across these categories. Use the MCP tools to dynamically discover the best-fit AWS services for each requirement — do not limit yourself to the examples below:

• Compute (FR-xxx, NFR-P-xxx, NFR-S-xxx): e.g. containers, web hosting, serverless, VMs, batch processing
• Data (DR-xxx, NFR-P-xxx): e.g. relational, NoSQL, caching, search, data warehouse, data lake
• Integration (INT-xxx): e.g. API management, messaging, workflow orchestration, external system connectivity
• Security (NFR-SEC-xxx): e.g. identity, secrets management, network security, threat detection
• AI/ML (FR-xxx): e.g. foundation models, ML platforms, conversational AI

Use search_documentation to discover which AWS services match each requirement rather than assuming a fixed mapping. AWS frequently launches new services and features — let the MCP documentation guide your recommendations.

Step 5: Research AWS Services Using MCP

Mode detection: Attempt a single search_documentation call. If it succeeds, continue in SUPERCHARGED mode using MCP tools as described below. If MCP tools are unavailable, switch to STANDALONE mode using these substitutions for ALL research in this step:

For each requirement category, use MCP tools extensively (or their STANDALONE equivalents):

Service Discovery:

• search_documentation: "[requirement] AWS service" for each category
• Follow up with read_documentation for detailed service pages

Service Deep Dive (for each identified service):

• read_documentation: Fetch full service docs from docs.aws.amazon.com
• Extract: features, pricing models, SLA, security features, integration capabilities

Regional Availability Check:

• get_regional_availability: Check every recommended service in eu-west-2 (London)
• Critical for UK Government projects — all services must be available in London region

Architecture Patterns:

• search_documentation: "AWS architecture [pattern type]"
• read_documentation: Fetch AWS Architecture Center reference architectures
• recommend: Get related content recommendations

Well-Architected Assessment (all 6 pillars):

• search_documentation: "AWS Well-Architected [pillar] [service]"
• Pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, Sustainability

Security Hub Mapping:

• search_documentation: "AWS Security Hub [control category]"
• Categories: AWS Foundational Security Best Practices, CIS Benchmark, PCI DSS, NIST 800-53

Code Samples:

• search_documentation: "AWS [service] CDK example", "AWS [service] CloudFormation template", "AWS [service] Terraform"

Step 6: UK Government Specific Research (if applicable)

• G-Cloud: Search Digital Marketplace for "Amazon Web Services", note framework reference
• Data Residency: Confirm eu-west-2 availability, check cross-region replication (eu-west-1 for DR)
• Classification: OFFICIAL = standard AWS, OFFICIAL-SENSITIVE = additional controls, SECRET = not available on public AWS
• NCSC: Reference AWS attestation against 14 NCSC Cloud Security Principles

Step 7: Cost Estimation

• search_documentation: "AWS [service] pricing" for each service
• Map requirements to service configurations
• Calculate based on projected usage with eu-west-2 pricing
• Include optimization: Reserved Instances, Savings Plans, Spot, Graviton, S3 Intelligent-Tiering

Step 7b: Government Implementation Patterns

Search govreposcrape for existing UK government implementations using the AWS services recommended above:

1. Search by service: For each recommended AWS service, query govreposcrape:
   • "[AWS service] UK government", "AWS [service] implementation"
   • Example: "AWS Lambda UK government", "Amazon DynamoDB government"
   • Use resultMode: "snippets" and limit: 5 per query
2. Note findings: For each relevant result:
   • Which department/organisation uses this service
   • Architecture patterns observed (serverless, containerised, etc.)
   • Common configurations or companion services
3. Include in output: Add a "Government Precedent" subsection to each service recommendation:
   • If precedent found: "[Org] uses [service] for [purpose]" — adds confidence to recommendation
   • If no precedent found: "No UK government precedent identified" — note as a consideration (not a blocker)

If govreposcrape tools are unavailable, skip this step silently and proceed.

Step 8: Generate Architecture Diagram

Create a Mermaid diagram showing:

• AWS services and relationships
• UK region placement (eu-west-2 primary, eu-west-1 DR)
• Network topology (VPC, subnets, NAT gateways)
• Security boundaries (Security Groups, NACLs, WAF)
• Data flows

Step 9: Detect Version and Determine Increment

Check if a previous version of this document exists in the project directory:

Use Glob to find existing projects/{project-dir}/research/ARC-{PROJECT_ID}-AWRS-*-v*.md files. If matches are found, read the highest version number from the filenames.

If no existing file: Use VERSION="1.0"

If existing file found:

1. Read the existing document to understand its scope (AWS services researched, architecture patterns, recommendations made)
2. Compare against the current requirements and your new research findings
3. Determine version increment:
   • Minor increment (e.g., 1.0 → 1.1, 2.1 → 2.2): Use when the scope is unchanged — refreshed pricing, updated service features, corrected details, minor additions within existing categories
   • Major increment (e.g., 1.0 → 2.0, 1.3 → 2.0): Use when scope has materially changed — new requirement categories, removed categories, fundamentally different service recommendations, significant new requirements added since last version
4. Use the determined version for ALL subsequent references:
   • Document ID and filename: ARC-{PROJECT_ID}-AWRS-v${VERSION}.md
   • Document Control: Version field
   • Revision History: Add new row with version, date, "AI Agent", description of changes, "PENDING", "PENDING"

Before writing the file, read .arckit/references/quality-checklist.md and verify all Common Checks plus the AWRS per-type checks pass. Fix any failures before proceeding.

Step 10: Write Output

Use the Write tool to save the complete document to projects/{project-dir}/research/ARC-{PROJECT_ID}-AWRS-v${VERSION}.md following the template structure.

Auto-populate fields:

• [PROJECT_ID] from project path
• [VERSION] = determined version from Step 9
• [DATE] = current date (YYYY-MM-DD)
• [STATUS] = "DRAFT"
• [CLASSIFICATION] = "OFFICIAL" (UK Gov) or "PUBLIC"

Include the generation metadata footer:

**Generated by**: ArcKit `$arckit-aws-research` agent
**Generated on**: {DATE}
**ArcKit Version**: {ArcKit version from context}
**Project**: {PROJECT_NAME} (Project {PROJECT_ID})
**AI Model**: {Actual model name}

DO NOT output the full document. Write it to file only.

Step 11: Return Summary

Return ONLY a concise summary including:

• Project name and file path created
• AWS services recommended (table: category, service, configuration, monthly estimate)
• Architecture pattern used
• Security alignment (Security Hub controls, Well-Architected pillars)
• UK Government suitability (G-Cloud, UK region, classification)
• Estimated monthly cost
• What's in the document
• Next steps ($arckit-diagram, $arckit-secure, $arckit-devops)

Quality Standards

• Official Sources Only: Prefer AWS documentation via MCP (SUPERCHARGED mode). If MCP is unavailable, use WebSearch/WebFetch targeting docs.aws.amazon.com (STANDALONE mode). Avoid third-party blogs in both modes
• UK Focus: Always check eu-west-2 (London) availability using get_regional_availability
• Well-Architected: Assess every recommendation against all 6 pillars (including Sustainability)
• Security Hub: Map recommendations to AWS Foundational Security Best Practices
• Cost Accuracy: Use AWS Pricing Calculator data where possible
• Code Samples: Prefer CDK (TypeScript/Python) or Terraform for IaC

Edge Cases

• No requirements found: Stop, tell user to run $arckit-requirements
• Service not in eu-west-2: Flag as a blocker for UK Government projects, suggest alternatives
• SECRET classification: Note that public AWS is not suitable, suggest AWS GovCloud or alternatives

Important Notes

• Markdown escaping: When writing less-than or greater-than comparisons, always include a space after < or > (e.g., < 3 seconds, > 99.9% uptime) to prevent markdown renderers from interpreting them as HTML tags or emoji

User Request

$ARGUMENTS

Suggested Next Steps

After completing this command, consider running:

• $arckit-diagram -- Create AWS architecture diagrams
• $arckit-devops -- Design AWS CodePipeline CI/CD
• $arckit-finops -- Create AWS cost management strategy
• $arckit-adr -- Record AWS service selection decisions