DoiT has added support for AWS Managed Service Provider Program Validation Checklist 8.0 to its PartnerOps Channel Management module, positioning the update as a way for cloud partners to organize the AI-specific evidence required for the next validation cycle.
The new checklist, known as VCL 8.0, is scheduled to replace the preceding version on Jan. 1, 2027, according to DoiT. It applies to partners seeking or renewing the AWS Managed Service Provider program designation. AWS describes the program as a validation for partners that deliver services across the cloud lifecycle, from planning and migration to ongoing operations and optimization.
DoiT says the revised checklist asks partners to demonstrate observability for generative-AI and agentic workloads, including token consumption and inference cost per agent. It also calls for AI workload cost optimization and measurable AI-driven business outcomes for each customer. Those requirements create a more detailed evidence burden for providers that manage cloud services on behalf of many customers.
Channel Management is designed to put an owner and set of tasks against each control, route approvals and review evidence before it reaches an auditor, DoiT said. The company also says the module can scan managed AWS environments automatically, draft supporting documents and track work between audit cycles. For new applicants, the intended benefit is a structured view of the audit sequence; for renewing partners, it is a way to identify gaps against the new controls.
The announcement matters because MSP validation is not solely a documentation exercise. A provider must be able to show how it operates its own customer practice. DoiT is tying the compliance workflow to other products in its portfolio: Revenue Management for billing and per-customer reporting, Attribute for runtime AI cost attribution, Cloud Intelligence for cost and optimization data, and PerfectScale and SELECT for Kubernetes and data-cloud environments.
The company says Attribute links token, model and GPU costs to customers, features and agents using live runtime data. That information could help an MSP prepare customer-level AI usage evidence where the underlying application and cloud billing records do not on their own provide enough context. The release does not detail the data sources, deployment requirements or audit acceptance criteria for those integrations, so partners will need to assess those matters in their own environments.
The practical value of the update is likely to be greatest for partners managing a broad portfolio of AWS customers while preparing for a 2027 audit or renewal. Automating task assignment, evidence reviews and environment scanning could reduce the manual coordination involved in compliance preparation. It does not eliminate the need to demonstrate that the provider’s operations meet the applicable technical and business controls.
DoiT says PartnerOps supports both checklist versions during the transition. Managed service providers will still need to confirm their audit timing, applicable requirements and the evidence expected for their particular validation with AWS. For cloud-operations leaders, the change is an early signal that cost visibility and governance for AI workloads are becoming part of partner program operations, not just an internal FinOps concern.