thesoftwarehouse/tsh-designing-multi-cloud-architecture
.github/skills/tsh-designing-multi-cloud-architecture/SKILL.md
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 leveraging best-of-breed services from multiple providers.
$ install --global
skillsauthnpx skillsauth add thesoftwarehouse/copilot-collections tsh-designing-multi-cloud-architectureInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 11:58 PM9.7s3 files scanned
SKILL.md
- name:
- tsh-designing-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 leveraging best-of-breed services from multiple providers.
Multi-Cloud Architecture
Decision framework and patterns for architecting applications across AWS, Azure, and GCP.
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 | 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
- Use reserved/committed capacity (30-70% savings)
- Leverage spot/preemptible instances
- Right-size resources
- Use serverless for variable workloads
- Optimize data transfer costs
- Implement lifecycle policies
- Use cost allocation tags
- 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
Process
- Assess requirements → Identify drivers (DR, compliance, best-of-breed, cost)
- Choose pattern → Select from patterns above based on requirements
- Map services → Use service comparison tables to select equivalents
- Design abstraction → Use Kubernetes + Terraform for portability
- Plan networking → Design cross-cloud connectivity (VPN, interconnect)
- Implement IaC → Use
tsh-implementing-terraform-modulesskill - Set up observability → Unified monitoring across clouds
- Document runbooks → Cloud-specific operational procedures
Checklist
- [ ] Multi-cloud drivers documented (DR, compliance, vendor diversification)
- [ ] Service equivalents mapped across target clouds
- [ ] Abstraction layer chosen (Kubernetes, Terraform, or both)
- [ ] Cross-cloud networking designed and secured
- [ ] Identity federation configured (single IAM source of truth)
- [ ] Unified monitoring and logging implemented
- [ ] Cost allocation and tracking across clouds
- [ ] DR/failover procedures tested
- [ ] Team trained on all target cloud platforms
Anti-Patterns
| ❌ Don't | ✅ Do | |----------|-------| | Use proprietary services for portability needs | Choose cloud-agnostic alternatives (K8s, PostgreSQL) | | Duplicate everything across clouds | Be intentional about what runs where | | Manage each cloud differently | Use unified IaC and observability | | Ignore data transfer costs | Design to minimize cross-cloud traffic |
Reference Files
references/service-comparison.md- Complete service comparisonreferences/multi-cloud-patterns.md- Architecture patterns
Related Skills
tsh-implementing-terraform-modules- For IaC implementationtsh-optimizing-cloud-cost- For cost management
Related Skills
thesoftwarehouse/tsh-writing-hooks
development
VerifiedTrustedCommunity
Custom hook and composable patterns — naming, composition, stable return shapes, lifecycle cleanup, and testing strategies. Use when writing reusable logic units (React hooks, Vue composables), refactoring logic into hooks, debugging hook behavior, or reviewing hook implementations.
206SKILL.mdUpdated Apr 15, 2026
thesoftwarehouse/tsh-ui-verifying
testing
VerifiedTrustedCommunity
UI verification criteria, structure checklists, severity definitions, and tolerance rules for comparing implementations against Figma designs. Use for verifying UI matches design, understanding what to check, and determining acceptable differences.
206SKILL.mdUpdated Apr 15, 2026
thesoftwarehouse/tsh-transcript-processing
development
VerifiedTrustedCommunity
Clean raw workshop or meeting transcripts from small talk, filler words, and off-topic tangents. Extract and structure business-relevant content into a standardized format with discussion topics, key decisions, action items, and open questions.
206SKILL.mdUpdated Apr 15, 2026
thesoftwarehouse/tsh-technical-context-discovering
development
VerifiedTrustedCommunity
Discover and establish technical context before implementing any feature. Prioritize project instructions, existing codebase patterns, and external documentation in that order. Use for any task requiring understanding of project conventions, coding standards, architecture patterns, and established practices before writing code.
206SKILL.mdUpdated Apr 15, 2026