Skills Guide

Multi-Cloud Architecture

VerifiedSafe

Decision framework and patterns for architecting applications across AWS, Azure, and GCP.

Download and use
Sby Skills Guide Bot
DevOpsIntermediate
7/27/2026
Claude CodeCursorWindsurf
#multi-cloud#aws#azure#gcp#cloud-architecture

Recommended for

Backend developerClaude CodeCursorDevOps engineerWindsurfGit automation

Automated summary

This skill provides a decision framework and architecture patterns for designing multi-cloud systems and mapping equivalent services across AWS, Azure, and GCP.

Strengths

  • Clear side-by-side mapping tables for compute, storage, and database services across the three providers
  • Four named multi-cloud patterns (cross-cloud DR, best-of-breed, geographic distribution, cloud-agnostic abstraction)
  • Concrete list of open-source, portable alternatives (Kubernetes, PostgreSQL, Kafka, Redis, Terraform)
  • Cost-optimization levers and pricing-model notes per provider

Limitations

  • Service comparisons stay at the naming level, with no pricing figures or benchmarks
  • The Migration Strategy section is empty/truncated in the supplied file
  • Detailed examples are deferred to external reference files that are not included
When to use it

Use it when you must weigh AWS, Azure, and GCP service options or define a multi-cloud, lock-in-avoidance strategy.

When not to use it

Avoid it for single-provider implementation or debugging work, or when there is no genuine multi-cloud requirement.

Security analysis

Safe
Quality score82/100

This is a documentation-only architecture skill with no declared tools and no instructions to execute commands, access credentials, modify systems, or exfiltrate data. The referenced files are not executed, and the content is limited to cloud architecture guidance.

No concerns found

How this analysis is made

Examples

Choose a multi-cloud pattern
We run our main workload on AWS but need disaster recovery in Azure for compliance. Which multi-cloud pattern fits, and how should we replicate the database across clouds?
Map services across providers
Give me the equivalent of AWS Lambda, S3, and DynamoDB on Azure and GCP, and explain the trade-offs of picking one provider for all three.
Reduce vendor lock-in
Help me redesign our stack to be cloud-agnostic using Kubernetes, PostgreSQL, Kafka, and S3-compatible storage, and tell me which managed services to avoid.

name: multi-cloud-architecture description: "Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, and GCP. Use when building multi-cloud systems, avoiding vendor lock-in, or leveragin..." risk: unknown source: community date_added: "2026-02-27"

Multi-Cloud Architecture

Decision framework and patterns for architecting applications across AWS, Azure, and GCP.

Do not use this skill when

  • The task is unrelated to multi-cloud architecture
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Purpose

Design cloud-agnostic architectures and make informed decisions about service selection across cloud providers.

Use this skill when

  • Design multi-cloud strategies
  • Migrate between cloud providers
  • Select cloud services for specific workloads
  • Implement cloud-agnostic architectures
  • Optimize costs across providers

Cloud Service Comparison

Compute Services

| AWS | Azure | GCP | Use Case | |-----|-------|-----|----------| | EC2 | Virtual Machines | Compute Engine | IaaS VMs | | ECS | Container Instances | Cloud Run | Containers | | EKS | AKS | GKE | Kubernetes | | Lambda | Functions | Cloud Functions | Serverless | | Fargate | Container Apps | Cloud Run | Managed containers |

Storage Services

| AWS | Azure | GCP | Use Case | |-----|-------|-----|----------| | S3 | Blob Storage | Cloud Storage | Object storage | | EBS | Managed Disks | Persistent Disk | Block storage | | EFS | Azure Files | Filestore | File storage | | Glacier | Archive Storage | Archive Storage | Cold storage |

Database Services

| AWS | Azure | GCP | Use Case | |-----|-------|-----|----------| | RDS | SQL Database | Cloud SQL | Managed SQL | | DynamoDB | Cosmos DB | Firestore | NoSQL | | Aurora | PostgreSQL/MySQL | Cloud Spanner | Distributed SQL | | ElastiCache | Cache for Redis | Memorystore | Caching |

Reference: See references/service-comparison.md for complete comparison

Multi-Cloud Patterns

Pattern 1: Single Provider with DR

  • Primary workload in one cloud
  • Disaster recovery in another
  • Database replication across clouds
  • Automated failover

Pattern 2: Best-of-Breed

  • Use best service from each provider
  • AI/ML on GCP
  • Enterprise apps on Azure
  • General compute on AWS

Pattern 3: Geographic Distribution

  • Serve users from nearest cloud region
  • Data sovereignty compliance
  • Global load balancing
  • Regional failover

Pattern 4: Cloud-Agnostic Abstraction

  • Kubernetes for compute
  • PostgreSQL for database
  • S3-compatible storage (MinIO)
  • Open source tools

Cloud-Agnostic Architecture

Use Cloud-Native Alternatives

  • Compute: Kubernetes (EKS/AKS/GKE)
  • Database: PostgreSQL/MySQL (RDS/SQL Database/Cloud SQL)
  • Message Queue: Apache Kafka (MSK/Event Hubs/Confluent)
  • Cache: Redis (ElastiCache/Azure Cache/Memorystore)
  • Object Storage: S3-compatible API
  • Monitoring: Prometheus/Grafana
  • Service Mesh: Istio/Linkerd

Abstraction Layers

Application Layer
    ↓
Infrastructure Abstraction (Terraform)
    ↓
Cloud Provider APIs
    ↓
AWS / Azure / GCP

Cost Comparison

Compute Pricing Factors

  • AWS: On-demand, Reserved, Spot, Savings Plans
  • Azure: Pay-as-you-go, Reserved, Spot
  • GCP: On-demand, Committed use, Preemptible

Cost Optimization Strategies

  1. Use reserved/committed capacity (30-70% savings)
  2. Leverage spot/preemptible instances
  3. Right-size resources
  4. Use serverless for variable workloads
  5. Optimize data transfer costs
  6. Implement lifecycle policies
  7. Use cost allocation tags
  8. Monitor with cloud cost tools

Reference: See references/multi-cloud-patterns.md

Migration Strategy

Phase 1: Assessment

  • Inventory current infrastructure
  • Identify dependencies
  • Assess cloud compatibility
  • Estimate costs

Phase 2: Pilot

  • Select pilot workload
  • Implement in target cloud
  • Test thoroughly
  • Document learnings

Phase 3: Migration

  • Migrate workloads incrementally
  • Maintain dual-run period
  • Monitor performance
  • Validate functionality

Phase 4: Optimization

  • Right-size resources
  • Implement cloud-native services
  • Optimize costs
  • Enhance security

Best Practices

  1. Use infrastructure as code (Terraform/OpenTofu)
  2. Implement CI/CD pipelines for deployments
  3. Design for failure across clouds
  4. Use managed services when possible
  5. Implement comprehensive monitoring
  6. Automate cost optimization
  7. Follow security best practices
  8. Document cloud-specific configurations
  9. Test disaster recovery procedures
  10. Train teams on multiple clouds

Reference Files

  • references/service-comparison.md - Complete service comparison
  • references/multi-cloud-patterns.md - Architecture patterns

Related Skills

  • terraform-module-library - For IaC implementation
  • cost-optimization - For cost management
  • hybrid-cloud-networking - For connectivity

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/multi-cloud-architecture-ms2s7ctz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/multi-cloud-architecture-ms2s7ctz/download' --output '.skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md.part' && mv '.skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md.part' '.skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md' && test -s '.skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/multi-cloud-architecture' && cp -R '.skill-downloads/multi-cloud-architecture-ms2s7ctz' '.claude/skills/multi-cloud-architecture'

Cursor
test -f '.skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md' && test -s '.skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/multi-cloud-architecture' && cp -R '.skill-downloads/multi-cloud-architecture-ms2s7ctz' '.cursor/skills/multi-cloud-architecture'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/multi-cloud-architecture-ms2s7ctz'

openskills read 'multi-cloud-architecture-ms2s7ctz'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/multi-cloud-architecture-ms2s7ctz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Configure a Chat Channel with SecretRefs

DevOps

Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.

Claude CodeCodexintermediateSafe 387,940
Skills Guide Bot

Investigate ClickHouse CI Failures

DevOps

Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.

Claude CodeadvancedSafe 49,516
Skills Guide Bot

Ansible PR Review

DevOps

Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.

Claude CodeintermediateSafe 70,491
Skills Guide Bot