FTR vs Well-Architected Review: What's the Difference, and Which Do You Need?

If you're an AWS partner working toward a specialisation, ISV validation, or a spot on AWS Marketplace, you've probably run into two terms that get used almost interchangeably: the Foundational Technical Review (FTR) and the AWS Well-Architected Framework Review (WAFR). They're related, but they're not the same thing, and knowing which one you actually need (or whether you need both) can save weeks of back-and-forth.

What Is an AWS Well-Architected Review?

A Well-Architected Review assesses a specific workload against AWS's six pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimisation, and Sustainability. It's a broad architectural health check, typically used by AWS partners and their customers to identify risks, cost inefficiencies, and technical debt in an existing environment, independent of any partner program requirement.

Anyone running workloads on AWS can (and generally should) do a Well-Architected Review. It's not tied to a specific partner tier or ISV path, it's simply a best-practice audit.

What Is an AWS Foundational Technical Review (FTR)?

An FTR is a specific, program-linked review required for AWS ISV Partners seeking Validated status, co-sell eligibility, or a listing on AWS Marketplace. It uses the Well-Architected Framework as its underlying standard but applies a more targeted self-assessment checklist, focused on whether your software solution (not just your infrastructure) meets AWS's baseline bar for security, reliability, and operational excellence.

In short: the FTR is AWS validating your product for a specific commercial outcome. The Well-Architected Review is a general architectural assessment that can support that validation, but doesn't replace it.

The Key Differences

	Well-Architected Review (WAFR)	Foundational Technical Review (FTR)
Purpose	General architecture health check	AWS Partner Program validation
Required for	No formal requirement, best practice	ISV Validated status, Marketplace co-sell
Scope	Workload/infrastructure	Software solution + infrastructure
Outcome	Recommendations report	Pass/fail toward AWS validation

Which One Do You Need?

• Building a SaaS product and want to list on AWS Marketplace or reach Validated status? You need the FTR. A recent Well-Architected Review can support and accelerate it, but won't substitute for it.

• Running customer workloads and want to identify risk, cost, or reliability gaps? A Well-Architected Review is the right tool, no partner program requirement attached.

• Already AWS Well-Architected Partner accredited? You may qualify for AWS's "Alternative Assessment" pathway, which lets your existing Well-Architected credentials streamline the FTR process rather than starting from scratch.

Doing Both Without Doubling the Work

Because the FTR builds on Well-Architected principles, the two reviews overlap heavily in what they assess, security posture, reliability, operational monitoring, and so on. Running them separately, manually, often means redoing the same evidence-gathering twice.

This is exactly where automation changes the equation. 6pillars' AUTOMATE+ platform generates both your Well-Architected Framework Review report and your FTR Self-Assessment Checklist from the same underlying scan, so partners aren't manually duplicating evidence collection across two processes.

Ready to see where your workload stands? Run an automated Well-Architected Review or start your accelerated FTR with 6pillars.ai.