Private access in a VPC: designing for services that should not be public
Notes from building a private-access lab: subnet boundaries, routing intent, and the practical questions that make an architecture safer to operate.
Read project notes →ALEJANDRO SALAZAR · PORTFOLIO & BLOG
TECH STACK
01 / FIELD NOTES
Notes from building a private-access lab: subnet boundaries, routing intent, and the practical questions that make an architecture safer to operate.
Read project notes →A short checklist for inputs, outputs, naming, and the operational story around the code.
Choosing boring, maintainable hosting for a developer portfolio.
02 / BUILT IN PUBLIC
Real work, concise context.
A hands-on infrastructure lab focused on keeping service traffic private and making the network intent visible in code.
A production-minded assistant project built around log datasets, incident postmortems, and labeled debugging cases.
03 / ABOUT THIS SPACE
This is not a feed. It is a small, searchable record of how I think through cloud systems, backend services, and automation—what I chose, what I would change, and why.