> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/pump-save/aws-reserved-instance-and-savings-plan-policy-changes-2025.md). # AWS Reserved Instance and Savings Plan Policy Changes (2025) Effective June 1, 2025, AWS updated its Reserved Instance and Savings Plan policies. The changes affect how Managed Service Providers, Solution Providers, and solutions providers share commitments across multiple customer accounts. Specifically, sharing RI and SP commitments across multiple customer accounts is no longer permitted. ### Impact on Pump customers Pump customers are not affected by this change. Pump does not pool or share commitments across customers. Every commitment Pump purchases lands in your own cloud account and is keyed to your account ID. ### Why Pump customers are already compliant | AWS policy requirement | Pump's existing practice | | --------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | RIs and SPs must be used for a single end customer's AWS usage | Every commitment Pump purchases is scoped to your account. No sharing across customers. | | Sharing commitment pools across customer accounts is prohibited | Pump does not maintain shared commitment pools. Each customer's commitments are independent. | ### What this means for you No action is required. Your existing commitments and Pump's optimization approach are fully aligned with the updated AWS policies. You can continue using Pump with no changes to your setup. ### Questions If you have questions about these policy changes and how they relate to your account, contact your Pump account manager or reach out to . --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.pump.co/pump-save/aws-reserved-instance-and-savings-plan-policy-changes-2025.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.