East Freetown, Massachusetts
I work on AWS foundations, hybrid networks, identity, and the systems around them. I started on the helpdesk, with the person who had a problem in front of them.
The morning
There was a time in my life when everything felt uncertain. Not the kind of uncertainty you can easily ignore, but the kind that sits with you quietly and follows you throughout the day.
I sat by the window. The sky was still dark, but you could tell something was about to change. Slowly, almost quietly, the first light started to appear.
Progress doesn't always feel like progress when you're in the middle of it. Just because you can't see the full picture yet doesn't mean nothing is happening.
I didn't need everything to be perfect before moving forward. I didn't need to have every step figured out. What I needed was to keep going, even when things weren't clear.
That is the part I keep on this page. The rest of that morning, and the work that followed it, is written out here.
Bay State IT
At Bay State IT I was not thinking about architecture. I was trying to understand why something that worked yesterday had stopped working today.
People called with what they could see. A login that failed. A file that was not where it had been. A machine that was fine until it was not. I got interested in the cause.
A call starts at one machine. Stay with it and it keeps opening into the system around that machine.
What the work turned into
These are not a list of skills. They are the parts of an environment that became my responsibility as the work got larger.
Control Tower, Landing Zone Accelerator, multi-account estates.
I ended up here when a single account stopped being something you could keep in your head. The work became an estate someone new could map.
The same line
A healthcare landing zone
A multi-account AWS foundation I deploy and operate, aligned to HIPAA and HITRUST. Choose a layer. The drawing follows it.
Microsoft Entra ID over SAML, SCIM provisioning, permission sets, MFA, and Client VPN. One place to grant access, and one place to take it back.
Evidence
Not a catalog. Environments I stayed in long enough to know where they break. On a wide screen, move through them sideways.
Field notes
Nothing here arrived as a slogan. It is what I started doing after I had been wrong, or late, or unclear.
If I put my name on a design, I own what happens in operations too: certificates, integrations, drift, and handoff quality.
Engineers need specifics, and non-engineers still need clear trade-offs. I aim for language both groups can act on.
Security and scale are design decisions, not late-stage add-ons. It is always cheaper to argue in design than in incident review.
I trust evidence: logs, metrics, runbooks, and clear change history. Process should match how failures actually happen.
What is sold and what the platform can sustain should describe the same reality. I push back when that gap grows.
Documentation is part of delivery. Good notes and diagrams are how you respect the next operator and your future self.
Still unfinished
The work tends to be an AWS foundation, a hybrid network, identity, research computing, storage and recovery, or a move to Microsoft 365 that has to be quiet on Monday morning.
If something here connects with what you are working through, write to me.