New to Claude Skills? Learn how to install them →

wshobson on GitHub

Multi-Cloud Architecture

Free

Design cloud-agnostic architectures across providers.

Get this skill

Free · Opens the source repo

What Multi-Cloud Architecture does

The Multi-Cloud Architecture skill provides a structured decision framework for designing applications that span multiple cloud environments, specifically AWS, Azure, GCP, and OCI. This skill is essential for developers and architects looking to avoid vendor lock-in and leverage the best services from each cloud provider. It facilitates the creation of cloud-agnostic architectures that can adapt to various workloads and business needs.

By utilizing this skill, users can effectively select and integrate cloud services tailored to their specific requirements. The bundled references include detailed comparisons of compute, storage, and database services across the major cloud platforms, allowing users to make informed decisions based on their unique use cases. The skill also outlines multi-cloud patterns that can be employed to optimize performance, compliance, and cost efficiency.

This skill is particularly useful in scenarios such as designing multi-cloud strategies, migrating workloads between providers, and implementing cost optimization strategies. With a focus on best practices, users are guided on how to leverage infrastructure as code, implement CI/CD pipelines, and ensure comprehensive monitoring across their multi-cloud environments.

In summary, the Multi-Cloud Architecture skill is a valuable resource for anyone involved in cloud architecture, providing the necessary tools and insights to build resilient, scalable, and cost-effective multi-cloud solutions.

When to use it

Use this skill when designing multi-cloud strategies, migrating workloads, or selecting cloud services for specific applications.

When not to use it

This skill may not be suitable for projects that are strictly limited to a single cloud provider or do not require multi-cloud capabilities.

What you can build with it

Designing a Multi-Cloud Strategy

Utilize the skill to create a comprehensive strategy that incorporates services from AWS, Azure, and GCP to meet diverse application needs.

Migrating Workloads Between Providers

Follow the migration strategy outlined in the skill to seamlessly transition workloads from one cloud provider to another while minimizing downtime.

Optimizing Costs Across Cloud Providers

Leverage the cost comparison and optimization strategies to ensure that your multi-cloud architecture remains cost-effective.

How to install Multi-Cloud Architecture

View source

1. Install with the skills CLI

npx skills add wshobson/agents/multi-cloud-architecture --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by wshobson

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

AWSAzureGCPOCIUse Case
EC2Virtual MachinesCompute EngineComputeIaaS VMs
ECSContainer InstancesCloud RunContainer InstancesContainers
EKSAKSGKEOKEKubernetes
LambdaFunctionsCloud FunctionsFunctionsServerless
FargateContainer AppsCloud RunContainer InstancesManaged containers

Storage Services

AWSAzureGCPOCIUse Case
S3Blob StorageCloud StorageObject StorageObject storage
EBSManaged DisksPersistent DiskBlock VolumesBlock storage
EFSAzure FilesFilestoreFile StorageFile storage
GlacierArchive StorageArchive StorageArchive StorageCold storage

Database Services

AWSAzureGCPOCIUse Case
RDSSQL DatabaseCloud SQLMySQL HeatWaveManaged SQL
DynamoDBCosmos DBFirestoreNoSQL DatabaseNoSQL
AuroraPostgreSQL/MySQLCloud SpannerAutonomous DatabaseDistributed SQL
ElastiCacheCache for RedisMemorystoreOCI CacheCaching

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

Frequently asked questions about Multi-Cloud Architecture

Similar skills