# change-management Published articles for change-management. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Klarna Built Cloud Inventory for AWS Configuration Management DevFeed: [How Klarna Built Cloud Inventory for AWS Configuration Management]() Original publisher: [Read original article]() Author: Maxim Savin Published: 2025-06-06T06:38:06Z Content type: article Language: en Sources: [Klarna Engineering]() Topics: [configuration-management](), [cloud-infrastructure](), [Amazon Web Services](), [configuration](), [Cloud](), [Security](), [digital]() Tags: [automated](), [aws](), [change-management](), [cloud](), [cloud-infrastructure](), [cloud-inventory-software](), [configuration-management](), [engineering-management](), [lead-time](), [load-balancer](), [logs](), [rds](), [security](), [snapshots](), [technical-change]() ### AI overview Klarna describes Cloud Inventory, an ecosystem of services for collecting, normalizing, mapping, and serving information about ICT assets across its cloud infrastructure. The article explains how it supports configuration management through automated controls and reports faster control rollout and large-scale infrastructure optimization work. ### Source excerpt A long time ago, as a punishment for his crimes, Hades, the king of the underworld, made Sisyphus roll a huge enchanted boulder endlessly up a steep hill. Since then, many tech companies have learned to do that at scale by the hardships of cloud configuration management. Consider an Engineer who wants to ensure that the data that moves through their system is encrypted along the way. This is a noble goal, and to achieve it they must identify every classic load balancer in their AWS environment to replace it with an application load balancer that enforces encryption in transit. Now imagine doing that at the scale of a company like Klarna, where teams collectively own more than a thousand AWS accounts? Add to this a multitude of other configuration challenges -- databases that have not been deployed in a multi-availability zone set-up, missing Cloudwatch logs, expired digital certificates, systems running on unsupported framework versions -- the list is endless. Identifying and rectifying violating cloud assets often feels like an endless game of whack-a-mole played blindfolded. This is the steep price tech companies pay to operate their systems securely and confidently, day by day. Klarna Engineering Platform (KEP) has been on a mission to facilitate configuration management for Klarna Engineers. After a few iterations we have built an ecosystem of Klarna services designed to collect, normalize, map, and serve data on ICT assets within Klarna's cloud infrastructure. We call this system Cloud Inventory. Over the last few months Klarna has: Rolled out over 100 automated controls enhancing every aspect of our configuration management (security, governance, and operational excellence), each control aimed to help system owners to identify and fix violations quickly. Reduced the lead time of rolling out a control from several weeks to a matter of minutes And as a result, successfully completed several large-scale cloud infrastructure optimization projects, such as a company- ## Using Lean Change Management Experiments to Guide Organizational Change DevFeed: [Using Lean Change Management Experiments to Guide Organizational Change]() Original publisher: [Read original article]() Author: Mari Kumlien (mari@upday.com) Published: 2017-01-12T04:00:00Z Content type: opinion Language: en Sources: [Upday]() Topics: [experiments](), [Agile]() Tags: [agile](), [change-management](), [experiments](), [insights](), [management]() ### AI overview The article describes how upday applies Lean Change Management to organizational improvement. It advocates collecting insights from people in the organization, designing small experiments with affected participants, and evaluating hypotheses against predefined metrics before taking the next step. ### Source excerpt A new year comes with the feeling that now is the time to change things. How many of us started the year with a promise to change and a few days later, it was already broken? Once a year, big-bang changes don't work - it never did and never will. Instead, change things when and where you feel the need to. At upday, we strive to continuously improve; how we work and what we deliver. This requires constant change. How do we foster an organization where the changes are based on what is truly going on in the organization and its surroundings? Where change is not driven by a few, but by anyone who sees the need for change? Where change is not planned upfront and executed top-down but as small steps involving people who are affected? Where we all take part in shaping the future of the organization we want to work in and where we can deliver excellence? Where Did We Start? I (Agile Coach at upday) joined a Lean Change Agent workshop together with Richard, one of our Data Scientists, and our CTO Andi. It was a two day workshop held by Mike Weber and based on the book by Jason Little: Lean Change Management. It was an active workshop including lots of participation and interactions, with great tools and ideas about how to work with change in an organization. We were introduced to a way of approaching change by collecting insights and from these, create small experiments that you evaluate and learn from before you take the next step. The idea is that instead of planning the change upfront, to create small experiments based on your current understanding and insights gathered, and review these after a fixed time period. The word experiment is important here since it emphasizes that until we have tried something out; verified our assumptions (hypotheses) based on predefined metrics, we don't know whether it's the right thing to do and if our change will be successful. Another key ingredient is to involve people affected by the change in designing the change. This is called the L ## Puppet Change Management for DevOps DevFeed: [Puppet Change Management for DevOps]() Original publisher: [Read original article]() Author: Bryce Johnson Published: 2011-09-20T23:18:04Z Content type: article Language: en Sources: [Atlassian Developer Blog]() Topics: [DevOps](), [Puppet]() Tags: [bamboo](), [builds](), [change-management](), [devops](), [greenhopper](), [jira](), [mentor](), [production](), [puppet](), [review]() ### AI overview The article discusses how DevOps engineers can use Puppet for change management, including carefully applying changes to production, reviewing changes with stakeholders, mentoring colleagues, and remembering what was changed. ### Source excerpt DevOps engineers need a way to carefully apply their changes to production. They also need to review those changes with other stakeholders, mentor fellow colleagues, and of course remember what they did...