What is the lock-in/impact on flexibility?
There are two forms of lock-in to consider. The lock-in to the optimization tool and the lock-in created by the commitments used to make savings. Ensure the distinction is clear and that you understand your options should things not work out as expected.
- How does the tool use commitments to make savings?
Different commitment types are better suited to certain use cases and come with their own options to manage the risk of lock-in (understanding AWS commitments). Are all these being used and how are decisions made on which to use?
- What level of involvement do you want with the tool?
If you’re searching for a tool, maybe your preference is to let the tool manage everything on your behalf. If that is the case then make sure there is a way to audit its actions. At the very least you’ll want to know about actions that will create a lasting impact on your cloud spend should you stop using the tool.
If you want the freedom to take a more active role to what extent is that enabled? Can you provide insights into future plans so that commitment decisions aren’t made purely on historical trends (AI and commitment management)? Can you exert any control over the nature of commitments being made for you so that the use of the tool doesn’t have to be an “all or nothing” decision? The low level of automation observed here points to the challenges of doing this and suggests a rightfully cautious approach to end-to-end Automation (State of FinOps by FinOps Foundation).
- Buy-back and underutilization payments
AWS applies the benefits from commitments on a continuous, hourly basis through the term of that commitment. If there is no appropriate cloud usage to which the commitment can be applied in any hour, it becomes less effective as a way of providing overall savings. This is measured as “commitment utilization”. Utilization can decrease to the point where a commitment’s net effect is to waste, rather than save, money.
How will the solution maximize the value of commitments whilst avoiding underutilization and to what extent will you be locked into paying for it or wastage? This may be expressed in your contract termination rights so be sure to understand who actually “owns” any commitments. If there are buy-back guarantees or underutilization payments make sure you understand what is actually covered (all commitments, or quite often, just mistakes made by the tool), whether there is any cap and how your cash flow will be affected while any issues are resolved. The devil is always in the detail and this often makes reality very different to the sales and marketing messaging so be sure to explore this fully.
Beyond the standard initial term and notice period considerations there are a few specific factors to think about. Can you terminate for performance-related reasons or convenience and how long would that take to complete?
If you’re terminating for performance-related reasons you’re likely unhappy with the commitment management approach that has been adopted. How will you assess what your commitment position is and how will you take over its management? How will you independently assess performance on an ongoing basis (more below)?
Be prepared to ask these questions upfront and push on the commitment strategy used (understanding AWS commitments). You may find the challenge of replacing an underperforming tool is so great that it, rather than the contract, provides the lock-in you’re aiming to avoid.