Are you unsure whether your AWS-hosted software needs a Foundational Technical Review (FTR), a Well-Architected Framework Review (WAFR), or both to meet AWS requirements?
Although both assessments address cloud security, reliability, and operational best practices, they serve different purposes and follow different validation processes.
On June 16, 2026, AWS introduced streamlined FTR validation, allowing eligible AWS partners to receive approval or actionable feedback within minutes (Source).
More recently, AWS updated its Well-Architected Framework on November 16, 2026, organizing guidance into 45 Cloud Foundations best practices and 216 Cloud Workloads best practices across its architectural framework (Source).
Understanding AWS FTR vs WAFR helps SaaS companies, ISVs, and DevOps teams determine the right assessment, prepare the required documentation, address high-risk findings, and streamline AWS partner validation.
AWS FTR vs WAFR: What Are the Key Differences?
AWS Foundational Technical Review (FTR) and AWS Well-Architected Framework Review (WAFR) both help organizations align their cloud environments with AWS architectural best practices. However, FTR validates a specific eligible AWS Partner software solution linked to an AWS Marketplace product against foundational requirements, while WAFR assesses AWS workload architecture to identify risks and opportunities for improvement.
What is AWS Foundational Technical Review (FTR)?
The AWS Foundational Technical Review (FTR) is a technical validation process for software solutions developed by AWS Partners. It verifies alignment with foundational security, reliability, and operational excellence requirements derived from the AWS Well-Architected Framework.
Under AWS's streamlined validation process, partners can submit a qualifying SOC 2 Type II audit report or AWS Well-Architected Framework Review (WAFR) report through AWS Partner Central.
Completing FTR helps eligible software partners earn the AWS Qualified Software badge and access applicable AWS Partner Network (APN) benefits, including eligibility for programs such as AWS ISV Accelerate, subject to additional program requirements.
According to AWS's official FTR documentation, the review is free, supports self-service validation, and remains valid for two years after approval.
What is AWS Well-Architected Framework Review (WAFR)?
The AWS Well-Architected Framework Review (WAFR) is a structured assessment that evaluates how an AWS workload aligns with cloud architecture best practices. It helps organizations identify architectural risks, improve workload reliability, strengthen security, and optimize cloud operations.
A WAFR evaluates workloads against six pillars of the AWS Well-Architected Framework:
Operational Excellence: Running, monitoring, and continuously improving workloads.
Security: Protecting cloud resources, applications, systems, and data.
Reliability: Maintaining workload availability and recovering from failures.
Performance Efficiency: Using computing resources efficiently as requirements change.
Cost Optimization: Managing cloud costs while delivering business value.
Sustainability: Reducing the environmental impact of cloud workloads.
On November 16, 2026, AWS updated its Well-Architected Framework, organizing best practices into Well-Architected Cloud Foundations for account- and organization-level guidance and Well-Architected Cloud Workloads for workload-specific architecture decisions.
Unlike FTR, WAFR does not grant AWS partner software validation. Instead, it documents architectural findings, including high-risk and medium-risk issues, and provides recommendations for continuous improvement.
AWS FTR vs WAFR: Comparison Table
Comparison Factor | AWS FTR | AWS WAFR |
|---|
Primary objective | Validate an eligible AWS Partner software solution | Assess and improve AWS workload architecture |
Target audience | AWS software partners, ISVs, and SaaS providers | Cloud architects, DevOps teams, enterprises, and AWS partners |
Assessment scope | Foundational security, reliability, and operational excellence requirements | Six Well-Architected pillars |
Validation or assessment evidence | Qualifying SOC 2 Type II or WAFR report | Workload architecture information and review responses |
Primary AWS tool | AWS Partner Central | AWS Well-Architected Tool |
Outcome | FTR approval, Qualified Software badge eligibility, and applicable AWS Partner Network benefits, subject to program-specific requirements; or actionable validation feedback | Architectural risk findings, including high-risk and medium-risk issues, and improvement recommendations |
Validity | Two years after approval | Point-in-time assessment; WAFR reports used for FTR must be less than one year old |
Business relevance | Qualified Software badge and applicable AWS partner benefits | Architecture improvements, risk reduction, and operational efficiency |
The key difference: AWS FTR validates a specific eligible AWS Partner software solution against foundational requirements, while WAFR provides a broader architectural assessment of AWS workloads. A qualifying WAFR report can support FTR validation, but completing a WAFR does not automatically result in FTR approval.
AWS FTR or WAFR: Which Review Does Your Software Need?
Whether your organization needs an AWS Foundational Technical Review (FTR), a Well-Architected Framework Review (WAFR), or both depends on your business objectives, AWS partner status, and validation requirements.
When Do AWS Software Partners Need FTR?
If you're an Independent Software Vendor (ISV) or SaaS provider seeking AWS software validation, FTR is the relevant process. An approved FTR helps eligible AWS Partners earn the Qualified Software badge and access applicable benefits, including eligibility for AWS ISV Accelerate.
However, FTR is not universally required to list software on AWS Marketplace. The need for FTR depends on your partner validation and program objectives.
When Should You Conduct an AWS WAFR?
If your primary goal is to evaluate an existing AWS workload, identify architectural risks, or improve security, reliability, performance, and cost efficiency, a WAFR is the appropriate assessment.
Organizations can conduct WAFR independently of FTR, even when they are not pursuing AWS partner software validation. The review helps teams prioritize improvements across the six Well-Architected pillars.
Can a WAFR Report Be Used for FTR Validation?
If your AWS software solution requires FTR validation, you can submit a qualifying WAFR report instead of a SOC 2 Type II report.
For this pathway, AWS requires zero high-risk issues (HRIs) in the Security, Reliability, and Operational Excellence pillars, along with other report eligibility conditions. Completing WAFR alone does not guarantee FTR approval.
In short: Choose FTR for eligible AWS partner software validation, WAFR for architectural assessment, or use an eligible WAFR report to support FTR validation when both objectives apply.
AWS FTR vs WAFR: Eligibility and Review Requirements
AWS FTR and WAFR have different requirements because they serve distinct purposes. AWS FTR requires eligible software partners to meet specific prerequisites and submit qualifying validation evidence, while WAFR involves assessing a defined AWS workload against architectural best practices.
AWS FTR Prerequisites Checklist in Partner Central
Before requesting an AWS Foundational Technical Review, software partners must satisfy six prerequisites in AWS Partner Central.
Requirement | What AWS Requires |
AWS Marketplace product | The solution must be linked to an AWS Marketplace product through AWS Partner Central. |
Single product association | Each solution submitted for FTR validation must be linked to only one AWS Marketplace product. |
Marketplace-only products | The solution must not contain any products outside AWS Marketplace. |
Eligible software type | The linked product must be SaaS, Amazon Machine Image (AMI), Container, or Machine Learning software. |
AWS-hosted architecture | The Marketplace product must be deployed on AWS with an approved AWS-hosted architecture, supported by an architecture diagram uploaded through the AWS Marketplace Management Portal. |
Partner Revenue Measurement (PRM) | PRM must be enabled, and the product must appear as onboarded in the attributed revenue dashboard. |
AWS Partner Central evaluates these prerequisites sequentially. Incomplete requirements prevent partners from submitting an FTR validation request until the issues are resolved.
After enabling Partner Revenue Measurement, AWS states that it may take up to seven days for measurement data to appear. Partners can refresh the Validation tab after addressing an incomplete prerequisite.
Source: AWS Partner Central - FTR Prerequisites
AWS WAFR Requirements and Assessment Scope
Unlike FTR, conducting an AWS Well-Architected Framework Review does not require an AWS Marketplace listing or partner software validation.
AWS recommends preparing the following information before conducting a WAFR:
Workload scope: Identify the application, AWS resources, dependencies, and architectural boundaries being evaluated.
Architecture documentation: Gather relevant architecture diagrams, infrastructure configurations, security information, and operational documentation.
Workload stakeholders: Involve relevant cloud architects, DevOps engineers, security personnel, and workload owners.
Architectural assessment: Evaluate the workload against applicable best practices across the six AWS Well-Architected pillars.
Risk documentation: Record review responses, identify high-risk issues (HRIs) and medium-risk issues (MRIs), and develop an improvement plan.
Get insights in your inbox!!
Weekly tips on building smarter apps. Join 8,200+ founders and builders.
No spam. Unsubscribe anytime. We respect your privacy.
AWS organizes the review into three phases: Prepare, Review, and Improve.
Following its November 16, 2026 update, the AWS Well-Architected Framework also distinguishes Well-Architected Cloud Foundations, covering account- and organization-level architecture, from Well-Architected Cloud Workloads, covering workload-specific decisions.
A standard WAFR helps organizations identify and prioritize architectural improvements. Completing the review does not itself require resolving every high-risk issue. However, additional criteria apply when the resulting report is submitted for AWS FTR validation.
Source: AWS Well-Architected Framework Review.
SOC 2 Type II vs WAFR: Which Report Does AWS Accept for FTR?
AWS accepts two evidence pathways for Foundational Technical Review validation: a qualifying SOC 2 Type II audit report or an AWS Well-Architected Framework Review report.
Validation Requirement | SOC 2 Type II Report | WAFR Report |
|---|
Report age | Report issue date is within one year | Report is less than one year old |
Assessment scope | Must explicitly cover the AWS-hosted partner solution | Must cover the solution's primary AWS-hosted workload |
Security requirements | Must include Security and Availability trust services criteria, with the AWS-hosted components and the specific partner solution explicitly in scope | Must show zero HRIs in Security |
Reliability and operations | Must meet the applicable audit scope and criteria | Must show zero HRIs in Reliability and Operational Excellence |
Additional evidence | Unqualified opinion from an accredited third-party auditor, with AWS infrastructure in scope | Specific solution named in the workload name or description; reviewer's full name and email in the reviewer owner field |
Review method | Independent third-party audit | Review conducted using AWS Well-Architected Tool, either self-service or with eligible assistance |
For the WAFR validation pathway, AWS requires zero high-risk issues in Security, Reliability, and Operational Excellence, not necessarily all six Well-Architected pillars.
Have high-risk issues blocking your FTR?
We fix IAM, logging, encryption, and backup findings with Terraform, CloudFormation, and CDK, so you can resubmit with confidence.
Talk to an AWS ExpertThe report must also satisfy AWS's document freshness, solution identification, reviewer information, and assessment-tool requirements.
AWS Partner Central automatically evaluates the submitted report and returns approval or actionable feedback within minutes. If the report fails validation, the partner can address the identified issues and resubmit the corrected document.
Source: AWS Partner Central - Accepted Validation Documents and Checks
Key takeaway: Organizations with a qualifying SOC 2 Type II report can use it for AWS FTR validation without completing a separate WAFR solely for that submission. Organizations choosing the WAFR pathway must ensure the report meets AWS's freshness, workload identification, reviewer, and zero-HRI requirements.
AWS FTR and WAFR Review Process: Step-by-Step Guide
The AWS FTR and WAFR processes follow different workflows. A Well-Architected Framework Review assesses workload architecture and identifies improvement opportunities, while a Foundational Technical Review validates qualifying evidence submitted through AWS Partner Central.
Understanding both processes helps AWS partners prepare documentation, address technical findings, and avoid unnecessary delays in software validation.
How to Conduct a WAFR Using the AWS Well-Architected Tool
AWS organizes WAFR into three phases: Prepare, Review, and Improve. Organizations can conduct a review using the AWS Well-Architected Tool or with assistance from an AWS employee, a Well-Architected Program Partner (WAPP), or ISV tools.
Define your workload: Open the AWS Well-Architected Tool, select Define workload, and enter the workload name, description, review owner, environment, and applicable AWS Regions. Select the applicable Well-Architected lens and complete the workload review.
Prepare architecture documentation: Gather relevant architecture diagrams, infrastructure configurations, security controls, and operational information. Involve stakeholders responsible for the workload.
Review architectural best practices: Select Start reviewing and answer the questions associated with the selected lens. Document applicable best practices, workload configurations, and relevant observations.
Generate the review report: After documenting the workload, save an initial milestone. Select the appropriate lens and choose Generate report to create a PDF summarizing assessment responses, identified risks, and recommended improvements.
Review findings and prioritize remediation: Open the Improvement plan to examine high-risk issues (HRIs), medium-risk issues (MRIs), and recommended actions. Prioritize improvements based on their technical impact and business importance.
Implement improvements and track progress: Address the selected findings, update the workload assessment, and save additional milestones to measure changes in architectural risk over time.
Teams commonly conduct Well-Architected reviews at major development milestones and revisit findings as workloads evolve.
Source: AWS Well-Architected Tool Tutorial
How to Submit an AWS FTR Request in AWS Partner Central
Under AWS's streamlined validation process introduced in June 2026, eligible AWS software partners can request FTR approval for a specific AWS Marketplace-linked solution by submitting a qualifying SOC 2 Type II or WAFR report through AWS Partner Central.
Once the eligibility prerequisites are complete, follow these steps:
Sign in to AWS Partner Central: Open AWS Partner Central and navigate to Build → Solutions.
Select your software solution: Choose the AWS Marketplace-linked software solution you want to validate.
Verify prerequisite completion: Open the Validation tab and confirm that all prerequisite checks show Complete.
Request FTR validation: Select Request validation and choose either SOC 2 report or WAFR report as the evidence type.
Upload the validation document: Upload the qualifying report as a PDF. AWS accepts PDF files up to 3 MB.
Submit the FTR request: Select Request FTR. AWS automatically evaluates the submitted report against its validation criteria.
Review the validation result: AWS returns approval or actionable feedback within minutes. An Approved status confirms FTR validation and displays the expiration date. It also enables applicable AWS Partner Network benefits, subject to program-specific requirements.
If the submission receives an Action required status, review the feedback in the Validation tab, resolve the identified issues, and select Resubmit to upload an updated report.
AWS allows multiple resubmissions, with automated validation performed after each submission.
Source: AWS Partner Central - Request Foundational Technical Review
Key takeaway: WAFR follows an iterative process of architectural assessment, risk identification, and improvement, while FTR uses qualifying documentation to validate an eligible software solution. Although AWS can return FTR validation results within minutes, preparing an eligible workload and resolving architectural findings may require additional engineering effort.
Common AWS FTR and WAFR Findings and How to Fix Them
AWS architecture assessments frequently examine weaknesses in identity management, access controls, data protection, monitoring, and disaster recovery. Addressing these issues requires targeted configuration changes and verification against applicable AWS Well-Architected best practices.
AWS Security, Reliability, and Operational Risks
Risk Area | Common Finding | Recommended Remediation |
|---|
Identity and access management | Overly permissive AWS IAM policies or unnecessary administrative privileges | Apply least-privilege permissions, remove unused access, and review IAM policies. |
Authentication security | Missing multi-factor authentication (MFA) or excessive reliance on long-term credentials | Strengthen MFA enforcement and use temporary credentials where appropriate. |
Logging and monitoring | Incomplete AWS CloudTrail coverage or insufficient operational alerts | Configure appropriate CloudTrail logging and implement Amazon CloudWatch monitoring and alerts. |
Data protection | Inadequate encryption or overly broad access to Amazon S3, EBS, or RDS resources | Configure encryption, review AWS KMS key policies, and restrict sensitive data access. |
Backup and disaster recovery | Untested recovery procedures, missing backups, or undefined recovery objectives | Automate backups, test restoration procedures, and establish measurable RPOs and RTOs. |
Operational excellence | Inconsistent deployment processes, insufficient observability, or weak incident response procedures | Standardize deployments, strengthen monitoring, and test operational response procedures. |
How to Prioritize and Validate AWS Remediation
Not every architectural finding requires the same urgency. Teams should prioritize remediation based on risk severity, workload criticality, potential business impact, and dependencies between improvements.
For example, excessive IAM privileges or publicly accessible sensitive data may warrant immediate attention, while noncritical monitoring improvements can be scheduled according to operational priorities.
After implementing changes, engineers should verify that the original risks have been addressed through configuration reviews, security checks, and updated workload assessments.
For organizations pursuing FTR validation through a WAFR report, remediation priorities must also account for the applicable high-risk issue acceptance criteria.
These activities become more complex when findings affect multiple AWS services or environments, making consistent implementation and validation processes essential.
Automating AWS FTR and WAFR Remediation with Infrastructure as Code
Infrastructure as Code (IaC) helps engineering teams implement AWS architecture improvements through version-controlled, repeatable configurations rather than relying entirely on manual changes in the AWS Management Console.
Tools such as Terraform, AWS CloudFormation, and AWS CDK allow teams to define infrastructure configurations as code, review proposed changes, and maintain consistency across development, staging, and production environments.
For AWS FTR and WAFR remediation, infrastructure automation provides several practical advantages:
Consistent configuration changes: Apply standardized IAM policies, encryption settings, and logging configurations across relevant AWS resources.
Version control and traceability: Track infrastructure modifications through code repositories, pull requests, and approval workflows.
Automated validation: Use infrastructure scanning, policy checks, and testing to identify potential misconfigurations before deployment.
Reduced configuration drift: Maintain alignment between approved infrastructure definitions and deployed resources through monitoring and reconciliation.
AWS also provides the AWS Well-Architected Agent (preview), which uses AI-assisted analysis to recommend architectural improvements and implementation changes. As a preview offering, its features and availability may change.
Get FTR-Ready Without the Guesswork
Not sure whether your software needs an FTR, a WAFR, or both? Our AWS-certified engineers will review your workload, flag high-risk issues in Security, Reliability, and Operational Excellence, and help you get a qualifying report ready for AWS Partner Central.
Book a Free FTR Readiness AssessmentAWS FTR vs WAFR FAQs
Is AWS FTR Required for Every AWS Marketplace Listing?
No. AWS FTR is not mandatory for every Marketplace listing. It validates eligible AWS Partner software solutions and supports access to benefits such as the Qualified Software badge and applicable AWS partner programs.
Can You Complete an AWS WAFR Without a Consultant?
Yes. Organizations can conduct a self-service Well-Architected Framework Review using the AWS Well-Architected Tool. They can also seek assistance from an AWS employee, a Well-Architected Program Partner (WAPP), or ISV tools.
How Long is AWS FTR Approval Valid?
AWS Foundational Technical Review approval remains valid for two years. After expiration, partners must complete the applicable validation process again to maintain their FTR status and associated eligibility.
Can You Reuse a WAFR Report for AWS FTR Validation?
Yes. AWS accepts an existing WAFR report if it is less than one year old, identifies the partner solution, includes required reviewer information, and shows zero high-risk issues in Security, Reliability, and Operational Excellence.
What is the Difference Between AWS WAF and WAFR?
AWS WAF and AWS WAFR are different AWS offerings. AWS WAF (Web Application Firewall) protects web applications against malicious HTTP(S) requests. AWS WAFR (Well-Architected Framework Review) evaluates cloud workload architecture against AWS best practices.
Written by
Paul Dhaliwal
Founder & Chief Executive Officer
Paul Dhaliwal is a tech innovator and Founder of CodeConductor, an open-source no/low-code platform. With 10+ years of experience in AI and scalable development, Paul focuses on crafting intelligent solutions that drive real-world value. A firm believer in the mantra "Eat, Sleep, Code, Repeat," he balances his passion for software with a love for travel and family.