greg@stengel:~$ whoami

Greg Stengel

Staff Infrastructure Engineer · Remote · Palm City, FL

Two decades making other people’s clouds behave.

AWS, Kubernetes, observability, and the identity plumbing nobody thanks you for — and lately, the AI agents helping run it all.

// certified

// the arc

  1. 01

    Foundations

    Datacenters, colo, and a few hundred web servers that didn’t care about your feelings. Apache, WebSphere, IIS, RHEL, VMware — keep it up, keep it patched, write down what broke.

  2. 02

    Observability

    Fell into Splunk and stayed for years. Multi-datacenter deployments into the thousands of nodes, automated rollout, and the dashboards that turn noise into something a human can read. Later, the same story in Elastic.

  3. 03

    Managed cloud

    AWS — plus Azure and GCP — as an architect, then leading the teams doing it. Infrastructure as code, automated backups and compliance, recurring costs killed by trading third-party tooling for native services.

  4. 04

    Platform & identity

    Multi-account landing zones, Kubernetes across regions, GitOps with ArgoCD, and the identity plumbing nobody thanks you for: Identity Center on Okta, Vault, KMS, and least-privilege guardrails.

  5. 05

    Cloud meets agents

    Now: the seam where infrastructure meets AI agents — using them to take delivery from weeks to days, and keeping them honest enough to trust near prod.

// the toolkit

Cloud

AWS home turf · Azure · GCP

Observability

Splunk · Elastic · Prometheus + Grafana · Datadog

IaC & GitOps

Terraform / Terragrunt · CloudFormation · ArgoCD · GitLab / GitHub / Jenkins CI

Containers & Platform

Kubernetes / EKS · Helm · ingress

Security & Identity

IAM Identity Center · Okta · Vault · KMS · AWS Config · least-privilege

Automation & Code

Python · Bash · Lambda / EventBridge · SSM

Foundations

Linux / RHEL · VMware · Puppet / Ansible

// signature builds

  1. Multi-datacenter Splunk platform

    2,500+ nodes across three datacenters; Puppet-automated forwarder rollout; scripted index config.

  2. Clustered Splunk-in-AWS monitoring

    Per-customer apps with 50+ dashboards each; custom TAs and sourcetypes; summary indexing for cross-resource correlation.

  3. Backup & compliance automation

    CloudFormation + AWS Config + SNS + tagging standards; Cloud Custodian guardrails; native AWS Backup replacing third-party tools (thousands in recurring cost removed).

  4. Hybrid file-sync pipeline

    Lambda / S3 / DynamoDB mapping SFTP↔SMB; automated sync between AWS and on-prem.

  5. Public-IP consolidation

    Automation to migrate and consolidate public IPs, cutting per-application IP cost.

  6. Identity modernization

    Legacy IAM → Identity Center on Okta; permission sets, customer-managed policies, reusable Terraform / Terragrunt modules via GitLab CI.

  7. Multi-region EKS access path

    Identity Center → k8s RBAC → ArgoCD, with Vault secrets and ingress, across three regions.

// on the record

One of the most talented engineers I’ve ever worked with — instrumental in building key automation and reporting systems, and always willing to teach others.
— DevOps / SRE team lead
He automated the entire Splunk setup for thousands of servers, self-taught, and documented it so well it was still in use two years later.
— former manager
Detail-oriented with a broad set of technical skills — always eager to learn, and never backs down from a challenge.
— VP, managed services
Dove into technologies he had no background in — Splunk, Python, cloud — and quickly became the person the team relied on.
— project manager

// after hours

homelab · all green

// read the receipts

the blog

// the stack

It’s the wall drifting behind all this. Hover a logo to name it — cloud, containers, observability, and a closet full of Linux.

// find me