Quick answer: The AWS Foundational Technical Review (FTR) is a gated assessment required to enter the AWS ISV Accelerate co-sell program. It validates that your product meets AWS's baseline security, reliability, and operational standards. The FTR is not required to list on AWS Marketplace — only to unlock co-sell.
The AWS Foundational Technical Review (FTR) is a technical assessment required for ISVs seeking to join the AWS ISV Accelerate program. It validates that the ISV's product meets AWS's baseline security, reliability, and operational standards. Passing the FTR is a prerequisite for co-sell eligibility on AWS Marketplace through ISV Accelerate.
What is the AWS FTR?
The FTR is a technical review conducted by the AWS Partner Network (APN) to validate the security and architecture of an ISV's product. It is conducted as a self-assessment with evidence submission — not a code audit. AWS assigns a technical reviewer who evaluates your documentation and asks clarifying questions.
The FTR is required for:
- ISV Accelerate program entry — the co-sell program that gives you access to AWS's field sales team
- AWS Competency applications (Healthcare, Security, Financial Services, etc.) — these have their own additional requirements on top of the FTR
- AWS Partner Network tier progression — advancing from Select to Advanced or Premier Partner tier
The FTR does not replace a security audit, a SOC 2 assessment, or an AWS Well-Architected Review. It is a documented evidence review against a specific AWS checklist.
Why the FTR matters for marketplace ISVs
ISV Accelerate is the most direct path to AWS co-sell. AWS's field sales team has quota credit for marketplace deals — they are incentivized to bring your product into their active accounts. Without ISV Accelerate, your listing exists in the catalog but you have no AWS sales partner actively referencing you.
The practical impact:
- Co-sell pipeline: Enrolled ISVs can register deals and receive inbound co-sell referrals from AWS account executives
- Reduced transaction fee: ISV Accelerate eligible listings may qualify for a reduced marketplace transaction fee on co-sell originated deals (confirm current terms with your AWS PDM)
- Enterprise buyer signal: Some enterprise procurement teams check for AWS Partner status as a vendor qualification criterion
- GTM support: AWS PDMs (Partner Development Managers) actively support ISV Accelerate members with introductions and deal support
Key point: You can list on AWS Marketplace without the FTR. You cannot enroll in ISV Accelerate without passing the FTR. For most ISVs, co-sell is where the marketplace revenue comes from — so the FTR is effectively a prerequisite for meaningful marketplace performance.
The six FTR pillars
The FTR maps to the AWS Well-Architected Framework and assesses your product across six pillars. You must provide documented evidence for each:
1. Security
Identity and access management (IAM), encryption at rest and in transit, network security, vulnerability management, and incident response procedures.
2. Reliability
Disaster recovery plan, backup procedures, change management process, and monitoring and alerting setup.
3. Performance Efficiency
Resource selection rationale, elasticity design, and right-sizing practices for your AWS workload.
4. Cost Optimization
Resource usage tracking, cost allocation tagging, and awareness of spend-efficient architecture choices.
5. Operational Excellence
Runbooks for standard operations, logging configuration, and operational health monitoring setup.
6. Sustainability
Resource efficiency practices — a newer pillar focused on minimizing unnecessary compute and storage usage.
Of these, Security and Reliability receive the most scrutiny. Missing evidence in either pillar is the most common reason FTR submissions are returned for remediation.
How the FTR process works
The FTR is initiated and managed through APN Partner Central. Here is the end-to-end process:
- Enroll in the AWS Partner Network (APN) as a Technology Partner if not already registered.
- Register your product in APN Partner Central under the relevant product category (SaaS, AMI, container, etc.).
- Request an FTR through APN Partner Central — this opens a shared workspace between you and an AWS technical reviewer.
- Complete the FTR questionnaire — self-assessed answers with supporting evidence: screenshots, policy documents, architecture diagrams, monitoring configurations.
- AWS technical reviewer evaluates your submission and may ask follow-up questions or request additional evidence.
- Address any findings — clarifications or required fixes to meet the checklist criteria.
- FTR approved — your product receives "FTR Reviewed" status in the APN.
- Apply for ISV Accelerate — once FTR status is confirmed, you can submit your ISV Accelerate enrollment request.
Timeline: Typically 4–8 weeks from initial submission to approval, assuming evidence is prepared in advance. Well-prepared ISVs with documented security and operational controls complete it in 4–5 weeks. ISVs that discover gaps during the process take longer.
Common FTR failure points
After delivering 80+ marketplace listings through the AWS co-sell process, we see these patterns repeatedly delay or fail the FTR:
Most common blocker: Missing or incomplete encryption documentation. AWS requires specifics — which AWS services are used, which key management approach (SSE-S3, KMS, customer-managed keys), and coverage for both data at rest and data in transit. Vague answers are returned for revision.
Frequent failure points
- Missing encryption documentation: AWS expects specific details — not just "we use HTTPS." You need to document encryption at rest (which services, which keys) and in transit (TLS version, certificate management).
- No written incident response plan: AWS expects a runbook, not just infrastructure. A page in Confluence or Notion describing your incident classification, escalation, and response steps satisfies this requirement.
- Lack of logging and monitoring evidence: CloudWatch (or equivalent) must be configured and documented. Screenshots showing active alarms and log groups are the accepted evidence format.
- Missing architecture diagram: AWS requires a current diagram showing how your product is deployed on AWS — services, network topology, data flow, and trust boundaries. An outdated or generic diagram will prompt follow-up questions.
- No formal vulnerability management process: Even a simple documented patch schedule (e.g., "OS patches applied within 14 days of release, critical patches within 72 hours") satisfies this requirement.
- IAM policies too permissive: Broad IAM roles (e.g.,
*actions on*resources) violate least-privilege principles. AWS will flag these and require narrowed policies with justification.
FTR vs AWS Well-Architected Review
ISVs often confuse these two reviews. They are related but serve different purposes:
| FTR | Well-Architected Review | |
|---|---|---|
| Purpose | Partner program gating (ISV Accelerate, Competencies) | Ongoing workload improvement for your own benefit |
| Frequency | Once per product (with renewal if major changes occur) | Recommended annually or after major architectural changes |
| Who conducts it | AWS technical reviewer via APN Partner Central | AWS Solutions Architect or AWS Partner (you can self-assess) |
| Output | "FTR Reviewed" status in APN | Well-Architected Review report with high/medium risk findings |
| Required for marketplace? | Required for ISV Accelerate only | Not required |
Completing a Well-Architected Review is an effective way to prepare for the FTR — the two frameworks overlap significantly. However, passing a Well-Architected Review does not automatically satisfy the FTR; you must still complete the FTR submission process through APN Partner Central.
Need help getting through the FTR?
Automatum has delivered 80+ marketplace listings through the AWS co-sell process, including FTR preparation and ISV Accelerate enrollment. Our team knows which evidence AWS reviewers look for.
Talk to our team →