AWS partner-central documentation change
Summary
Complete rewrite of FTR request documentation, adding sections on accepted validation documents (SOC 2/WAFR), prerequisites, detailed submission steps, validation controls, and resubmission process.
Security assessment
The change significantly expands documentation about security validation processes (SOC 2/WAFR reports) and security-focused validation controls, but doesn't address any specific vulnerability. It enhances clarity on security requirements for solutions.
Diff
diff --git a/partner-central/latest/builder-guide/requesting-ftr.md b/partner-central/latest/builder-guide/requesting-ftr.md index 64e3063fb..82dd99dbd 100644 --- a//partner-central/latest/builder-guide/requesting-ftr.md +++ b//partner-central/latest/builder-guide/requesting-ftr.md @@ -7 +7 @@ -# Request [Foundational Technical Review](https://aws.amazon.com/partners/foundational-technical-review) for your solutions +Accepted validation documentsPrerequisitesRequest FTR validationReview resultsValidation controlsResubmit after feedbackRelated resources @@ -9 +9 @@ -You can obtain an FTR to validate each of your submitted, active solutions of the following types: Software Products, Managed, Consulting, or Professional Service. An FTR helps you identify and mitigate any technical risks for your solution. +# Request Foundational Technical Review for your solutions @@ -11 +11 @@ You can obtain an FTR to validate each of your submitted, active solutions of th -###### To request an FTR +You can submit a Foundational Technical Review (FTR) validation request for your active software solutions listed in AWS Marketplace. The streamlined FTR process 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. @@ -13 +13 @@ You can obtain an FTR to validate each of your submitted, active solutions of th - 1. Log in to [AWS Partner Central](https://partnercentral.awspartner.com/APNLogin). +## Accepted validation documents @@ -15 +15 @@ You can obtain an FTR to validate each of your submitted, active solutions of th - 2. Download and review the AWS Foundational Technical Review Guide for [Software solutions](https://partnercentral.awspartner.com/partnercentral2/s/resources?Id=0690h00000BGRJhAAP) or [Service solutions](https://partnercentral.awspartner.com/partnercentral2/s/resources?Id=0698W00000hQrlnQAC), and FTR checklist for your solution type. +You can submit either of the following reports to satisfy FTR requirements: @@ -17 +17 @@ You can obtain an FTR to validate each of your submitted, active solutions of th - 3. From the Navigation bar, select **Build** then **Solutions**. + * **SOC 2 Type II report** — A third-party audit report from an accredited auditor that covers the trust services criteria for your AWS-hosted workload. @@ -19 +19 @@ You can obtain an FTR to validate each of your submitted, active solutions of th - 4. Click on the solution you would like to have validated. + * **[AWS Well-Architected Framework Review](https://docs.aws.amazon.com/wellarchitected/latest/userguide/waf.html) (WAFR) report** — A completed review that assesses your workload against the six pillars of the AWS Well-Architected Framework: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. The review must cover your solution's primary AWS-hosted workload. @@ -21 +20,0 @@ You can obtain an FTR to validate each of your submitted, active solutions of th - 5. Navigate to the **Validation** tab, select **Request Validation**. @@ -23 +21,0 @@ You can obtain an FTR to validate each of your submitted, active solutions of th - 6. Complete the self-assessment checklist and upload this file, your architecture diagram(s), and any other required or supplemental documentation that's relevant to the solution and case studies that demonstrate customer success specific to the solution. Note: There is a maximum file size of 3MB per document upload. @@ -25 +23,108 @@ You can obtain an FTR to validate each of your submitted, active solutions of th - 7. Select **Request Foundational Technical Review**. + +## Prerequisites + +Your solution must meet the following requirements before you can submit for FTR validation. In AWS Partner Central, the **Validation** tab displays these as a prerequisite checklist. Checks run in sequence — later checks remain blocked until earlier ones pass. + +Prerequisite | Description +---|--- +Solution is linked to an AWS Marketplace product | Your solution must have an AWS Marketplace product linked through the AWS Marketplace tab. To complete this, ensure you have completed [Partner Central AWS account linking](https://docs.aws.amazon.com/partner-central/latest/getting-started/account-linking.html) or access Partner Central on the AWS Console. +Solution is linked to only one AWS Marketplace product | FTR validation supports one product per solution. If your solution has multiple products linked, remove extras or create a separate solution for each product. +Solution does not contain non-AWS Marketplace products | All products in the solution must be AWS Marketplace listings. Remove any non-Marketplace products. +Solution is linked to a software product | The linked product must be a software type (SaaS, AMI, Container, or Machine Learning). Professional services and other non-software types are not eligible for this validation path. +AWS Marketplace product is deployed on AWS | Your product must have an approved AWS hosted architecture. Upload an architecture diagram in the AWS Marketplace Management Portal showing your solution running on AWS infrastructure. +AWS Marketplace product is Partner Revenue Measurement (PRM) enabled | [Partner Revenue Measurement](https://docs.aws.amazon.com/PRM/latest/aws-prm-onboarding-guide/what-is-service.html) must be enabled for the product. After you enable PRM, it can take up to 7 days for measurement data to appear. This check is complete when the product appears in your [Attributed revenue dashboard](https://docs.aws.amazon.com/partner-central/latest/getting-started/partner-analytics-attributed-revenue.html) as an onboarded product. + +After you make changes to resolve a prerequisite, choose **Refresh** on the Validation tab to update the status. + +## Request FTR validation + +After all prerequisites show as complete, you can submit a validation document. + + 1. Sign in to [AWS Partner Central](https://partnercentral.awspartner.com). + + 2. From the navigation, choose **Build** , then **Solutions**. + + 3. Choose the solution you want to validate. + + 4. Navigate to the **Validation** tab. Confirm that all prerequisites show a status of **Complete**. + + 5. Choose **Request validation**. + + 6. For **Report type** , select either **SOC 2 report** or **WAFR report**. + + 7. Upload your validation document. Maximum file size is 3 MB. Accepted format: PDF. + + 8. Choose **Request FTR**. + + + + +Your submission is reviewed automatically. You receive approval or feedback within minutes. + +## Review results + +After you submit, the FTR status on your solution updates to reflect the outcome: + + * **Approved** — Your solution passed FTR validation. The Validation tab displays the FTR expiration date and your solution is eligible for program benefits including badging, Partner Solutions Finder listing, and APN program eligibility. + + * **Action required** — Your submission did not pass one or more validation controls. The Validation tab displays specific feedback identifying which controls failed and what to address. Review the feedback, work with your auditor or team to resolve the issues, then choose **Resubmit** to upload an updated report. + + + + +## Validation controls + +The automated review evaluates your submitted report against the following controls. For the full list of FTR requirements, see the [Software FTR checklist](https://aws.amazon.com/partners/foundational-technical-review). + +**SOC 2 Type II reports:** + + * Report issue date is within 1 year + + * Unqualified auditor opinion + + * AWS infrastructure is in scope (system description references your AWS-hosted components) + + * The specific partner solution is in scope + + * Security and Availability trust services criteria are included + + + + +**WAFR reports:** + + * Report is less than 1 year old + + * Zero high-risk issues (HRIs) identified in the Security, Operational Excellence, and Reliability pillars + + * The specific partner solution is referenced in either the workload name or workload description + + * The WAFR is conducted using the AWS Well-Architected Tool (the review can be performed by the partner as a self-service exercise, or with the assistance of an AWS employee, a Well-Architected Program Partner (WAPP), or ISV tools) + + + + +## Resubmit after feedback + +If your report does not pass validation: + + 1. On the **Validation** tab, review the feedback in the **Validation feedback** section. + + 2. Address the identified issues with your auditor or team. + + 3. Choose **Resubmit**. + + 4. Upload the corrected report and submit. + + + + +You can resubmit as many times as needed. Each submission is reviewed automatically and returns results within minutes. + +## Related resources + + * [AWS Well-Architected Framework](https://docs.aws.amazon.com/wellarchitected/latest/userguide/waf.html) + + * [Partner Revenue Measurement onboarding guide](https://docs.aws.amazon.com/PRM/latest/aws-prm-onboarding-guide/what-is-service.html) + + * [Attributed revenue dashboard](https://docs.aws.amazon.com/partner-central/latest/getting-started/partner-analytics-attributed-revenue.html)