Suger is now Fours. Read the announcement

The AWS ISV Partner Path Is Now the Software Path

AWS renamed the ISV Path to the Software Path, and the rename is the least interesting part. What matters is which stage you are at, and what each one actually unlocks.

Sabrina Xie
Aug 9, 2026 ·

The AWS ISV Partner Path is the AWS Partner Network track for companies whose product is software — and it is now the Software Path, one of the Partner Paths AWS introduced to replace partner types, “evolving to an offering type model.” The path runs, in AWS’s words, “from enrolled to differentiated status,” with Validated in between, and the AWS Foundational Technical Review is the gate to Validated.


Most ISVs meet the AWS Partner Network as a set of acronyms someone in alliances says confidently: FTR, ACE, ISV Accelerate, Validated. What none of them explains is the shape underneath — that these are stages in a sequence, that each one gates specific benefits, and that the marketplace listing you actually want sits on top of them.

Here is the sequence, with the current names, and what each stage is for.

Updated November 6, 2026: the FTR now requires a solution linked to an AWS Marketplace software product, so the listing is no longer independent of the partner work, and the sequence below says to start it early. AWS’s current pages describe the path as running “from enrolled to differentiated status” and give an FTR approval two years without stating a renewal rule for Validated, so this post now calls the first stage Enrolled, and quotations we could no longer find on AWS’s pages are replaced with its current wording.


What is the AWS ISV Partner Path?

The AWS ISV Partner Path is the AWS Partner Network engagement track for organizations that build software. AWS opened it to any partner “with a software solution that runs on or is integrated with” AWS, and now calls it the Software Path.

It is one of five paths a partner can enrol in:

PathWhat it covers
Software Path (formerly ISV Path)Organizations that develop software that runs on or is integrated with AWS
Hardware PathOrganizations that develop hardware devices that work with AWS
Services PathOrganizations that deliver consulting, professional, managed, and value-added resale services
Training PathOrganizations that sell, deliver, or incorporate AWS training
Distribution PathOrganizations that recruit, onboard, and support their partners to resell and develop AWS solutions

The rename matters more than it looks. Paths describe what you offer, not what kind of company you are — which is why a company can sit on more than one. An ISV that also delivers implementation services belongs on the Software Path and the Services Path, and gets a different set of benefits from each.

One practical note before you enrol in anything: AWS states that “if you need to remove a Partner Path from your account, you must contact APN Support for assistance.” Enrolment is easier than un-enrolment. Choose deliberately.


The three stages, and what each one is for

AWS describes the journey as running “from enrolled to differentiated status,” tracked in the Partner Scorecard — “your tool to track progression of your AWS Partner path and tier requirements.”

Enrolled. You have an APN account and have selected a path. This is administrative. It gets you into Partner Central and the training and enablement material, and nothing more. Plenty of ISVs sit here for a year without realising there is anywhere else to be.

Validated. The stage that changes what you can do. Reaching it means AWS has technically reviewed your product, and it is the entry requirement for the programs that actually carry commercial value. The AWS ISV Workload Migration Program, for example, states that to be considered your organization must have “a fully managed SaaS offering on AWS,” have “completed an AWS Foundational Technical Review for the nominated workload,” and a “qualified migration use case” — the same review that moves you to Validated.

An FTR approval also expires: AWS says it “is valid for two years from approval,” and Partner Central’s Validation tab shows the expiration date.

Differentiated. The stage where AWS is willing to point customers at you: competencies, service-ready designations, solution-level badging, and deeper field engagement. Some programs accept either of the top two: the AWS ISV Accelerate Program, AWS’s co-sell program for software partners, requires “Validated or Differentiated status in AWS Partner Central.”

The specific requirements for each stage are published in Partner Central and change; the Partner Scorecard is the authoritative view of where you stand against them. Read it there rather than from a blog, including this one.


The Foundational Technical Review is the whole gate

If there is one thing to take away, it is this: the FTR is the step between “we have an AWS account” and “AWS will engage commercially.”

AWS says the FTR “provides specific guidelines to adopt a subset of AWS best practices to reduce risks around security, reliability, and operational excellence, as defined by the AWS Well-Architected Framework.”

The submission itself is now automated. AWS describes a “streamlined FTR process” that “accepts industry-standard compliance certifications aligned to the same security, reliability, and operational standards that AWS validates, and returns approval or actionable feedback within minutes.” You upload one of two documents against a solution in Partner Central — a SOC 2 Type II report or an AWS Well-Architected Framework Review (WAFR) report — and “your submission is reviewed automatically.”

That changes where the work sits. Three practical consequences:

The evidence is the long pole, not the review. The review returns in minutes; producing an unqualified SOC 2 Type II covering your AWS-hosted workload, or a WAFR with zero high-risk issues in the Security, Operational Excellence, and Reliability pillars, is the part that takes a quarter. Both reports must be less than a year old.

The prerequisites gate you before the upload does. AWS runs a prerequisite checklist in sequence, and later checks stay blocked until earlier ones pass: the solution must be linked to exactly one AWS Marketplace software product, deployed on AWS with an approved architecture diagram, and Partner Revenue Measurement enabled — and PRM data “can take up to 7 days” to appear. Start that a week before you plan to submit.

It unlocks solution-level badging — the AWS-issued designation that appears against your product rather than against your company name, plus Partner Solutions Finder listing and APN program eligibility.

It expires. AWS states the approval “is valid for two years from approval,” and Partner Central’s Validation tab shows the FTR expiration date. The badging, program eligibility and funding benefits AWS says an approval unlocks rest on it, so put the expiration date in the same calendar as your marketplace agreement renewals.


How the path relates to selling on AWS Marketplace

This is the part most often muddled, so it is worth stating plainly: the Software Path and AWS Marketplace are related but separate.

You register as an AWS Marketplace seller to list and transact. You progress through the Software Path to unlock AWS Partner Network benefits. Seller registration does not require partner standing, but the FTR does require a listing: the solution you submit “must have an AWS Marketplace product linked.”

Where they genuinely connect:

Co-sell runs on the partner relationship, not the listing. Submitting opportunities through APN Customer Engagements — and getting AWS sellers engaged on them — depends on your partner standing, not on having a listing. The AWS ACE guide for ISV sellers covers how that pipeline actually works.

Partner funding is gated on program status. POC funding, migration programs, and market development funds each have their own eligibility, and several depend on stage. AWS partner funding programs covers which is which.

The marketplace listing is where the money moves. Progression gets you AWS attention; the listing turns that attention into a transaction. The AWS Marketplace seller’s guide covers the listing side.

A useful way to hold it: the Software Path is your relationship with AWS. AWS Marketplace is your relationship with the buyer, running on AWS’s billing rails.


A sequence worth following

For an ISV starting from nothing, this order wastes the least time:

  1. Enrol in the Software Path. Free, fast, and it gates everything else.
  2. Register as an AWS Marketplace seller in parallel. Start the listing early: the FTR in step 3 needs an active AWS Marketplace software product linked to the solution.
  3. Start the FTR evidence early against one solution. The submission returns a result in minutes; the SOC 2 Type II or WAFR report behind it does not. Clear the prerequisites — one linked Marketplace product, an approved AWS architecture, PRM enabled — a week ahead.
  4. Reach Validated, then check which programs that opens for your specific motion. Do not chase all of them.
  5. Get co-sell hygiene right before pursuing Differentiated. AWS field engagement is earned through pipeline discipline, and nothing substitutes for opportunities that are submitted accurately and kept current.
  6. Diarise the FTR renewal. Approval lasts two years; put the expiration date in the calendar.

Frequently asked questions

What is the AWS ISV Partner Path? It is the AWS Partner Network track for companies whose offering is software. AWS has renamed it the Software Path, describing it as being for organizations that develop software that runs on or is integrated with AWS.

Why did AWS rename the ISV Path to the Software Path? Because AWS replaced its technology and consulting partner types with Partner Paths, “evolving to an offering type model” — paths describe what a partner offers, which is why one company can enrol in several.

What are the AWS partner stages? Enrolled, Validated, and Differentiated. AWS describes the journey as running from enrolled to differentiated status, tracked in the Partner Scorecard in AWS Partner Central.

What does the AWS Foundational Technical Review unlock? It is the gate to Validated stage and to solution-level badging. AWS describes it as helping partners identify and remediate risks based on best practices for security, reliability, and operational excellence.

How often does the FTR need renewing? AWS states an FTR approval is valid for two years from approval, and Partner Central shows the expiration date on the solution’s Validation tab.

Do I need to be on the Software Path to sell on AWS Marketplace? They are separate registrations. You register as a marketplace seller to list and transact, and progress through the Software Path to unlock partner benefits such as co-sell engagement and funding.


Takeaways

  • The ISV Path is now the Software Path. Paths describe what you offer, so a company can enrol in more than one.
  • The stages run Enrolled → Validated → Differentiated, tracked in the Partner Scorecard.
  • The Foundational Technical Review is the gate to Validated and to solution-level badging. The submission is automated and returns in minutes; the SOC 2 Type II or WAFR report behind it is the real work.
  • An FTR approval expires. AWS says it is valid for two years from approval, so diarise the expiration date.
  • Partner path progression and AWS Marketplace seller registration are separate, but the FTR needs a linked AWS Marketplace software product. Start the listing early.
  • Requirements change. The Partner Scorecard in Partner Central is the authoritative view, not any article about it.

Partner standing is what gets AWS engaged; a working co-sell motion is what keeps them engaged. See how co-sell automation in Fours syncs opportunities between your CRM and AWS Partner Central — so pipeline hygiene stops depending on somebody re-typing deals into a portal.

Sources

Primary sources for the platform rules cited above. Last verified November 6, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure.

Browse every post on the Fours Blog

Stay Updated

New posts, product updates and marketplace strategy are shared on LinkedIn as they publish.

Follow Fours on LinkedIn