Designing an Enterprise Landing Zone in 2026: The Structural Decision Framework for Clients with Legacy and AI Ambition
🎯 El punto de partida En varios kickoffs de Landing Zone enterprise en LATAM este año se repite el mismo patrón de inventario: unos 40 servidores físicos que nadie quiere tocar porque el que sabía renunció en 2022, un cluster VMware con 200 y algo de VMs, la mitad de las aplicaciones en Windows Server 2016 cerca del fin de soporte extendido, y un roadmap que menciona "adoptar IA generativa" sin…
Several Landing Zone enterprises in LATAM have similar inventory patterns, including 40 physical servers, a VMware cluster with 200+ VMs, and applications nearing extended support end on Windows Server 2016. The requirement is to start without technical debt from the design. A common mistake is treating the design as a migration project to AWS, rather than designing a platform for the next 5-7 years.
A framework of structural decisions is proposed to address this, including a platform-oriented OU model, incorporating AWS Transform, and implementing Identity Center from the start. This approach considers factors such as regulatory requirements, like Chile's Law 21.719, and non-human identities.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
