> 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/how-we-work-with-cloud-providers/cloud-provider-am-faq.md). # Cloud Provider AM FAQ These are questions we commonly hear from AWS, GCP, and Azure account managers when their customers start using Pump. If your question is not covered here, contact our partnerships team at . ### Is Pump an authorized partner? Yes. Pump is an authorized solutions provider and channel partner across all three major cloud providers. | Provider | Program | Verification | | -------- | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | AWS | Solution Provider Program (Advanced Tier), Cloud Operations Services Competency, AI Services Competency | [AWS Partner Listing](https://partners.amazonaws.com/partners/0018W00001wuP0XQAU/Pump) | | GCP | Google Cloud Partner | [GCP Partner Listing](https://cloud.google.com/find-a-partner/partner/pump) | | Azure | Authorized Microsoft Azure Partner | Available on request | Pump distributes through Ingram Micro for all three providers. ### Does customer spend through Pump still count toward my quota? Yes. Customer spend that routes through Pump's solutions provider channel counts toward your quota and attribution. Pump does not take commission from cloud provider AMs. The solutions provider relationship is additive to your existing account coverage. ### Does Pump reduce my customer's cloud spend? Pump optimizes how customers purchase commitments (Reserved Instances, Savings Plans, Committed Use Discounts). This improves the customer's cost efficiency per unit of compute. In practice, customers reallocate the savings into new workloads, expanded usage, or other cloud investments, which increases total spend over time. Pump does not recommend that customers reduce workloads, migrate away from your platform, or switch providers. Pump's right-sizing recommendations help customers match instance types to actual usage, which improves resource efficiency and frees up budget for additional cloud adoption. ### Does Pump affect my customer's support plan? No. The customer's existing cloud provider support plan (AWS Support, Google Cloud Support, Microsoft Unified Support) remains active and unchanged. Pump does not modify, replace, or interfere with support entitlements. ### Can my customer still work with me directly? Yes. The AM relationship is completely unaffected by Pump. Customers continue to work with their assigned AM for account strategy, service adoption, technical guidance, and all other account management activities. Pump handles billing optimization and commitment management only. ### How does Pump manage commitments on my customer's behalf? Pump's commitment management engine analyzes the customer's usage patterns, existing commitment portfolio, and expiration schedules. It calculates optimal purchases for Reserved Instances (AWS), Savings Plans (AWS/Azure), Committed Use Discounts (GCP), and Azure Reservations. All commitments are purchased within the customer's own account. Pump does not pool commitments across customers. Each commitment is tied to a single customer. Customers can choose Autopilot mode (Pump executes recommendations automatically, customer can block individual purchases) or Manual mode (customer reviews and approves every purchase before execution). ### What happens if my customer stops using Pump? No contracts, no lock-in. If a customer decides to leave Pump: 1. Existing commitments (RIs, SPs, CUDs) remain in the customer's account and run off on their natural expiration schedule. Nothing is canceled early. 2. Billing reverts to direct (customer pays the cloud provider directly). 3. The customer retains all their cloud resources, configurations, and data. The transition is straightforward and does not disrupt the customer's workloads or your AM relationship. ### Does Pump work with customers who have existing commitments? Yes. Pump's optimization engine accounts for existing RIs, SPs, and CUDs. Pump does not replace or cancel existing commitments. It optimizes new purchases around the customer's current portfolio, filling coverage gaps and improving utilization rates as existing commitments expire. ### Does Pump work with customers on an EDP or PPA? Yes. Pump is compatible with Enterprise Discount Programs (AWS), Private Pricing Agreements (GCP), and Enterprise Agreements (Azure). Pump's commitment management operates alongside these programs. ### Is Pump SOC 2 certified? Yes. Pump is SOC 2 Type II certified. Audit reports are available on request. Contact . ### How do I get more information? For any questions not covered here, including questions about specific customer accounts, partner verification, or Pump's security posture, contact our partnerships team at . We are happy to set up a call or provide documentation as needed. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.pump.co/how-we-work-with-cloud-providers/cloud-provider-am-faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.