APN Partner Central

Customer Deployed Edge Solution Foundational Technical Review

Customer-Deployed Validation Checklist

Validity Period: August 2025-February 2026

This version of the checklist was released on August 29th, 2025. The next version of this checklist is expected to be released in February 2026. AWS Partners may continue to use this version of the checklist until May 2026. AWS Partners may submit applications using the previous release (February 2025) until November 27th, 2025. Please review the change log for a list of changes (if any) since the previous version.

Self-assessment Spreadsheet

Introduction

The Foundational Technical Review ('FTR') assesses an AWS Partner's solution against a specific set of AWS best practices around security, performance, and operational processes that are most critical for customer success. Passing the FTR is required to qualify AWS Software Partners for APN programs such as AWS Competency and AWS Service Ready, but any AWS Partner who offers a technology solution is eligible to request an FTR review through Partner Central.

A solution can have multiple components. This checklist is applicable to components which are edge-deployed by the customers. If your solution includes a component deployed by the customer in their AWS account please use the Checklist for customer deployed for that component. If your solution is a Partner hosted solution or include a Partner hosted component, please use the checklist for partner hosted solution for that component.

Expectations of Parties

AWS Partners must review this document in detail before submitting an AWS Foundational Technical Review request. If items in this document are unclear, AWS Partners should contact their Partner Development Representative (PDR) or Partner Development Manager (PDM). AWS reserves the right to make changes to this document at any time.

The FTR request must be submitted on the APN Partner Central. For more information on how to submit a request, please see the "Request an FTR" section on this page. If you need more information, please contact your PDR or PDM.

After submitting a request, an AWS Partner Solutions Architect will reach out with a self-assessment spreadsheet (also available for download at the top of this page) for the Partner to fill out. AWS Partners should prepare for the Technical Validation by reading the Checklist, completing and submitting a self-assessment for solution, and submitting all relevant objective evidence with the application, including architecture diagrams. An AWS Partner Solutions Architect will review for completeness and for compliance with the requirements.

The PSA approves an FTR if the solution meets all FTR requirements. If the solution has unfulfilled requirements, the partner can remediate all unfulfilled requirements to complete the FTR. If the FTR is not completed within six months, the Partner must submit a new FTR request and meet all the FTR requirements effective at that time which may include additional controls.

AWS Foundational Technical Review Prerequisites

AWS Partner must include the solution's architecture diagram in order to pass the FTR requirements.

  1. 1.0Foundational Technical Review Requirements

    1. 1.1Architecture Diagram

      Submitted Foundational Technical Review Request must include architecture diagrams.

      • Architecture diagrams must detail how the solution interacts with the AWS Cloud; specifically, what AWS tools and services are used in the solution.

      Note: Click here for best practices on how to build an acceptable Architecture Diagram.

Customer Deployed Technical Baseline Requirements

The following requirements apply to AWS Partners' Customer-Deployed Practice

Introduction

  • INT-001 - Introductory material must contain use cases for the software.

    Please provide the link to deployment guide and specify (page number, section, paragraph etc.) where it describes use cases for the software.

  • INT-002 - Describe a typical deployment including how it connects to AWS Service(s).

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it describes the typical deployment including how it connects to AWS Service(s).

  • INT-004 - Introductory material contains the expected amount of time to complete the deployment on one edge-device.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it describes the expected amount of time it takes to complete deployment.

Prerequisites and Requirements

  • PRQ-001 - All technical prerequisites and requirements to complete the deployment process are listed (e.g. required OS, database type and storage requirements).

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it lists all technical prerequisites and requirements needed to complete the deployment process.

  • PRQ-002 - The deployment guide lists all skills or specialized knowledge needed by the user (e.g. familiarity with AWS, specific AWS services, a scripting or programming language).

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it lists all skills or specialized knowledge that users need.

  • PRQ-003 - The deployment guide lists the environment configuration that is needed for the deployment (e.g. an AWS account, a specific operating system, licensing, DNS).

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it lists what environment configuration is needed for deployments.

Architecture Diagrams

  • ARCH-001 - Architecture diagram(s) must illustrate all AWS services running and the relationships between them in a typical customer deployment.

    Architecture diagram(s) illustrate standard deployment(s) on AWS.

  • ARCH-004 - Architecture diagram(s) use AWS Simple Icons.

    Architecture diagram(s) use AWS Simple Icons.

  • ARCH-006 - Architecture diagram(s) show integration points, including third party assets/APIs and on-premises/hybrid assets.

    Architecture diagram(s) show integration points, including third party assets/APIs and on-premises/hybrid assets.

Security

  • DSEC-002 - The application does not require the use of root privileges for deployment or operation.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it warns customers to not use the root user for any deployment or operations.

  • DSEC-003 - The deployment guide provides prescriptive guidance on following the policy of least privilege for all access granted as part of the deployment.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides prescriptive guidance on following the principle of least privilege for all access granted as part of the deployment.

  • DSEC-004 - The deployment guide clearly documents any public resources (e.g. Amazon S3 buckets with bucket policies allowing public access).

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it documents any public resources.

  • DSEC-005 - The deployment guide describes the purpose of each IAM role and IAM policy the user is instructed to create.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it describes the purpose of IAM roles/policies the user is instructed to create.

  • DSEC-006 - The deployment guide describes the purpose and location of each key the user is instructed to create.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it describes the purpose and location of each key the user is instructed to create.

  • DSEC-008 - The deployment guide includes details on where customer sensitive data are stored.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it describes where sensitive customer data are stored.

Costs

  • CST-001 - The deployment guide includes a list of billable services and guidance on whether each service is mandatory/optional.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it lists billable services and guidance on whether each service is mandatory/optional.

  • CST-002 - The deployment guide includes the cost model and licensing costs.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it includes the cost model and licensing costs.

Sizing

  • SIZ-001 - Either provide scripts to provision required resources or provide guidance for type and size selection for resources.

    Please provide the link to the scripts or the deployment guide and specify (page number, section, paragraph etc.) where it provides guidance.

Deployment Assets

  • DAS-001 - The deployment guide provides step-by-step instructions for deploying the software as per typical deployment architecture.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides step-by-step instructions for deploying the software as per typical deployment architecture.

  • DAS-003 - The deployment guide describes the different deployment configurations (e.g. for a solution that can connect to single and/or multi-region, an explanation of the different deployment configurations as well as the pros and cons of each is included).

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it describes the different deployment configurations.

  • DAS-004 - The deployment guide contains prescriptive guidance for testing/troubleshooting.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it contains prescriptive guidance for testing/troubleshooting.

Health Check

  • HLCH-001 - The deployment guide provides step-by-step instructions for how to assess and monitor the health and proper function of the application.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides step-by-step instructions for how to assess and monitor the health and proper function of the application.

Backup and Recovery

  • BAR-001 - Identify data stores to be backed up. If any of the data stores are proprietary, provide step by step instructions for backup and recovery.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides details on backup and recovery.

Routine Maintenance

  • RM-001 - The deployment guide provides step-by-step instructions for rotating programmatic system credentials and cryptographic keys.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides step-by-step instructions for rotating programmatic system credentials and cryptographic keys.

  • RM-002 - The deployment guide provides prescriptive guidance for software patches and upgrades.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides prescriptive guidance for software patches and upgrades.

  • RM-003 - The deployment guide provides prescriptive guidance on managing licenses.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides prescriptive guidance on managing licenses.

Emergency Maintenance

  • EMER-001 - The deployment guide provides step-by-step instructions on handling fault conditions.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides step-by-step instructions on handling fault conditions.

  • EMER-002 - The deployment guide provides step-by-step instructions on how to recover the software.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides step-by-step instructions on how to recover the software.

Support

  • SUP-001 - The deployment guide provides details on how to receive support.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides details on how to receive support.

  • SUP-002 - The deployment guide provides details on technical support tiers.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides details on technical support tiers.

  • SUP-003 - The deployment guide provides details on different support tiers and SLAs.

    Please provide the link to the deployment guide and specify (page number, section, paragraph etc.) where it provides details on different support tiers and SLAs.