Skip to content
Skills Library
DevOps & cloud · Planning

cloud-platforms

/cloud-platforms

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.

Licence
MIT
Last repository change
07.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
7
Scripts
0
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

What it does and when to use it

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.

Original author 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.

How it works

  1. Choose the right tier before you apply standards
  2. Common rules for every provider
  3. Provider references
Original SKILL.md headings · 40 lines, 401 words
SKILL.md preview
---
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.
Files in this package (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

Versions

The database has no other skills named cloud-platforms.

Database snapshot: 13.11.2026 · package version 9f85a4c8f62e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cloud-architect
    Designs multi-cloud and hybrid cloud architectures across AWS, GCP, and Azure. Use when designing cloud infrastructure or when the user mentions cloud architecture, AWS, GCP, Azure, or multi-cloud.
  • 100sota-cloud-infrastructure
    State-of-the-art cloud infrastructure architecture (2026). Applies when designing, building, or auditing cloud environments on AWS, GCP, or Azure — account/project structure and landing zones, IAM and workload identity, VPC/network design, DNS/TLS/CDN, compute selection…
  • 100cloud-networking
    Cross-platform comparison and architecture guidance for cloud networking across AWS, Azure, and GCP: VPC/VNet design, hybrid connectivity, security groups, transit architectures, private service access, and multi-cloud networking patterns. Use for \"cloud networking\", \"VPC…
  • 90cloud-engineer
    Guides cloud engineering on AWS, GCP, and Azure—landing zones and account structure, VPC/VNet networking, compute and autoscaling, object/block storage, managed databases and caches, serverless and messaging, DNS/CDN, cloud IAM and workload identity, multi-AZ/region reliability,…
  • 98terravision-cloud-diagrams
    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision. Use whenever the user asks to draw, diagram, sketch or visualize a system on AWS, Azure or Google Cloud, or one built from their services (Lambda, DynamoDB, S3, EC2,…
  • 100managed-kubernetes-eks-aks-gke
    Guides provisioning and configuring managed Kubernetes clusters on AWS EKS, Azure AKS, and Google GKE — cluster creation, node group/pool design, and per-cloud workload identity (IRSA on EKS, Azure AD Workload Identity on AKS, Workload Identity Federation on GKE) so pods get…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.