AWS Vendor Lock-in: IAM and Architecture, Not Egress Fees

This analysis argues that AWS customer retention is driven primarily by architectural dependencies, specifically Identity and Access Management (IAM) and managed services, rather than data egress fees. Although AWS announced in March 2024 that it would waive egress fees for customers leaving the platform, the article contends this move was strategically timed ahead of the EU Data Act's full enforcement in 2027. The author asserts that egress costs are relatively minor and easily mitigated, making them an insignificant barrier for large enterprises. Instead, true lock-in exists in three layers: the widely discussed egress layer, the runtime layer involving proprietary managed services, and the deeply embedded IAM layer. The piece highlights that while AWS delivered on its initial promise of productive infrastructure without hardware ownership, the resulting architecture makes leaving increasingly difficult. It suggests that regulatory efforts focusing solely on switching charges miss the deeper technical complexities that bind customers to the platform. The article serves as a critical examination of cloud vendor mechanics, emphasizing that architectural design, not just pricing, dictates customer freedom and ownership of built systems.