IaC — Terraform

Service Summary

PES implements Infrastructure as Code using HashiCorp Terraform to deploy and manage resources across AWS, Oracle OCI, and Microsoft Azure. Our approach uses reusable modules, parameter files (variables.tf), local values (locals.tf), and environment-specific variable files (terraform.tfvars).

Note: The IaC strategies and code examples are recommendations based on HashiCorp best practices. Every plan is tailored to your existing codebase, state backend, and provider versions.

Capabilities

Deploy Resources via Terraform — Reusable HCL with locals, variables, and outputs.
Manage Existing Code — Refactor, update provider versions, optimize state.
Import Existing Resources — Use terraform import to bring orphaned resources under management.

AWS — EC2 with locals & variables

# main.tf — AWS EC2 with reusable locals and variables
locals {
  environment = var.environment
  common_tags = {
   Environment = local.environment
   ManagedBy   = "Terraform"
   Owner       = "PES"
  }
}

resource "aws_instance" "app" {
  ami           = var.ami_id
  instance_type = var.instance_type
  subnet_id     = aws_subnet.main.id
  tags          = local.common_tags
}

See full files: variables.tf | locals.tf | terraform.tfvars

OCI — Compute with provider config

# main.tf — OCI Compute with provider and locals
provider "oci" {
  region = var.region
}

locals {
  compartment_id = var.compartment_ocid
  common_tags = {
   Environment = var.environment
   ManagedBy   = "Terraform"
  }
}

resource "oci_core_instance" "app" {
  availability_domain = data.oci_identity_availability_domains.ads.availability_domains[0].name
  compartment_id     = local.compartment_id
  shape              = var.instance_shape
  display_name       = "app-server-${var.environment}"
  source_details {
   source_type = "image"
   source_id   = var.image_ocid
  }
}

See: variables.tf | locals.tf

Azure — VM with azurerm provider

# main.tf — Azure Virtual Machine with azurerm
provider "azurerm" {
  features {}
}

locals {
  location = var.location
  common_tags = {
   Environment = var.environment
   ManagedBy   = "Terraform"
  }
}

resource "azurerm_virtual_machine" "app" {
  name                = "app-vm-${var.environment}"
  location            = local.location
  resource_group_name = var.resource_group_name
  vm_size             = var.vm_size
  network_interface_ids = [azurerm_network_interface.app.id]
  tags = local.common_tags
}

See: variables.tf | locals.tf

Implementation Plan

Phase 1

Infrastructure Assessment — Weeks 1–2

Inventory existing resources, identify IaC candidates, assess state management maturity. CSF: Identify ISO: A.8

Phase 2

Module Design — Weeks 3–4

Reusable module architecture, locals convention, variables structure, output design. CSF: Govern ISO: A.5

Phase 3

Terraform Development — Weeks 5–6

HCL authoring, state backend configuration (S3, OCI Object Storage, Azure Storage), CI/CD integration. CSF: Protect ISO: A.12

Phase 4

Import & Validation — Weeks 7–8

terraform import for existing resources, plan/apply validation, drift detection setup. CSF: Detect ISO: A.18

Phase 5

Documentation & Handoff — Week 9

Runbooks, pipeline integration, knowledge transfer, and team training. CSF: Respond ISO: A.16

Workflow Diagram — Terraform Lifecycle

flowchart LR; A[Assess Infrastructure] --> B[Design Modules]; B --> C[Write HCL Code]; C --> D[Import Resources]; D --> E[Validate: Plan / Apply]; E --> F[CI/CD Pipeline]; F --> G[Documentation Handoff]

Implementation Timeline

Phase	Activity	Duration	CSF 2.0	ISO 27001
1	Assessment	Weeks 1–2	Identify	A.8
2	Module Design	Weeks 3–4	Govern	A.5
3	Development	Weeks 5–6	Protect	A.12
4	Import & Validation	Weeks 7–8	Detect	A.18
5	Documentation	Week 9	Respond	A.16

Why Businesses Will Benefit

Infrastructure as Code eliminates snowflake servers, enables disaster recovery through codified environments, and makes compliance audits trivial — your infrastructure IS documentation, version-controlled and reviewable. PES brings production Terraform experience across AWS, OCI, and Azure, including importing hundreds of orphaned resources into state management. The included example code shows our approach: reusable, parameterized, and production-tested.

Infrastructure as Code — Terraform