I design, automate and operate cloud platforms with a focus on repeatability, secure delivery and production reliability. My work connects infrastructure architecture, Kubernetes, CI/CD, GitOps, observability, incident response and platform security so teams can ship changes safely and operate systems with clear evidence.
|
AWS and Azure foundations, networking, identity, multi-environment design, EKS/AKS, capacity and production operations. |
Terraform, Terragrunt, CloudFormation, Jenkins, GitHub Actions, GitLab CI/CD, Argo CD and rollback-ready delivery. |
Prometheus, Grafana, Loki, CloudWatch, incident response, RCA, least-privilege IAM, secrets and security controls. |
Verify AWS credential on Credly
| Azure Enterprise Landing Zone Live-validated AKS landing-zone project with Terraform, CI checks, architecture evidence and cost-controlled operations. |
Internal Developer Platform Internal platform engineering project with Kubernetes guardrails, namespace policies, golden-path delivery and validation evidence. |
Multi-Region DR Platform Disaster recovery engineering project with RTO/RPO targets, failover runbook, recovery workflow and validation evidence. |
Event-Driven Serverless Platform Event-driven serverless engineering project with queue processing, function handler, audit path and failure handling. |
Additional engineering work lives across my repositories; this section highlights four cloud projects with architecture, implementation, validation evidence and cost-control discipline.
| Cloud Platform Infrastructure Terraform foundation for multi-environment AWS and Kubernetes platform provisioning. |
Cloud Platform App Containerized application with tests, security scanning and Jenkins CI. |
Cloud Platform GitOps Argo CD and Kustomize delivery configuration for staged Kubernetes releases. |
Cloud Platform Ansible Repeatable Linux and NGINX automation with validation and idempotent operations. |
Jenkins CI Pipeline CI pipeline pattern for container builds, GitOps delivery and Kubernetes deployment. |
| Cloud DevOps MCP Server Model Context Protocol server for infrastructure risk review, incident runbooks, CI/CD readiness and SLO error budget analysis. |
- Infrastructure and delivery changes are version-controlled and reviewable.
- Environments are reproducible from code rather than dependent on manual setup.
- Security controls are built into the delivery path.
- Production deployments include health checks, rollback paths and measurable verification.
- Observability is part of platform design, with operational claims tied to evidence and validation.
| Portfolio alexemekagodwin.com |
LinkedIn linkedin.com/in/alexcgodwin |
Email alex.godwin@alexemekagodwin.com |
| Discipline | Technical implementation | Operational focus |
|---|---|---|
| Cloud & identity | Azure landing zone, GCP foundations | Terraform, networking, access policies and validation |
| Delivery & GitOps | Jenkins CI, GitOps release definitions | Reviewed changes, environment boundaries and rollback |
| OS automation | Ansible Linux platform | Serial rollout, config verification and idempotency |
| Reliability engineering | Disaster recovery, event-driven platform | Data durability, recovery drills, retries and failure isolation |
| Terraform internals | State recovery, module testing | Safe state changes, native tests, CI and failure handling |
| AI operations | AWS AIOps and SSM, Cloud DevOps MCP | Least privilege, evidence-based diagnostics and human approvals |
How to verify this work: architecture, security boundaries, unit/integration tests, and the distinction between runnable code and actual cloud deployment.