スキル multi-cloud-architecture
☁️

multi-cloud-architecture

安全

Design multi-cloud architectures across AWS, Azure, and GCP

こちらからも入手できます: wshobson

Avoid vendor lock-in and build resilient cloud systems. This skill provides a decision framework for selecting and integrating services across multiple cloud providers.

対応: Claude Codex Code(CC)
🥉 74 ブロンズ
1

スキルZIPをダウンロード

2

Claudeでアップロード

設定 → 機能 → スキル → スキルをアップロードへ移動

3

オンにして利用開始

テストする

「multi-cloud-architecture」を使用しています。 Compare serverless compute options across clouds

期待される結果:

AWS Lambda: Event-driven functions with 15-minute timeout, extensive integrations. Azure Functions: Tight Microsoft ecosystem integration, Durable Functions for stateful workflows. GCP Cloud Functions: Simple pricing, native BigQuery integration. Recommendation: Use Lambda for complex event workflows, Azure Functions for Microsoft stacks, Cloud Functions for data pipelines.

「multi-cloud-architecture」を使用しています。 Design geo-distributed architecture for global users

期待される結果:

Architecture: Use GCP Cloud CDN for static assets, AWS CloudFront for dynamic content, Azure Front Door for API gateway. Deploy stateless services to GKE, AKS, and EKS in nearest regions. Use Cloud Spanner or Cosmos DB for globally distributed data. Route traffic via DNS-based geo-routing with health checks and automatic failover.

セキュリティ監査

安全
v1 • 2/25/2026

All static analyzer findings are false positives. The SKILL.md file is pure documentation containing markdown tables, text descriptions, and architecture diagrams. No executable code or command injection vectors exist. External command references are documentation text pointing to other files, not actual shell execution.

1
スキャンされたファイル
192
解析された行数
0
検出結果
1
総監査数
セキュリティ問題は見つかりませんでした
監査者: claude

品質スコア

38
アーキテクチャ
100
保守性
87
コンテンツ
50
コミュニティ
100
セキュリティ
91
仕様準拠

作れるもの

Enterprise multi-cloud strategy

Design a cloud strategy that distributes workloads across AWS, Azure, and GCP to reduce vendor dependency and improve negotiating leverage with providers.

Cloud migration planning

Plan and execute migration from one cloud provider to another while minimizing downtime and maintaining service quality.

Disaster recovery architecture

Build resilient systems with disaster recovery capabilities across multiple cloud providers for business continuity.

これらのプロンプトを試す

Compare cloud services for a workload 
I need to deploy a high-availability web application with auto-scaling. Compare the equivalent services across AWS, Azure, and GCP for compute, storage, database, and networking. Recommend the best option for each category based on cost and features.
Design cloud-agnostic architecture 
Design a cloud-agnostic architecture for a microservices application that can run on any cloud provider. Include specific technologies for compute orchestration, data storage, messaging, and monitoring that work consistently across AWS, Azure, and GCP.
Multi-cloud disaster recovery plan 
Create a disaster recovery architecture using AWS as primary and Azure as secondary. Include database replication strategy, failover automation, RTO/RPO targets, and step-by-step recovery procedures.
Cloud migration execution plan 
We are migrating from AWS to GCP over 6 months. Create a detailed migration plan using the four-phase approach. Include workload assessment criteria, pilot selection, migration sequencing, risk mitigation, and success metrics for each phase.

ベストプラクティス

  • Use infrastructure as code (Terraform) to manage resources consistently across all cloud providers
  • Design for failure by assuming any single cloud region or provider can become unavailable
  • Implement comprehensive monitoring with cloud-agnostic tools like Prometheus and Grafana

回避

  • Building tightly coupled architectures that depend on proprietary cloud services without abstraction layers
  • Ignoring data transfer costs between cloud providers which can quickly escalate expenses
  • Attempting multi-cloud without proper team expertise in each provider leading to operational complexity

よくある質問

When should I use multi-cloud versus single cloud?
Use multi-cloud when you need vendor risk mitigation, regulatory compliance across regions, best-of-breed services, or improved negotiating leverage. Single cloud is simpler and often sufficient for startups or applications without strict availability requirements.
What is the biggest challenge with multi-cloud architectures?
Operational complexity is the primary challenge. Teams need expertise across multiple platforms, monitoring becomes fragmented, and debugging issues across clouds requires additional tooling and processes.
How do I avoid vendor lock-in when using cloud-native services?
Use abstraction layers like Kubernetes for compute, PostgreSQL-compatible databases, S3-compatible storage APIs, and infrastructure as code. Avoid proprietary services unless their benefits clearly outweigh lock-in risks.
What is the recommended disaster recovery pattern for multi-cloud?
Primary-Secondary pattern: Run production in one cloud with asynchronous replication to a secondary cloud. Use automated health checks and failover procedures. Test failover quarterly to ensure recovery objectives are met.
How much cost savings can I expect from multi-cloud?
Direct cost savings vary widely but typically range from 10-30% through competitive pricing and workload optimization. The larger value is often risk mitigation and negotiating leverage rather than direct cost reduction.
Should I start with multi-cloud or migrate later?
Design for cloud-agnostic architecture from the start using portable technologies, but deploy to a single cloud initially. Add additional providers when business needs justify the added complexity and operational overhead.

開発者の詳細

作成者

sickn33

ライセンス

MIT

リポジトリ

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/multi-cloud-architecture

参照

main

ファイル構成

📄 SKILL.md