9+ years running infrastructure that has to stay up — now building the same discipline into AWS, Terraform, and cloud architecture.
+ resource "engineer" "enyioma" { role = "IT Infrastructure Specialist" years_experience = 9 current_stack = [ "M365 / Entra ID", "Intune", "Hyper-V", "Fortinet", ] learning = [ "AWS", "Terraform", "least-privilege IAM design", ] based_in = "Lagos, Nigeria" target = "Cloud / Infrastructure roles, remote or relocation" }
I spend my days keeping M365, Entra ID, Hyper-V, and Fortinet infrastructure running for a hybrid aviation environment — corporate office and hangar systems both need to work, and both tend to break at inconvenient times.
What pulled me toward cloud wasn't a certification path — it was genuinely wanting to understand how the same reliability and access-control discipline I already practice translates into AWS. I like that a VPC and a Fortinet segment solve the same problem with different vocabulary, and that Terraform makes infrastructure changes reviewable the same way a DSC config does.
Most of what's below was built hands-on: provisioned, broken, debugged, and torn down for real — not just read about.
AWS (EC2, VPC, RDS, S3, IAM), Terraform, boto3
Entra ID, least-privilege IAM design, certificate-based auth
PowerShell, Python, Ansible, DSC
Hyper-V, Fortinet, Microsoft 365, network monitoring
A VPC with public/private subnet isolation, an RDS database proven unreachable from the internet, and a least-privilege IAM identity scoped iteratively against real AccessDenied errors — not guessed upfront.
A custom VPC, EC2 web server, and S3 bucket provisioned declaratively, with a dynamic AMI lookup instead of a hardcoded image ID, and a Python monitor reporting live status across all three.
Monitors Remote Desktop Services broker health independently of Server Manager's console, which can report a false "no deployment exists" error on legacy farm configurations. Alerts via Microsoft Graph with certificate-based auth.
Pings production network devices on a schedule, logs to SQLite, alerts via Teams, and only attempts auto-remediation on devices explicitly flagged safe — production gear stays monitor-only by design.
Three Microsoft Graph scripts automating identity, device, and license governance checks, running unattended via certificate-based app-only authentication.
The same server hardening goal — legacy feature removal, firewall enforcement, governed local admin — implemented twice, through DSC and Ansible, to prove the outcome independent of tooling.