Cloud architects write more than they architect.
The average cloud architect spends 30–40% of their time producing documents that have nothing to do with designing systems: architecture decision records, RFP responses, executive cost justification briefs, migration proposals, runbooks, and vendor evaluations. These documents are mission-critical—a bad ADR creates three months of arguments, and a weak cost brief kills a cloud initiative that should have launched last quarter.
The open web has almost no ChatGPT content aimed at cloud architects specifically. The few "prompt packs" that exist are for generic developers or infrastructure engineers. None address the high-stakes documentation workflows that actually slow cloud architects down.
This article fixes that. Below are 35 prompts organized into 7 categories—tested against the real writing workload cloud architects face every day.
1. Architecture Decision Records (ADRs)
ADRs are the most important documents most cloud architects write badly. These prompts help you produce records that hold up under scrutiny.
Prompt 1 — Initial ADR draft
"Write an Architecture Decision Record (ADR) using the MADR format. The decision is: [choose between AWS Aurora Serverless v2 and RDS Postgres for our transactional database tier]. Context: our application has spiky traffic patterns (5x peaks), the team has strong Postgres expertise, and we need to keep cold-start latency under 500ms. Include status, context, considered options with pros/cons, and decision rationale."
Prompt 2 — ADR for rejected option
"Write the 'Considered Options' section of an ADR documenting why we rejected [Kubernetes on-prem] in favor of [ECS Fargate]. Focus on TCO, operational burden, team capability gap, and migration risk. Be specific and include the tradeoffs we accepted."
Prompt 3 — Stakeholder-friendly ADR summary
"Take this ADR [paste ADR] and rewrite the executive summary for a VP of Engineering who is not technical. Keep it to 150 words. Emphasize business impact, risk mitigation, and why the rejected alternatives were inferior for our context."
Prompt 4 — ADR review checklist
"Review this Architecture Decision Record [paste ADR] and identify: (1) missing context that a new engineer would need, (2) assumptions that need validation, (3) consequences that aren't documented, (4) any wording that's ambiguous. Output as a bulleted checklist."
Prompt 5 — Multi-cloud ADR
"Write an ADR for the decision to adopt a multi-cloud strategy across AWS (primary) and Azure (DR/compliance). The drivers are: a regulatory requirement to store EU data within EU Azure regions, and our existing AWS investment in us-east-1. Include risks, organizational consequences, and the principle we'll use to prevent cloud sprawl."
2. RFP Responses and Vendor Evaluations
RFPs are high-stakes sales documents that cloud architects rarely enjoy writing. These prompts speed up the process without sacrificing rigor.
Prompt 6 — RFP section draft
"Write the Technical Architecture section of an RFP response for [enterprise data lake modernization on AWS]. Our solution uses S3 as the storage layer, AWS Glue for ETL, Athena for ad-hoc queries, and Redshift for the serving layer. The client requirement is sub-5-second query response for dashboards serving 500 concurrent users. Tone: confident, specific, no marketing filler."
Prompt 7 — Security and compliance section
"Write the Security and Compliance section of an RFP response covering: SOC 2 Type II certification, data encryption in transit and at rest, IAM least-privilege architecture, VPC design with private subnets, and our incident response SLA of 4-hour P1 acknowledgment. The client is in financial services."
Prompt 8 — Vendor comparison matrix
"Create a vendor evaluation matrix comparing [Snowflake, Databricks, and AWS Redshift] across these criteria: query performance at 10TB scale, pricing model predictability, integration with our existing AWS ecosystem, vendor lock-in risk, and team learning curve. Format as a table with a scoring column (1–5) and a recommendation row."
Prompt 9 — Clarifying questions for RFP
"We received an RFP for [cloud migration of a legacy Java monolith]. Before responding, write 15 clarifying questions we should ask the client to properly scope our response. Focus on: current architecture complexity, data migration requirements, downtime tolerance, team cloud readiness, and regulatory constraints."
Prompt 10 — Executive summary for RFP response
"Write a 200-word executive summary for our RFP response to [city government cloud infrastructure modernization]. Emphasize our track record with public sector compliance (FedRAMP, StateRAMP), our approach to minimizing service disruption, and our commitment to knowledge transfer so the client isn't dependent on us long-term."
3. Executive Cost Justification Briefs
The cloud initiative that dies in finance is usually the one where the architect submitted a spreadsheet instead of a story. These prompts build the narrative.
Prompt 11 — CapEx to OpEx justification
"Write an executive cost justification brief for migrating our on-premises data center to AWS. Current state: 3 data centers, $4.2M annual CapEx, 12 FTE ops team. Projected state: AWS spend $1.8M annually, 6 FTE team, with elasticity to scale without new hardware cycles. Frame this as CapEx to OpEx transformation with 3-year NPV analysis structure."
Prompt 12 — Cloud cost optimization brief
"Write a 1-page brief for our CFO justifying a $120K investment in cloud cost optimization tooling (Spot.io + Cloudability). Current cloud spend: $1.4M/year. Expected savings: 25–35% within 6 months based on Gartner benchmarks for our profile. Address the objection: 'Why can't your team just do this manually?'"
Prompt 13 — Risk-adjusted ROI
"Help me write a risk-adjusted ROI section for a cloud migration business case. Include: (1) quantified risk of staying on-prem (aging hardware failure probability, compliance penalty exposure, talent retention cost), (2) migration project risk and mitigation, (3) time-to-value assumptions, (4) sensitivity analysis showing what happens if cloud costs run 20% over projection."
Prompt 14 — Multi-year cloud financial model narrative
"Write the narrative section accompanying a 5-year cloud TCO model. Year 1 costs are higher due to migration investment ($800K). Years 2–5 show decreasing unit cost as we optimize. Key message: the payback period is 18 months and we capture $3.2M in savings by Year 5. Audience: Board of Directors. Length: 400 words."
Prompt 15 — Rejection response memo
"Our cloud modernization proposal was rejected by the finance committee due to cost concerns. Write a response memo that: (1) acknowledges their concerns, (2) proposes a phased approach starting with a 3-month pilot on our lowest-risk workload, (3) quantifies what inaction costs (technical debt accrual rate, incident cost), (4) requests a 30-minute meeting to discuss the pilot scope."
4. Migration Proposals and Technical Roadmaps
Cloud migrations live or die on the quality of the initial proposal. These prompts help you write migration documents that create alignment before a single workload moves.
Prompt 16 — 6R analysis write-up
"Write the migration strategy section of a cloud proposal using the 6R framework (Rehost, Replatform, Repurchase, Refactor, Retire, Retain). We have 47 applications. Segment them into Rs based on these criteria: [list your criteria]. Document the decision logic so engineering leads can apply it consistently to applications we haven't analyzed yet."
Prompt 17 — Wave planning narrative
"Write the wave planning section of our cloud migration proposal. Wave 1 (months 1–3): low-complexity stateless apps, 12 services. Wave 2 (months 4–8): databases and stateful workloads, requires data migration strategy. Wave 3 (months 9–14): legacy monolith refactoring. For each wave, document: success criteria, team composition, rollback plan, and dependencies."
Prompt 18 — Cutover plan
"Write a production cutover plan for migrating [our e-commerce checkout service] from on-prem to AWS. Include: pre-cutover checklist (72 hours), DNS cutover sequence, parallel running period (72 hours minimum), rollback trigger conditions, communication plan for stakeholders, and post-cutover validation steps."
Prompt 19 — Migration risk register
"Create a migration risk register for our AWS migration. Include at least 10 risks across these categories: data integrity, performance regression, security misconfiguration, team capability gap, vendor dependency, and regulatory compliance. For each risk: likelihood (H/M/L), impact (H/M/L), owner, and mitigation action."
Prompt 20 — Go/No-Go criteria document
"Write a Go/No-Go criteria document for our cloud migration production cutover. Define criteria in these areas: performance benchmarks (latency, throughput), security validation, data integrity checks, runbook readiness, team sign-off requirements, and executive approval chain. Format as a checklist with owners for each criterion."
5. Cloud Architecture Documentation
The architecture documentation that actually gets read is the one that tells a story, not just a diagram. These prompts help you write docs engineers use.
Prompt 21 — Architecture overview for engineers
"Write the architecture overview section of our [data platform] technical documentation. Include: system purpose in one sentence, high-level component diagram description (I'll add the actual diagram), data flow narrative for the three main use cases, and key design decisions with their rationale. Target audience: engineers joining the team who need context in under 20 minutes."
Prompt 22 — Networking architecture doc
"Write the networking architecture section for our AWS landing zone documentation. Cover: VPC design (3-tier: public/private/isolated), Transit Gateway for multi-account connectivity, security group strategy, NACLs, and our egress inspection architecture using AWS Network Firewall. Include a section on what engineers are NOT allowed to change and why."
Prompt 23 — Disaster recovery runbook
"Write a disaster recovery runbook for our primary SaaS platform. Scenario: complete failure of us-east-1 (black swan). Recovery steps to shift to us-west-2 DR environment. Include: detection criteria, escalation chain, RTO target (4 hours), RPO target (1 hour), step-by-step recovery procedure, communication templates, and post-incident documentation requirements."
Prompt 24 — Capacity planning document
"Write a capacity planning document for our AWS infrastructure for the next 12 months. Current usage: [describe]. Growth assumptions: 40% user growth, 2x data volume. Include: projected resource requirements by quarter, scaling triggers and automation approach, budget projections by service category, and assumptions that would invalidate this plan."
Prompt 25 — Well-Architected review narrative
"Write the narrative summary of our AWS Well-Architected Framework review. Pillar scores: Operational Excellence 72/100, Security 81/100, Reliability 65/100, Performance 78/100, Cost 69/100, Sustainability 55/100. Lowest score is Reliability due to single-AZ databases and missing circuit breakers. Write a 500-word executive summary that prioritizes remediation and sets a 90-day improvement target."
6. Stakeholder and Leadership Communication
Cloud architects spend more time managing stakeholders than most realize. These prompts help you communicate up without dumbing down.
Prompt 26 — Monthly cloud health report
"Write a monthly cloud health report for our VP of Engineering. Format: 1 page. Include: cloud spend vs. budget ($847K vs. $900K forecast — under budget), top 3 reliability events this month and resolutions, security finding count (7 Medium, 0 High/Critical), and next month's focus areas. Tone: confident, brief, no technical jargon above 'database' and 'server.'"
Prompt 27 — Cloud incident executive summary
"Write an executive summary of our [4-hour S3 outage] that affected customer file uploads. Audience: CEO and board. Cover: what happened in plain English, customer impact (2,300 users affected, no data loss), root cause (brief), what we've done to prevent recurrence, and our confidence level going forward. Length: 200 words."
Prompt 28 — Architecture review meeting prep
"Write a meeting agenda and pre-read document for our quarterly Architecture Review Board. Topic: approving our shift from ECS to EKS for the platform tier. Decision needed: approve, reject, or request further analysis. Include: context section (why we're considering the change), the trade-offs we've evaluated, what we're asking the board to decide, and what happens if they say no."
Prompt 29 — Cloud strategy presentation outline
"Write a 10-slide cloud strategy presentation outline for our leadership team. We're 60% through a 3-year cloud transformation. Slides needed: where we started, where we are, what we've learned, the remaining work, risks on the horizon, our ask for Year 3 budget ($2.1M), and the business outcomes tied to cloud completion."
Prompt 30 — Repatriation recommendation memo
"Write a memo recommending we repatriate [our GPU training cluster] from AWS back to on-premises colocation. The economics changed: GPU spot prices on AWS increased 40%, our training jobs run continuously (not spiky), and we can lease dedicated H100 nodes at 60% of AWS cost. Address the expected objection: 'But we committed to cloud-first.'"
7. Cloud Governance and Policy Documentation
Governance documents nobody reads are a governance failure. These prompts help you write policy docs that engineers actually follow.
Prompt 31 — Tagging policy document
"Write a cloud resource tagging policy for our AWS organization. Required tags: Environment, Team, CostCenter, Project, DataClassification. Include: enforcement mechanism (SCP that denies resource creation without required tags), exception process for legacy resources, and the quarterly tagging audit procedure. Tone: clear and direct — this will be enforced."
Prompt 32 — Cloud security policy
"Write a cloud security policy for our engineering organization covering: (1) what requires security review before deployment, (2) approved services list vs. restricted services, (3) data classification rules for what can/cannot go to cloud, (4) encryption requirements, (5) secrets management (we use AWS Secrets Manager — no hardcoded secrets, no exceptions). Target audience: software engineers."
Prompt 33 — FinOps governance doc
"Write a FinOps governance document establishing our cloud cost accountability model. Covers: team-level budget ownership, monthly showback report format, escalation process when teams exceed budget by 15%+, the 'no untagged resources' rule and its enforcement, and our commitment to 90% budget forecast accuracy. This will be signed off at VP level and enforced."
Prompt 34 — Change management process for cloud
"Write the cloud change management process for our platform team. Define: change categories (Standard/Normal/Emergency), approval chain for each, deployment windows, rollback requirements, post-change validation steps, and incident escalation if a change causes degradation. This replaces our previous ITIL process — keep it lean and focused on speed without sacrificing safety."
Prompt 35 — Cloud onboarding guide for new engineers
"Write a cloud onboarding guide for engineers joining our team. Cover: how to get AWS access, our account structure (prod/staging/dev/sandbox), what they can do in sandbox without approval, what requires a ticket, our core tooling (Terraform, AWS CLI, kubectl), and where to find our architecture docs and ADR library. Length: 600 words. Tone: welcoming but precise."
Start With the Work That Blocks Everything Else
The five prompts that cloud architects tell me create the most immediate leverage:
- ADR draft (Prompt 1) — eliminates the blank-page problem on your most politically charged documents
- Executive cost brief (Prompt 11) — the document that unlocks every cloud initiative
- Migration risk register (Prompt 19) — makes you look like you've thought of everything (because you have)
- Cloud incident executive summary (Prompt 27) — turns the worst day of your quarter into a confidence builder
- Tagging policy (Prompt 31) — solves a governance problem that compounds every month you delay
These aren't shortcuts. They're scaffolding. You still bring the judgment, the architecture knowledge, and the organizational context. ChatGPT handles the blank page and the structural heavy lifting.
If you're building a complete ChatGPT prompt toolkit for cloud infrastructure work, check out the full pack at gumroad.com/PENDING_CLOUD_ARCH — 100+ prompts organized by workflow, including IaC documentation, multi-cloud governance, and FinOps reporting templates.