Architecture
The Architecture group in the Agentic Transformation Platform (ATP) sidebar holds 5 assessment pages. Each page is run by the same agent, Curt (architecture agent). Use this page to choose the right assessment and prepare the evidence it asks for.
Before you start
- Every page in this group uses the same assessment workspace. To learn how to upload evidence, run an analysis and ask follow-up questions, read Run an assessment.
- Upload metadata and exports only. Each page's Instructions panel says what not to upload.
Open a page in this group
- In ATP, open the menu at the left of the navigation bar.
- Expand Architecture.
- Select the page you need.
When a page from this group is open, the navigation bar shows the group's pages as tabs, so you can move between them. Pages that don't fit are under More.
Pages in this group
| Page | What it covers |
|---|---|
| Reference Architecture | Standard architecture patterns and templates. |
| Architecture Support | Architecture guidance and technical support. |
| Account & OU Structure | AWS account organization and OU design. |
| Core Networking | Network architecture and connectivity design. |
| Tagging Strategy | Resource tagging standards and governance. |
Reference architecture
Select Reference Architecture to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Curt. The sidebar describes it as: Standard architecture patterns and templates.
The Instructions panel is titled How to Generate Your Reference Architecture Assessment Report. It says:
To generate your reference architecture assessment report, Curt only needs metadata (Architecture diagrams and design documentation) — not business data. Upload raw exports from your architecture documentation tools, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Architecture Diagrams: System architecture diagrams, infrastructure designs, network topology maps, and environment relationship diagrams.
- Design Patterns: Standard architecture patterns, reference frameworks, cloud service templates, and best-practice guidelines.
- Technology Stack: Technology inventory, service dependencies, cloud service integrations, and multi-region configuration data.
- Assessment Documents: Architecture reviews, gap analyses, maturity assessments, improvement plans, and architectural debt inventories.
- Conformance Standards: Architecture standards records, compliance requirements, security and risk findings, and review feedback.
The panel also shows this note:
Important: Do not upload sensitive data, PII, or sensitive records — Curt analyzes architectural content, not customer content.
Architecture support
Select Architecture Support to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Curt. The sidebar describes it as: Architecture guidance and technical support.
The Instructions panel is titled How to Generate Your Architecture Support Assessment Report. It says:
To generate your architecture support assessment report, Curt only needs metadata (support tickets and impact patterns) — not business data. Upload raw exports from your ticketing systems, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Support Tickets: Architecture support requests, design consultation tickets, architecture review requests, and escalation records.
- Design Reviews: Architecture review requests, RFC documents, design documentation, and team-level design approval records.
- Solution Patterns: Approved solution designs, reusable architecture templates, pattern libraries, and best-practice references.
- Impact Analysis: Business impact assessments, technical debt records, root cause analysis outputs, and architectural risk indicators.
- Resource Plans: Architecture team capacity data, engagement models, staffing plans, and support workload distribution records.
The panel also shows this note:
Important: Do not upload sensitive data, PII, or sensitive records — Curt analyzes architecture support patterns, not customer content.
Account and OU structure
Select Account & OU Structure to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Curt. The sidebar describes it as: AWS account organization and OU design.
The Instructions panel is titled How to Generate Your Account & OU Structure Assessment Report. It says:
To generate your account and OU structure assessment report, Curt only needs metadata (organization structure and policies) — not business data. Upload raw exports from AWS Organizations or SCP management tools, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Organization Structure: AWS Organizations hierarchy, account inventory, OU parent-child relationships, and account grouping definitions.
- Service Control Policies: SCP configurations, account-level policies, approval processes, and OU-level permission boundaries.
- Account Metadata: Account ownership records, billing allocations, account tagging schemas, naming conventions, and IAM role assignments.
- Compliance Frameworks: Compliance findings, audit logs, regulatory requirements, and security configuration baselines.
- Growth Planning: Account creation policies, landing zone templates, scaling strategies, and OU expansion automation data.
The panel also shows this note:
Important: Do not upload sensitive data, PII, or sensitive records — Curt analyzes organizational structure and policy patterns, not customer content.
Core networking
Select Core Networking to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Curt. The sidebar describes it as: Network architecture and connectivity design.
The Instructions panel is titled How to Generate Your Core Networking Assessment Report. It says:
To generate your core networking assessment report, Curt only needs metadata (network configuration and topology) — not business data. Upload raw exports from your network management tools, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- VPC Architecture: VPC configurations, subnet layouts, route tables, security group policies, and IP address management data.
- Routing & Connectivity: VPC peering configurations, Transit Gateway routing, Direct Connect setups, and corporate connectivity data.
- Security Groups & NACLs: Security group rules, network access control lists, firewall configurations, and network access policies.
- DNS & Route 53: DNS configurations, hosted zones, routing policies, health check definitions, and failover rules.
- CDN & Network Services: CloudFront configurations, WAF setups, load balancer definitions, and advanced networking service data.
The panel also shows this note:
Important: Do not upload sensitive data, PII, or sensitive records — Curt analyzes network topology and configuration patterns, not customer content.
Tagging strategy
Select Tagging Strategy to open this page. The page header shows the badge Assessment workspace and the line Expert Consultation with Curt. The sidebar describes it as: Resource tagging standards and governance.
The Instructions panel is titled How to Generate Your Tagging Strategy Assessment Report. It says:
To generate your tagging strategy assessment report, Curt only needs metadata (tag inventory and compliance status) — not business data. Upload raw exports from your tag management tools, no JSON wrapping or special formatting is required.
It lists the evidence to upload:
- Tag Inventory: Current resource tagging levels, tag key-value usage data, tag distribution reports, and tag coverage statistics.
- Tagging Standards: Mandatory tag policies, accepted tag values, enforcement rules, and tag remediation workflows.
- Compliance Status: Non-compliant resource reports, tagging exemption records, compliance audit findings, and enforcement evidence.
- Automation & Enforcement: Tagging automation configurations, policy violation reports, remediation rule definitions, and compliance workflows.
- Cost Allocation Tags: Finance-required tag definitions, billing tag activation records, cost allocation tag mapping, and reporting requirements.
The panel also shows this note:
Important: Do not upload sensitive data, PII, or sensitive records — Curt analyzes tagging patterns and governance structures, not customer content.