agentleFS
d-padmanabhand-padmanabhan/agent-engineering-handbook/skills/cloud-platforms/SKILL.md

cloud-platforms

Skill17 starsChanged 55 days agoMITView on GitHub

Cloud platform best practices for AWS, Azure, GCP, and Cloudflare. Covers Zero Trust architecture, IAM patterns, EKS/AKS/GKE configurations, serverless patterns, and multi-cloud strategies. Use when working with cloud infrastructure, AWS services, Azure resources, GCP projects, Cloudflare Workers, or when asking about cloud architecture and deployment.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Zero Trust: Never trust, always verify

    line 10
  2. Distinctive:

    Infrastructure as Code: All infrastructure defined in code

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cloud Platforms

Core Principles

  1. Zero Trust: Never trust, always verify
  2. Least Privilege: Minimum necessary permissions
  3. Defense in Depth: Multiple layers of security
  4. Infrastructure as Code: All infrastructure defined in code
  5. Observability: Comprehensive logging, metrics, and tracing

Platform Selection

Use CaseRecommended
Enterprise, broad servicesAWS
Microsoft ecosystemAzure
Data/ML workloadsGCP
Edge/CDN, simple serverlessCloudflare

AWS Quick Reference

IAM Best Practices

# EKS Pod Identity (Recommended over IRSA)
resource "aws_eks_pod_identity_association" "app" {
  cluster_name    = aws_eks_cluster.main.name
  namespace       = "default"
  service_account = "app"
  role_arn        = aws_iam_role.app_pod_identity.arn
}

VPC Pattern

# Private subnets only - Zero Trust
resource "aws_subnet" "private" {
  count             = 3
  vpc_id            = aws_vpc.main.id
  cidr_block        = "10.16.${count.index + 1}.0/24"
  availability_zone = data.aws_availability_zones.available.names[count.index]

  tags = {
    Name = "private-subnet-${count.index + 1}"
    Type = "Private"
  }
}

Essential Services

  • EKS: Managed Kubernetes
  • Lambda: Serverless compute
  • RDS/Aurora: Managed databases
  • S3: Object storage
  • CloudFront: CDN
  • Secrets Manager: Secret storage

Azure Quick Reference

Managed Identity

resource "azurerm_user_assigned_identity" "app" {
  name                = "app-identity"
  resource_group_name = azurerm_resource_group.main.name
  location            = azurerm_resource_group.main.location
}

Essential Services

  • AKS: Managed Kubernetes
  • Azure Functions: Serverless
  • Azure SQL: Managed databases
  • Blob Storage: Object storage
  • Azure CDN: Content delivery
  • Key Vault: Secret management

GCP Quick Reference

Workload Identity

resource "google_service_account" "app" {
  account_id   = "app-sa"
  display_name = "Application Service Account"
}

resource "google_project_iam_member" "app" {
  project = var.project_id
  role    = "roles/storage.objectViewer"
  member  = "serviceAccount:${google_service_account.app.email}"
}

Essential Services

  • GKE: Managed Kubernetes
  • Cloud Functions: Serverless
  • Cloud SQL: Managed databases
  • Cloud Storage: Object storage
  • Cloud CDN: Content delivery
  • Secret Manager: Secrets

Cloudflare Quick Reference

Workers

export default {
  async fetch(request, env) {
    const url = new URL(request.url);
    
    if (url.pathname === '/api/data') {
      const data = await env.MY_KV.get('key');
      return new Response(JSON.stringify({ data }), {
        headers: { 'Content-Type': 'application/json' }
      });
    }
    
    return new Response('Hello World');
  }
};

Essential Services

  • Workers: Edge compute
  • Pages: Static site hosting
  • D1: SQLite database
  • KV: Key-value storage
  • R2: S3-compatible storage

Security Checklist

  • IAM roles with least privilege
  • Network segmentation (VPCs, security groups)
  • Encryption at rest and in transit
  • Secret management (not in code)
  • Audit logging enabled
  • Multi-factor authentication
  • Regular security assessments

Detailed References

  • AWS: See references/aws.md for EKS, IAM, networking
  • Azure: See references/azure.md for AKS, identity
  • GCP: See references/gcp.md for GKE, IAM
  • Cloudflare: See references/cloudflare.md for Workers, Pages
  • Identity protocols: See ../security-testing/references/identity-access.md for OIDC/PKCE and SAML/ADFS validation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.