Multi Cloud Architecture
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add multi-cloud-architectureWho is stuck, and on what
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.
The whole source
Frontmatter — 2 properties
| name | multi-cloud-architecture |
|---|---|
| description | 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. |
| 1 | --- |
| 2 | name: multi-cloud-architecture |
| 3 | description: 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. |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # Multi-Cloud Architecture |
| 7 | |
| 8 | Decision framework and patterns for architecting applications across AWS, Azure, GCP, and OCI. |
| 9 | |
| 10 | ## Purpose |
| 11 | |
| 12 | Design cloud-agnostic architectures and make informed decisions about service selection across cloud providers. |
| 13 | |
| 14 | ## When to Use |
| 15 | |
| 16 | - Design multi-cloud strategies |
| 17 | - Migrate between cloud providers |
| 18 | - Select cloud services for specific workloads |
| 19 | - Implement cloud-agnostic architectures |
| 20 | - Optimize costs across providers |
| 21 | |
| 22 | ## Cloud Service Comparison |
| 23 | |
| 24 | ### Compute Services |
| 25 | |
| 26 | | AWS | Azure | GCP | OCI | Use Case | |
| 27 | | ------- | ------------------- | --------------- | ------------------- | ------------------ | |
| 28 | | EC2 | Virtual Machines | Compute Engine | Compute | IaaS VMs | |
| 29 | | ECS | Container Instances | Cloud Run | Container Instances | Containers | |
| 30 | | EKS | AKS | GKE | OKE | Kubernetes | |
| 31 | | Lambda | Functions | Cloud Functions | Functions | Serverless | |
| 32 | | Fargate | Container Apps | Cloud Run | Container Instances | Managed containers | |
| 33 | |
| 34 | ### Storage Services |
| 35 | |
| 36 | | AWS | Azure | GCP | OCI | Use Case | |
| 37 | | ------- | --------------- | --------------- | -------------- | -------------- | |
| 38 | | S3 | Blob Storage | Cloud Storage | Object Storage | Object storage | |
| 39 | | EBS | Managed Disks | Persistent Disk | Block Volumes | Block storage | |
| 40 | | EFS | Azure Files | Filestore | File Storage | File storage | |
| 41 | | Glacier | Archive Storage | Archive Storage | Archive Storage | Cold storage | |
| 42 | |
| 43 | ### Database Services |
| 44 | |
| 45 | | AWS | Azure | GCP | OCI | Use Case | |
| 46 | | ----------- | ---------------- | ------------- | ------------------- | --------------- | |
| 47 | | RDS | SQL Database | Cloud SQL | MySQL HeatWave | Managed SQL | |
| 48 | | DynamoDB | Cosmos DB | Firestore | NoSQL Database | NoSQL | |
| 49 | | Aurora | PostgreSQL/MySQL | Cloud Spanner | Autonomous Database | Distributed SQL | |
| 50 | | ElastiCache | Cache for Redis | Memorystore | OCI Cache | Caching | |
| 51 | |
| 52 | **Reference:** See `references/service-comparison.md` for complete comparison |
| 53 | |
| 54 | ## Multi-Cloud Patterns |
| 55 | |
| 56 | ### Pattern 1: Single Provider with DR |
| 57 | |
| 58 | - Primary workload in one cloud |
| 59 | - Disaster recovery in another |
| 60 | - Database replication across clouds |
| 61 | - Automated failover |
| 62 | |
| 63 | ### Pattern 2: Best-of-Breed |
| 64 | |
| 65 | - Use best service from each provider |
| 66 | - AI/ML on GCP |
| 67 | - Enterprise apps on Azure |
| 68 | - Regulated data platforms on OCI |
| 69 | - General compute on AWS |
| 70 | |
| 71 | ### Pattern 3: Geographic Distribution |
| 72 | |
| 73 | - Serve users from nearest cloud region |
| 74 | - Data sovereignty compliance |
| 75 | - Global load balancing |
| 76 | - Regional failover |
| 77 | |
| 78 | ### Pattern 4: Cloud-Agnostic Abstraction |
| 79 | |
| 80 | - Kubernetes for compute |
| 81 | - PostgreSQL for database |
| 82 | - S3-compatible storage (MinIO) |
| 83 | - Open source tools |
| 84 | |
| 85 | ## Cloud-Agnostic Architecture |
| 86 | |
| 87 | ### Use Cloud-Native Alternatives |
| 88 | |
| 89 | - **Compute:** Kubernetes (EKS/AKS/GKE/OKE) |
| 90 | - **Database:** PostgreSQL/MySQL (RDS/SQL Database/Cloud SQL/MySQL HeatWave) |
| 91 | - **Message Queue:** Apache Kafka or managed streaming (MSK/Event Hubs/Confluent/OCI Streaming) |
| 92 | - **Cache:** Redis (ElastiCache/Azure Cache/Memorystore/OCI Cache) |
| 93 | - **Object Storage:** S3-compatible API |
| 94 | - **Monitoring:** Prometheus/Grafana |
| 95 | - **Service Mesh:** Istio/Linkerd |
| 96 | |
| 97 | ### Abstraction Layers |
| 98 | |
| 99 | ``` |
| 100 | Application Layer |
| 101 | ↓ |
| 102 | Infrastructure Abstraction (Terraform) |
| 103 | ↓ |
| 104 | Cloud Provider APIs |
| 105 | ↓ |
| 106 | AWS / Azure / GCP / OCI |
| 107 | ``` |
| 108 | |
| 109 | ## Cost Comparison |
| 110 | |
| 111 | ### Compute Pricing Factors |
| 112 | |
| 113 | - **AWS:** On-demand, Reserved, Spot, Savings Plans |
| 114 | - **Azure:** Pay-as-you-go, Reserved, Spot |
| 115 | - **GCP:** On-demand, Committed use, Preemptible |
| 116 | - **OCI:** Pay-as-you-go, annual commitments, burstable/flexible shapes, preemptible instances |
| 117 | |
| 118 | ### Cost Optimization Strategies |
| 119 | |
| 120 | 1. Use reserved/committed capacity (30-70% savings) |
| 121 | 2. Leverage spot/preemptible instances |
| 122 | 3. Right-size resources |
| 123 | 4. Use serverless for variable workloads |
| 124 | 5. Optimize data transfer costs |
| 125 | 6. Implement lifecycle policies |
| 126 | 7. Use cost allocation tags |
| 127 | 8. Monitor with cloud cost tools |
| 128 | |
| 129 | **Reference:** See `references/multi-cloud-patterns.md` |
| 130 | |
| 131 | ## Migration Strategy |
| 132 | |
| 133 | ### Phase 1: Assessment |
| 134 | |
| 135 | - Inventory current infrastructure |
| 136 | - Identify dependencies |
| 137 | - Assess cloud compatibility |
| 138 | - Estimate costs |
| 139 | |
| 140 | ### Phase 2: Pilot |
| 141 | |
| 142 | - Select pilot workload |
| 143 | - Implement in target cloud |
| 144 | - Test thoroughly |
| 145 | - Document learnings |
| 146 | |
| 147 | ### Phase 3: Migration |
| 148 | |
| 149 | - Migrate workloads incrementally |
| 150 | - Maintain dual-run period |
| 151 | - Monitor performance |
| 152 | - Validate functionality |
| 153 | |
| 154 | ### Phase 4: Optimization |
| 155 | |
| 156 | - Right-size resources |
| 157 | - Implement cloud-native services |
| 158 | - Optimize costs |
| 159 | - Enhance security |
| 160 | |
| 161 | ## Best Practices |
| 162 | |
| 163 | 1. **Use infrastructure as code** (Terraform/OpenTofu) |
| 164 | 2. **Implement CI/CD pipelines** for deployments |
| 165 | 3. **Design for failure** across clouds |
| 166 | 4. **Use managed services** when possible |
| 167 | 5. **Implement comprehensive monitoring** |
| 168 | 6. **Automate cost optimization** |
| 169 | 7. **Follow security best practices** |
| 170 | 8. **Document cloud-specific configurations** |
| 171 | 9. **Test disaster recovery** procedures |
| 172 | 10. **Train teams** on multiple clouds |
| 173 | |
| 174 | |
| 175 | ## Related Skills |
| 176 | |
| 177 | - `terraform-module-library` - For IaC implementation |
| 178 | - `cost-optimization` - For cost management |
| 179 | - `hybrid-cloud-networking` - For connectivity |
| 180 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Paper Poster (HTML): measurement-gated poster generationDEFAULT poster pipeline — build an academic conference poster (ICML/NeurIPS/ICLR/CVPR/...) as a single HTML/CSS file with measurement-driven hard gates, real paper figures, a two-hue design-token system, and print-ready PDF via headless Chromium. Use when the●····●36/40Brand Monitoring 📡Brand monitoring tool for tracking mentions across social media platforms. Monitor Reddit, Google News, YouTube, and DuckDuckGo for brand mentions. Includes sentiment analysis, trend tracking, crisis detection, and competitor comparison. No API key required fo◐····●34/40Spark Memory & Thermal OpsManage unified memory and thermals during long-running ML jobs on NVIDIA DGX Spark. Use when planning memory headroom for a training run on GB10, when a job OOMs on unified memory, or when monitoring temperature and power during multi-hour training.◐····●32/40Secrets ManagementImplement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.◐····●32/40