Skip to main content
Agent skill

Multi Cloud Architecture

Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, GCP, and OCI. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Multi Cloud Architecture when an AI agent needs a reusable SKILL.md workflow for this job: Design multi-cloud architectures using a decision framework to select and integrate services across AWS, Azure, GCP, and OCI. Use when building multi-cloud systems, avoiding vendor lock-in, or leveraging best-of-breed services from multiple providers.

When not to use it

Skip Multi Cloud Architecture when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/multi-cloud-architecture
# Save SKILL.md to ~/.claude/skills/multi-cloud-architecture/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/multi-cloud-architecture/SKILL.md. For a shared project, commit the folder at .claude/skills/multi-cloud-architecture/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Multi Cloud Architecture skill for this task: Design multi-cloud strategies. Confirm any required inputs or files before making changes.

What supports this recommendation?

81/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
90/100
Practical detail
82/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Multi-Cloud Architecture

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

## Purpose

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

## When to Use

- 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 | OCI | Use Case | | ------- | ------------------- | --------------- | ------------------- | ------------------ | | EC2 | Virtual Machines | Compute Engine | Compute | IaaS VMs | | ECS | Container Instances | Cloud Run | Container Instances | Containers | | EKS | AKS | GKE | OKE | Kubernetes | | Lambda | Functions | Cloud Functions | Functions | Serverless | | Fargate | Container Apps | Cloud Run | Container Instances | Managed containers |

### Storage Services

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

### Database Services

| AWS | Azure | GCP | OCI | Use Case | | ----------- | ---------------- | ------------- | ------------------- | --------------- | | RDS | SQL Database | Cloud SQL | MySQL HeatWave | Managed SQL | | DynamoDB | Cosmos DB | Firestore | NoSQL Database | NoSQL | | Aurora | PostgreSQL/MySQL | Cloud Spanner | Autonomous Database | Distributed SQL | | ElastiCache | Cache for Redis | Memorystore | OCI Cache | 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 - Regulated data platforms on OCI - 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/OKE) - **Database:** PostgreSQL/MySQL (RDS/SQL Database/Cloud SQL/MySQL HeatWave) - **Message Queue:** Apache Kafka or managed streaming (MSK/Event Hubs/Confluent/OCI Streaming) - **Cache:** Redis (ElastiCache/Azure Cache/Memorystore/OCI Cache) - **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 / OCI ```

## 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 - **OCI:** Pay-as-you-go, annual commitments, burstable/flexible shapes, preemptible instances

### 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

## Related Skills

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

Intended uses

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

Implementation notes

  • Use infrastructure as code (Terraform/OpenTofu)
  • Implement CI/CD pipelines for deployments
  • Design for failure across clouds
  • Use managed services when possible
  • Implement comprehensive monitoring
  • Automate cost optimization
  • Follow security best practices
  • Document cloud-specific configurations
  • Test disaster recovery procedures
  • Train teams on multiple clouds

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.