Before you begin
Before beginning the process of migrating to ACE v14, it is necessary to do some preparatory work. The good news is that this can be done in advance of the technical aspects of the migration, allowing you to get a head start.
The first step is to add your solutions to ACE. This can be confusing because the AWS documentation also refers to solutions as "offerings". It is important to understand that for the purposes of the ACE v14 migration, solutions and offerings are the same thing. More specifically, a solution as defined by AWS is "a solution delivered as a product, service, or practice, that leverages the AWS Cloud and is sold to customers. Offerings are considered repeatable and scalable, and deliver on a customer's desired business outcome(s). It can include outcomes or amenities that represent additional value to customers, such as availability, convenient delivery, technical support or quality of service." If you have access to AWS Partner Central, you can refer to the AWS Partner Solutions Overview Guide🔗 for more detailed information.
Adding your solutions to ACE is not only a requirement for ACE v14, it also improves the ability to correctly surface and understand your value offering when evaluating co-sell opportunities.
Now that we know what solutions are and why we need them, let's get started! You will need the following resources:
Partner Central Account Admin with “Alliance Lead” role
Create a solution
Log in to AWS Partner Central.
Select Build -> Offerings.
Click Create.
You should complete all fields (including optional ones) if possible to maximize the value of the offering to your co-sell motion. The following fields are required and must be completed in all cases:
Offering title is limited to 72 characters and should make clear what the solution is.
Offering description is limited to 1000 characters and should outline a concise breakdown of the advantages and capabilities of your solution. Descriptions longer than 188 characters will show a truncated description with a Show more link for the complete description.
Offering selling proposition is limited to 2000 characters and should indicate clear business results that customers should expect. Utilize data driven claims, avoid ambiguous claims such as "the best" or "world class".
SaaS offerings have an additional requirement to configure deployment details.
You can choose either You or Your customers as the primary deployment method for your software. This is not editable after the offering has been submitted.
If you choose You as the deployment method, you have the option to identify if the software has a secondary component.
You must indicate where the software is hosted.
Enter the approximate percentage of the software that operates on AWS.
Enter the contact information for someone in your organization that will be responsible for the solution. This person should have access to AWS Partner Center with sufficient permission to manage the solution.
Request a Foundational Technical Review
You may very likely have completed a Foundational Technical Review when you first onboarded to AWS, however, if this is a net new solution, you can request a Foundational Technical Review (FTR) to validate each of your submitted, active offerings of the following types: Software Products, Managed, Consulting, or Professional Service. Solutions are published to your AWS Partner Solution Finder listing when the Foundational Technical Review is approved and your solution's status is Active.
Log in to AWS Partner Central.
Select Build -> Offerings.
Choose the solution you want to submit for review.
Click on the Validation tab.
Download and check the AWS FTR Guide for Software Offerings or Service Offerings and FTR checklist for your solution type.
Complete the checklist for your self-assessment.
Submit the following files (files must be 3MB or less):
Self-assessment checklist
Architecture diagram(s)
Documentation relevant to your solution (required and/or supplemental)
Customer success case studies specific to the solution
Click Request Foundational Technical Review.
For greater detail, refer to the AWS documentation in Partner Central🔗.