AWS Partner Central separates case-study publishing from specialization review

AWS Partner Central is separating the review needed to publish go-to-market case studies from the deeper review used for specialization applications. In an announcement published October 20, 2026, AWS introduced Program Navigator and a redesigned Case Study Generator, saying both are available to all AWS Partners in Partner Central.

One place for specialization applications

Program Navigator lets partners browse AWS Specialization designations, view their requirements and benefits, submit applications through a guided workflow, and track those applications in one place.

AWS says the streamlined process offers faster reviews and more detailed, requirement-level feedback. The announcement gives no numerical turnaround target, so the speed claim should not be treated as a scheduling guarantee. Applications for non-specialization programs remain in the existing experience. Source: AWS.

Case studies get two review paths

The redesigned Case Study Generator offers three starting points:

• Create a case study with AI assistance.
• Import an existing customer success story from a URL.
• Auto-populate a case study from an opportunity.

For go-to-market case studies, AWS describes a lightweight policy-validation path that allows publication to AWS domains without a specialization review. The deeper specialization-level review applies only to case studies associated with Program Navigator applications. Source: AWS.

The practical distinction is review status: publication of a go-to-market customer story does not, by itself, mean that story has passed specialization-level review. Teams planning to use a case study for both purposes should account for the separate review path when preparing a specialization application.

Availability and access

AWS says both tools are available to all AWS Partners in AWS Partner Central. To access them, open Go to Market in the left navigation panel, then select Program Navigator or Case Studies. The application-workflow change concerns specializations, not every partner program. Source: AWS.