Suger is now Fours. Read the announcement

AWS FTR: Foundational Technical Review Checklist

The AWS FTR is now an automated check of a SOC 2 Type II or WAFR report. The six prerequisites in order, what each report must show, and what it unlocks.

Stacy Wu
Feb 21, 2025 ·

Updated November 12, 2026: Rewritten against AWS’s current FTR page and Partner Central Builder Guide, which describe a self-service review of a SOC 2 Type II or WAFR report behind six prerequisites; claims those pages don’t support, such as a “Reviewed by AWS” tag, three-year validity and a Well-Architected waiver, are removed.

The AWS Foundational Technical Review (FTR) is AWS’s check that a partner’s software follows a subset of its best practices for security, reliability and operational excellence, “as defined by the AWS Well-Architected Framework.” It is now self-service: you attach a SOC 2 Type II report or a Well-Architected Framework Review (WAFR) report to a solution in AWS Partner Central, and AWS says you receive approval or feedback “within minutes.”

The review itself is fast. What takes time is everything AWS checks before it accepts the upload, and producing a report that passes its automated checks. This checklist takes both in the order Partner Central does.

What does an approved AWS FTR get you?

An approval earns the solution AWS’s “Qualified Software” badge and a listing in the AWS Partner Solutions Finder, and makes it eligible for APN programs. AWS’s FTR page says approval unlocks “badging, program eligibility, and funding benefits,” and names funding, the AWS Competency Program and the AWS ISV Accelerate Program among the partner benefits it opens.

Two things it is not:

  • Not a requirement to list on AWS Marketplace. The dependency runs the other way: AWS accepts an FTR request only for a solution linked to an AWS Marketplace software product, so the listing comes first.
  • Not permanent. An approval “is valid for two years from approval,” and the solution’s Validation tab shows the expiration date.

Before you start

Have these in place before you open the Validation tab:

  • An AWS Partner Central account. AWS’s first step is to “complete AWS Partner Central registration to join the AWS Partner Network (APN).”
  • Partner Central linked to your AWS account. The first prerequisite depends on it: AWS points you to Partner Central AWS account linking, or to Partner Central on the AWS Console.
  • A solution in Partner Central. If you don’t have one yet, AWS says to select “Create solution” and complete the required fields.
  • An active AWS Marketplace software product: SaaS, AMI, Container or Machine Learning.
  • One report, less than a year old: a SOC 2 Type II or a WAFR. The report section below lists what each must show.

The FTR checklist: six prerequisites, in AWS’s order

Partner Central shows the prerequisites as a checklist on the solution’s Validation tab, and “checks run in sequence — later checks remain blocked until earlier ones pass.” Work down the list:

  1. The solution is linked to an AWS Marketplace product. Link it from the solution’s AWS Marketplace tab.
  2. It is linked to only one product. “FTR validation supports one product per solution.” If more than one is linked, remove the extras or create a separate solution for each product.
  3. It contains no non-AWS Marketplace products. Every product in the solution must be an AWS Marketplace listing.
  4. The product is software. SaaS, AMI, Container or Machine Learning. Professional services and other non-software types aren’t eligible for this validation path.
  5. The product is deployed on AWS. It needs an approved AWS hosted architecture: an architecture diagram, uploaded in the AWS Marketplace Management Portal, that shows the solution running on AWS infrastructure. What the Deployed on AWS badge proves walks through the hosting patterns and the diagram AWS expects.
  6. The product is Partner Revenue Measurement (PRM) enabled. After you enable PRM, “it can take up to 7 days for measurement data to appear,” and the check completes when the product appears in your Attributed revenue dashboard as an onboarded product. Choosing between resource tagging and a User Agent string for PRM covers the build.

After you fix one, choose Refresh on the Validation tab to update its status. PRM is the last check and the slowest to register, so start it at least a week before you plan to submit.

SOC 2 Type II or WAFR: what each report must show

AWS accepts either report, and its automated review checks each against its own list:

CheckSOC 2 Type II reportWAFR report
AgeIssue date within 1 yearLess than 1 year old
ResultUnqualified auditor opinionZero high-risk issues in the Security, Operational Excellence and Reliability pillars
Your solutionThe specific solution is in scopeNamed in the workload name or the workload description
Also requiredAWS infrastructure in scope (the system description references your AWS-hosted components); the Security and Availability trust services criteria includedConducted in the AWS Well-Architected Tool; the reviewer’s full name and email address in the reviewer owner field

The SOC 2 route suits a company that already holds a current Type II report scoped to this solution and its AWS infrastructure. A report whose scope doesn’t include the specific solution fails the check, however clean the opinion.

The WAFR route is one your own team can complete. AWS says the review “can be performed by the partner as a self-service exercise,” or with the help of an AWS employee, a Well-Architected Program Partner or ISV tools. A WAFR assesses all six Well-Architected pillars, but the high-risk-issue check counts only Security, Operational Excellence and Reliability.

How to submit the FTR request

Once every prerequisite shows Complete:

  1. Sign in to AWS Partner Central.
  2. Choose Build, then Solutions, and choose the solution.
  3. Open the Validation tab and confirm that every prerequisite shows Complete.
  4. Choose Request validation.
  5. For Report type, select SOC 2 report or WAFR report.
  6. Upload the report as a PDF of no more than 3 MB.
  7. Choose Request FTR.

AWS reviews the submission automatically.

Approved or Action required: reading the result

The solution’s FTR status changes to one of two outcomes:

  • Approved. The Validation tab shows the FTR expiration date, and the solution is eligible for badging, a Partner Solutions Finder listing and APN program eligibility.
  • Action required. The Validation tab lists which checks failed and what to address. Resolve them with your auditor or team, choose Resubmit, and upload the corrected report. AWS says “you can resubmit as many times as needed,” and each resubmission also returns a result within minutes.

Plan for the expiration date now

An approval lasts two years, and the Validation tab shows when it ends. AWS’s pages describe no separate renewal step, but every submission is checked for a report less than a year old, so the report behind your first approval will be too old to reuse. Put the expiration date in the same calendar as your marketplace agreement renewals, and schedule the next SOC 2 audit or WAFR so a current report exists before that date arrives.

Where Fours fits

Fours doesn’t perform the FTR, produce the SOC 2 or WAFR report, or submit the request; those stay with your team and your auditor in AWS Partner Central. It works on either side of the review. Before it, Fours lists and manages the AWS Marketplace product the solution has to link to. After it, once you co-sell, Fours connects your CRM (Salesforce, HubSpot or Dynamics 365) to AWS Partner Central and keeps referrals in sync for the life of the deal. The ACE eligibility steps on doc.fours.com show where the FTR falls among the other requirements to co-sell with AWS.

The FTR is one gate on a longer path: how the AWS Software Path’s stages work, and what each one unlocks, covers where it sits.

Sources

Primary sources for the platform rules cited above. Last verified November 12, 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