IT AI Skill

Infrastructure Provisioning

Automate infrastructure provisioning using Infrastructure as Code, cloud resource management, environment deployment, and configuration management. Use when provisioning cloud resources, managing IaC templates, automating environment setup, or standardizing...

Infrastructure Provisioning & IaC

Automate infrastructure provisioning and management using Infrastructure as Code principles for consistency and scalability.

Workflow

1. Infrastructure Architecture & Design

  1. Infrastructure blueprint development:
  1. Infrastructure standards definition:
  1. Platform and tool selection:

2. IaC Development & Management

  1. Module and template development:
  1. State management and collaboration:
  1. Code review and governance:

3. Environment Deployment & Orchestration

  1. CI/CD for infrastructure:
  1. Deployment execution:
  1. Configuration drift management:

4. Cloud Resource Optimization

  1. Cost optimization:
  1. Performance optimization:
  1. Resource lifecycle management:

5. Security & Compliance Automation

  1. Security by default:
  1. Compliance automation:
  1. Disaster recovery automation:

Templates & Frameworks

Infrastructure Module Template

TERRAFORM MODULE — [Service Name]
===================================

MODULE: modules/[service-name]
  Purpose: [description of what this module provisions]
  Owner: [team/person]
  Last updated: [date]

INPUT VARIABLES:
  environment     (string) — dev, staging, prod
  region          (string) — primary AWS/Azure/GCP region
  instance_type   (string) — compute instance size
  min_instances   (number) — minimum running instances
  max_instances   (number) — maximum auto-scaling instances
  enable_monitoring (bool) — enable CloudWatch/Datadog monitoring
  tags            (map) — resource tagging

OUTPUT VALUES:
  endpoint       — service endpoint URL
  security_group_id — SG ID for resource access
  alb_dns_name   — load balancer DNS name
  rds_endpoint   — database endpoint

PROVISIONED RESOURCES:
  — Auto Scaling Group (min: ${min}, max: ${max})
  — Application Load Balancer (HTTPS, path-based routing)
  — RDS Instance (Multi-AZ, encrypted, automated backups)
  — Security Groups (restricted ingress/egress)
  — CloudWatch Alarms (CPU, memory, error rate)
  — S3 Bucket (logs, encrypted, versioned)
  — IAM Roles (least privilege, assumed by instances)

USAGE EXAMPLE:
  module "web-app" {
    source = "./modules/web-app"
    environment = "production"
    region = "us-east-1"
    instance_type = "t3.medium"
    min_instances = 2
    max_instances = 10
    enable_monitoring = true
    tags = {
      owner = "platform-team"
      cost_center = "engineering"
      application = "web-frontend"
    }
  }

DEPLOYMENT NOTES:
  — Estimated monthly cost: ~$450 (dev), ~$2,100 (prod)
  — RTO: 15 minutes (auto-scaling + ALB)
  — RPO: 5 minutes (RDS automated backups)
  — Requires: VPC module, DNS module

Infrastructure Deployment Pipeline

INFRASTRUCTURE CI/CD PIPELINE
===============================

STAGE 1: VALIDATION
  — Terraform fmt (code formatting)
  — Terraform validate (syntax check)
  — Checkov/tfsec (security scanning)
  — Cost estimation (infracost)
  — Policy compliance check (Sentinel/OPA)

STAGE 2: PLAN
  — Terraform plan (preview changes)
  — Diff review and annotation
  — Cost impact assessment
  — Stakeholder notification (if production)

STAGE 3: APPROVAL
  — Development: auto-approve
  — Staging: team lead approval
  — Production: 2-person approval + change manager

STAGE 4: APPLY
  — Terraform apply (execute changes)
  — State update and backup
  — Deployment log capture

STAGE 5: VALIDATION
  — Health check execution
  — Smoke test execution
  — Monitoring alert verification
  — Performance baseline comparison
  — Compliance scan post-deployment

STAGE 6: DOCUMENTATION
  — Change log update
  — Runbook update (if needed)
  — Stakeholder notification
  — Rollback procedure verification

ROLLBACK TRIGGER:
  — Health check failure > 3 consecutive
  — Error rate > 5% for 5 minutes
  — Latency p95 > 2x baseline
  — Manual trigger by on-call engineer

Integration Points

Edge Cases

Output

Infrastructure Provisioning Dashboard

INFRASTRUCTURE STATUS — April 2025
===================================

ENVIRONMENT INVENTORY:
  Development: 12 environments (47 resources)
  Staging: 3 environments (134 resources)
  Production: 2 environments (387 resources)
  DR: 1 environment (387 resources — synchronized)

PROVISIONING METRICS:
  IaC coverage: 94% (target: >95% ⚠)
  Manual changes detected: 7 (remediation in progress)
  Configuration drift: 2.3% (target: <1% ⚠)
  Deployments this month: 47 (34 successful, 1 rollback, 12 pending)

CLOUD RESOURCE COST:
  Monthly spend: $127,400 (↓ 4.2% from last month ✓)
  Reserved instance coverage: 78%
  Spot instance utilization: 23% (batch workloads)
  Right-sizing savings identified: $8,400/month
  Unused resources flagged: 12 ($2,300/month waste)

SECURITY POSTURE:
  Encryption at rest: 99.2% resources ✓
  Security group compliance: 97.8% ✓
  IAM policy compliance: 95.4% ✓
  Security scan issues (critical): 0 ✓
  Open vulnerabilities (medium): 4 (patching scheduled)

COMPLIANCE STATUS:
  SOC 2 compliance: 98.7% ✓
  HIPAA compliance: 99.1% ✓
  PCI-DSS scope: 3 systems (all compliant ✓)
  Audit evidence automated: 94%
  Last compliance scan: April 14 (passed)

DEPLOYMENT PERFORMANCE:
  Avg deployment time: 8.4 minutes
  Deployment success rate: 97.9% ✓
  Mean time to rollback: 3.2 minutes
  Zero-downtime deployments: 92%

AUTOMATION METRICS:
  Auto-scaling events: 234 this month
  Automated remediation: 67 actions
  Scheduled maintenance: 4 completed (0 issues)
  Backup success rate: 99.7% ✓

Trigger Phrases

"infrastructure as code", "IaC", "cloud provisioning", "Terraform", "environment deployment", "configuration management", "auto-scaling", "resource tagging", "infrastructure template", "CI/CD infrastructure", "drift detection", "right-sizing", "multi-cloud", "infrastructure pipeline"