The cloud computing landscape, dominated by Amazon Web Services (AWS), is often lauded for its innovation and transformative power. Yet, a recent reflection from a long-time user on Hacker News, titled "20 years on AWS and never not my job," offers a candid counterpoint to the prevailing narrative of effortless scalability and simplified operations. This perspective delves into the persistent complexities and ongoing demands of managing cloud infrastructure, even after two decades of experience with the platform.\n\nThe author highlights that despite the advancements in AWS services, the fundamental responsibilities of system administration, security, and cost management remain critical and time-consuming. The initial promise of cloud computing was to abstract away much of the operational burden, allowing businesses to focus on core competencies. However, the reality for many, including this veteran user, is that the sheer breadth and depth of AWS services, coupled with the ever-evolving nature of the platform, necessitate continuous learning and dedicated effort. "Never not my job" succinctly captures the sentiment that managing cloud resources is an enduring, non-delegable task, requiring constant vigilance and expertise.\n\nThe implications of this viewpoint extend beyond individual practitioners to the broader tech industry and the businesses that rely on cloud services. It suggests that the perceived ease of cloud adoption might mask a significant ongoing operational cost in terms of skilled personnel and time investment. For organizations, this underscores the importance of not only choosing the right cloud services but also investing in the expertise to manage them effectively. The article serves as a valuable reminder that while cloud platforms offer immense power, harnessing that power efficiently and securely is an ongoing challenge that requires sustained commitment and specialized knowledge, challenging the notion of a purely "set it and forget it" cloud experience.\n\nHow does this long-term perspective on AWS management influence your own organization's cloud strategy?