I engineer cloud infrastructure into
automated. resilient.
production-ready systems.

Problem

Cloud foundations are harder to maintain when networking, compute, diagnostics, and deployment controls are configured inconsistently.

Design

Use reusable Terraform modules for network and compute components, remote state, diagnostics, and a GitHub Actions workflow with federated identity and an approval step.

Validation checklist

• Run terraform fmt -check and terraform validate.
• Review the Terraform plan before any apply.
• Confirm diagnostics and state configuration; document cleanup steps.

Problem

Manual changes in a cloud portal can leave deployed resources out of sync with the declared Terraform configuration.

Design

Schedule or trigger a workflow that authenticates with OIDC, refreshes state, creates a plan, and reports drift for review instead of silently applying changes.

Validation checklist

• Make a controlled test change in a disposable environment.
• Confirm the plan reports the difference.
• Verify the workflow does not auto-apply and does not store long-lived cloud credentials.

Problem

Learning cloud infrastructure across providers requires understanding both shared IaC patterns and provider-specific resource models.

Design

Keep Azure and AWS deployments independently understandable, using Terraform to define networking and compute resources with provider-specific configuration.

Validation checklist

• Run format and validation checks for each configuration.
• Inspect each provider's plan before provisioning.
• Record outputs and destroy test resources to avoid unnecessary cloud spend.