hybrid-cloud-architect
starsforks
How to install hybrid-cloud-architect?
tranhieutt/software_development_department/hybrid-cloud-architect
$npx -y skills add tranhieutt/software_development_department --skill hybrid-cloud-architectDesigns hybrid cloud architectures connecting on-premises infrastructure with public cloud services. Use when designing systems spanning on-prem and cloud, or when the user mentions hybrid cloud or multi-environment architecture.
SKILL.md
| 1 | # Hybrid Cloud Architect |
| 2 | |
| 3 | Designs hybrid and multi-cloud architectures that bridge on-premises infrastructure (OpenStack, VMware, bare metal) with public cloud services (AWS, Azure, GCP). |
| 4 | |
| 5 | ## When to Use |
| 6 | |
| 7 | - Designing systems that span on-premises and cloud environments |
| 8 | - Planning workload placement across private and public clouds |
| 9 | - Migrating from on-prem to hybrid architecture |
| 10 | - User mentions hybrid cloud, multi-cloud, or cross-environment |
| 11 | |
| 12 | ## When NOT to Use |
| 13 | |
| 14 | - Single-cloud deployment (use cloud-architect instead) |
| 15 | - Pure infrastructure provisioning without architecture decisions (use devops-deploy) |
| 16 | - Application-level architecture without infrastructure concerns (use backend-architect) |
| 17 | |
| 18 | ## Workflow |
| 19 | |
| 20 | ### 1. Assess Requirements |
| 21 | |
| 22 | Gather constraints before designing: |
| 23 | |
| 24 | | Dimension | Questions | |
| 25 | |-----------|----------| |
| 26 | | Compliance | Data sovereignty? Regulatory frameworks (HIPAA, PCI-DSS, GDPR)? | |
| 27 | | Performance | Latency requirements? Data gravity? Real-time vs batch? | |
| 28 | | Budget | TCO targets? Existing licenses? CapEx vs OpEx preference? | |
| 29 | | Skills | Team expertise in cloud platforms? OpenStack experience? | |
| 30 | | Timeline | Migration urgency? Phased approach acceptable? | |
| 31 | |
| 32 | ### 2. Classify Workloads |
| 33 | |
| 34 | For each workload, determine placement: |
| 35 | |
| 36 | | Criteria | On-Prem | Public Cloud | Edge | |
| 37 | |----------|---------|-------------|------| |
| 38 | | Data sovereignty | Yes | No unless region-locked | Yes | |
| 39 | | Low latency (less than 10ms) | Yes | No unless co-located | Yes | |
| 40 | | Elastic scaling | No | Yes | No | |
| 41 | | Cost-sensitive steady-state | Yes | No | - | |
| 42 | | Managed services needed | No | Yes | No | |
| 43 | |
| 44 | ### 3. Design Connectivity |
| 45 | |
| 46 | Choose connectivity based on requirements: |
| 47 | |
| 48 | Options: |
| 49 | - VPN: Low cost, lower bandwidth, good for non-critical traffic |
| 50 | - Dedicated (Direct Connect / ExpressRoute / Interconnect): High bandwidth, low latency, SLA-backed |
| 51 | - SD-WAN: Multi-site, dynamic path selection, cost optimization |
| 52 | - Service mesh: For cross-cloud microservices communication (Istio, Linkerd) |
| 53 | |
| 54 | ### 4. Design Security Architecture |
| 55 | |
| 56 | Apply zero-trust across environments: |
| 57 | - Identity federation: AD/LDAP to cloud IAM (SAML/OIDC) |
| 58 | - Network segmentation: Micro-segmentation, security groups across clouds |
| 59 | - Encryption: In-transit (TLS) + at-rest, key management per environment |
| 60 | - Secret management: Centralized (Vault) or cloud-native (KMS/KeyVault) |
| 61 | - Compliance: Per-environment compliance controls, audit logging |
| 62 | |
| 63 | ### 5. Design Data Strategy |
| 64 | |
| 65 | | Pattern | Use When | Tools | |
| 66 | |---------|----------|-------| |
| 67 | | Active-active replication | RPO=0, RTO less than 1min | Database-native replication, Kafka | |
| 68 | | Active-passive | RPO less than 15min, RTO less than 1hr | Cross-cloud backup, DNS failover | |
| 69 | | Data mesh | Domain ownership, distributed teams | Data catalogs, federated queries | |
| 70 | | Edge preprocessing | IoT, real-time analytics | Edge compute to cloud aggregation | |
| 71 | |
| 72 | ### 6. Define Infrastructure as Code |
| 73 | |
| 74 | Multi-cloud IaC strategy: |
| 75 | - Terraform/OpenTofu: Cross-cloud resource provisioning |
| 76 | - Ansible: Configuration management |
| 77 | - Pulumi/CDK: Complex orchestration logic |
| 78 | - OPA/Conftest: Policy as Code |
| 79 | - GitOps (ArgoCD/Flux): Multi-environment deployment |
| 80 | |
| 81 | State management: |
| 82 | - Remote state with locking (S3+DynamoDB, Azure Storage, GCS) |
| 83 | - Separate state per environment, shared modules |
| 84 | - State migration plan for cross-cloud moves |
| 85 | |
| 86 | ### 7. Design Observability |
| 87 | |
| 88 | Unified monitoring across environments: |
| 89 | - Metrics: Prometheus + Thanos / Grafana Mimir (cross-cloud) |
| 90 | - Logs: Centralized logging (ELK/Loki) with per-environment collectors |
| 91 | - Traces: Distributed tracing (Jaeger/Tempo) across service boundaries |
| 92 | - Alerting: Unified alerting with environment-aware routing |
| 93 | - Cost monitoring: Per-cloud cost dashboards, anomaly detection |
| 94 | |
| 95 | ### 8. Plan Disaster Recovery |
| 96 | |
| 97 | | Tier | Strategy | RPO | RTO | Cost | |
| 98 | |------|----------|-----|-----|------| |
| 99 | | Tier 1 | Active-active multi-cloud | 0 | less than 1min | High | |
| 100 | | Tier 2 | Active-passive cross-cloud | less than 15min | less than 1hr | Medium-High | |
| 101 | | Tier 3 | Backup + manual failover | less than 24hr | less than 4hr | Medium | |
| 102 | | Tier 4 | Backup only | less than 24hr | less than 24hr | Low | |
| 103 | |
| 104 | DR automation: |
| 105 | - Automated failover triggers (health checks, circuit breakers) |
| 106 | - Runbook automation for failover procedures |
| 107 | - Regular DR testing schedule (quarterly minimum) |
| 108 | |
| 109 | ## Output |
| 110 | |
| 111 | Deliver: |
| 112 | - Architecture diagram: showing all environments, connectivity, data flow |
| 113 | - Workload placement matrix: workload to environment with justification |
| 114 | - Connectivity plan: network topology |
People who liked this also viewed
6 picksType
- microsoft-foundryDeploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval, prompt optimizer, Agent Optimizer scaffoSkillsJul 2026
- azure-deployExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application SkillsJul 2026
- azure-preparePrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wSkillsJul 2026
- azure-validate--- name: azure-validate description: "Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity pSkillsJul 2026
- azure-aigatewayConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbSkillsJul 2026
- azure-hosted-copilot-sdkOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
