Technical requirement gathering
Purpose. Capture the technical facts that scope, architecture and cost depend
on. Complete with the customer's technical team.
Account and organisation
| Question | Response |
|---|
| AWS account ID(s) and account structure | |
| Is the account under AWS Organizations? | |
| Existing Control Tower or landing zone? | |
| Regions in use, and regions permitted | |
| Identity provider (Identity Center, Okta, Entra ID, other) | |
| Billing and chargeback model | |
Network
| Question | Response |
|---|
| Existing VPCs, CIDR ranges and overlap | |
| Connectivity to on-premises (VPN, Direct Connect) | |
| Public-facing services and their entry points | |
| DNS provider and zones | |
| Egress requirements and restrictions | |
| Firewall or inspection requirements | |
Compute and runtime
| Workload | Runtime | Instances / size | Scaling | Notes |
|---|
| | | | |
| Question | Response |
|---|
| Containerised workloads and orchestrator | |
| Serverless usage | |
| Batch or scheduled jobs | |
| Specialised hardware (GPU, high memory) | |
| Operating systems and versions | |
Data
| Data store | Engine | Size | Growth | Criticality |
|---|
| | | | |
| Question | Response |
|---|
| Data classification scheme | |
| Where sensitive data resides | |
| Backup requirements and current practice | |
| Retention obligations | |
| Data residency constraints | |
| Migration volume and downtime tolerance | |
Delivery
| Question | Response |
|---|
| Version control system and repository count | |
| CI/CD tooling in use | |
| Deployment frequency and duration | |
| Branching model | |
| Test coverage and test types | |
| Artefact registry | |
| Infrastructure as code tooling and state management | |
Security
| Question | Response |
|---|
| Compliance obligations | |
| Identity and access model | |
| MFA and password policy | |
| Secret management approach | |
| Encryption standards | |
| Vulnerability and patch management | |
| Detection and monitoring tools | |
| Incident response process | |
Observability
| Question | Response |
|---|
| Current monitoring tools | |
| Metrics collected | |
| Log aggregation and retention | |
| Tracing in use | |
| Alerting channels and on-call model | |
| Dashboards and their audience | |
Availability and recovery
| Workload | Availability target | RTO | RPO | Current capability |
|---|
| | | | |
Constraints
| Constraint | Detail | Impact |
|---|
| Technical | | |
| Organisational | | |
| Contractual | | |
| Timeline | | |
Integrations
| System | Direction | Protocol | Criticality | Owner |
|---|
| | | | |
Open items