cloud-platforms
/cloud-platforms
Podaje standardy projektowania infrastruktury chmurowej i lokalnej, np. Azure, AWS, GCP lub centrum danych, dobrane do wielkości projektu.
- Autor
- hoangminhung ↗
- Repozytorium
- devops-ai-kit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 07.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 7
- Skrypty
- 0
- Komentarze HTML
- 1
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 07.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Podaje standardy projektowania infrastruktury chmurowej i lokalnej, np. Azure, AWS, GCP lub centrum danych, dobrane do wielkości projektu.
Oryginalny opis (EN)
Design standards for cloud and on-prem infrastructure — Azure, AWS, GCP, Hetzner, OVHcloud and bare-metal data centers — organised by tier (baseline, production, enterprise landing zone) so recommendations match the real size of the project. Use whenever designing, provisioning or reviewing cloud networking, identity, managed Kubernetes (AKS/EKS/GKE), landing zones, VPC/VNet layouts or data-center infrastructure, even if the user only names a single provider service.
Jak działa
- Choose the right tier before you apply standards
- Common rules for every provider
- Provider references
Podgląd SKILL.md
--- name: cloud-platforms description: Design standards for cloud and on-prem infrastructure — Azure, AWS, GCP, Hetzner, OVHcloud and bare-metal data centers — organised by tier (baseline, production, enterprise landing zone) so recommendations match the real size of the project. Use whenever designing, provisioning or reviewing cloud networking, identity, managed Kubernetes (AKS/EKS/GKE), landing zones, VPC/VNet layouts or data-center infrastructure, even if the user only names a single provider service. when_to_use: Use when designing, deploying or reviewing infrastructure on Azure, AWS, GCP, Hetzner, OVH or on-premise — networking, identity, AKS/EKS/GKE, landing zone, VPC/VNet. Vietnamese triggers — "thiết kế, triển khai hoặc review hạ tầng trên Azure, AWS, GCP, Hetzner, OVH hoặc on-premise", "mạng, định danh, AKS/EKS/GKE, landing zone, VPC/VNet". --- # Cloud & on-premise infrastructure standards <!-- devops-ai-kit · Last reviewed: 2026-10-28 --> ## Choose the right tier before you apply standards Suggesting an enterprise architecture for a small project is over-engineering: it costs money, it costs operations work, and the user will then ignore even the good advice. Always decide the tier first, and write the chosen tier in the plan / ADR. | Tier | When | Apply | |---|---|---| | **Baseline** | Every project, including dev / PoC used for more than a few days | The "Baseline" part of each provider | | **Production** | Real users, real data, an uptime commitment | Baseline + "Production" | | **Enterprise landing zone** | Many teams / many subscriptions-accounts, compliance needs, a platform team | All three tiers | If the tier is not clear, ask the user. Do not pick Enterprise by default. ## Common rules for every provider - **MUST** Create every resource with IaC (Terraform / OpenTofu). Manual console work is only for troubleshooting. If you must create something by hand, write it down and import it into IaC later. - **MUST** Identity does not use long-lived static keys: CI uses OIDC federation, workloads use managed / workload identity. If a static key cannot be avoided, it has an expiry date and is rotated. - **MUST** Standard tags / labels (`Environment`, `Owner`, `Project`, `ManagedBy`) to track cost and ownership. - **SHOULD** Services that hold data (database, storage, key vault) are not public. Access them through a private endpoint / private link / private network. - **SHOULD** Encryption at rest is on by default (usually built in). Customer-managed keys (CMK) are **CONTEXT**: use them when compliance requires it. - **SHOULD** Set a budget and cost alerts from day one (see skill `finops`). - **SHOULD** Plan CIDRs once for all environments. Avoid overlap with networks you will peer / VPN / connect on-prem. Changing a CIDR later usually means rebuilding. ## Provider references Read the matching file in `references/` when you work with that provider: - Azure (including AKS): `references/azure.md`. To build AKS, also read skill `playbook-aks`. - AWS (including EKS): `references/aws.md` - GCP (including GKE): `references/gcp.md` - Hetzner: `references/hetzner.md` - OVHcloud: `references/ovh.md` - On-premise / bare metal: `references/on-premise.md` The reference files describe the **design direction**. Terraform attribute names and specific features change between provider versions: check the provider docs for the exact version before you write code.
Pliki w paczce (7)
- SKILL.md 3 KB
- references/aws.md 2 KB
- references/azure.md 2 KB
- references/gcp.md 1 KB
- references/hetzner.md 1 KB
- references/on-premise.md 1 KB
- references/ovh.md 1 KB
Wersje
W bazie nie ma innych skilli o nazwie cloud-platforms.
Migawka bazy z 13.11.2026 · wersja paczki 9f85a4c8f62e (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100cloud-architect
Projektuje architektury multi-cloud i hybrydowe w AWS, GCP i Azure. - 100sota-cloud-infrastructure
Prowadzi przez projektowanie i audyt środowisk chmurowych AWS, GCP i Azure: struktura kont, IAM, sieci VPC, DNS, wybór mocy obliczeniowej, backup, FinOps i odtwarzanie po awarii. - 100cloud-networking
Porównuje i doradza w architekturze sieci chmurowych AWS, Azure i GCP: projekt VPC i VNet, łączność hybrydowa, grupy bezpieczeństwa, architektury tranzytowe, prywatny dostęp do usług i sieci multi-cloud. - 90cloud-engineer
Pomaga projektować i obsługiwać zasoby AWS, GCP i Azure: sieci, przechowywanie danych, bazy, IAM, kopie zapasowe i koszty. - 98terravision-cloud-diagrams
Rysuje diagramy architektury chmurowej AWS, Azure i GCP z oficjalnymi ikonami dostawców, na podstawie opisu usług. - 100managed-kubernetes-eks-aks-gke
Prowadzi tworzenie zarządzanych klastrów Kubernetes na AWS EKS, Azure AKS i Google GKE: klaster, projekt grup węzłów oraz tożsamość workloadów (IRSA, Azure AD Workload Identity, Workload Identity Federation) bez długotrwałych kluczy.