cloud-architecture-design

Plan multi-cloud architectures across AWS, Azure, and GCP using Well-Architected principles.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill cloud-architecture-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-architecture-design
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/cloud-architecture-design/skills/cloud-architecture-design
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill cloud-architecture-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineers need a structured approach to plan scalable, secure, and cost-conscious cloud architectures across AWS, Azure, and GCP in line with the Well-Architected framework.

Core Features & Use Cases

  • Region and AZ strategy: guidance on multi-region deployment, fault tolerance, and disaster recovery.
  • Compute paradigms: recommendations for serverless, containers, VMs, and PaaS based on workload characteristics.
  • Identity, networking, and storage: best practices for IAM, network design, data residency, and managed storage.
  • Cost and governance: cost modeling, budgeting, and guardrails to prevent sprawl across clouds.

Quick Start

Propose a multi-cloud architecture design satisfying Well-Architected pillars for a given workload.

Frequently Asked Questions about cloud-architecture-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a multi-cloud architecture that meets Well-Architected principles?

Designing a well-architected multi-cloud architecture involves planning compute, storage, networking, and identity across AWS, Azure, and GCP. This approach applies structured guidelines to satisfy workload characterization, regional placement, and architectural trade-off documentation.

What is the best way to plan fault tolerance and disaster recovery across multiple cloud regions?

Planning fault tolerance across multiple cloud regions requires defining a region and Availability Zone (AZ) strategy. This ensures proper workload distribution and disaster recovery readiness by applying best practices for multi-region deployment and architectural resilience.

How do I choose between serverless, containers, VMs, and PaaS for my cloud workload?

Choosing between serverless, containers, VMs, and PaaS depends on your specific workload characteristics. A structured cloud architecture design evaluates these compute paradigms against Well-Architected principles to recommend the most suitable and cost-conscious deployment model.

Can I apply consistent security baselines and governance across AWS, Azure, and GCP?

Applying consistent security baselines and governance across AWS, Azure, and GCP is achievable through unified identity and networking best practices. This strategy implements cost modeling, budgeting, and guardrails to prevent sprawl while ensuring data residency and IAM compliance.

When do I need explicit architectural trade-off documentation for my cloud infrastructure?

Explicit architectural trade-off documentation is needed when planning complex multi-cloud infrastructures requiring regional placement and AZ diversity. Documenting these trade-offs satisfies Well-Architected requirements by providing clear reasoning for compute, storage, and networking decisions.

Does cloud architecture design help with cost optimization and preventing resource sprawl?

Cloud architecture design directly addresses cost optimization by applying governance and cost modeling practices. This approach establishes budgeting guardrails and managed storage strategies across AWS, Azure, and GCP to effectively prevent resource sprawl.