The build workflow includes the following development tasks:
- Complete the items listed in the Prerequisites section. After we approve your proposal, we set up a Git repository for your Partner Solution files.
- Build your Partner Solution templates:
- Use the templates we've provided as building blocks.
- Design your code.
- Use existing AMIs.
- Design template parameters.
- Follow best practices.
- Add Partner Solution IDs.
- Create a deployment guide.
- Test and debug your code.
To find out how building a Partner Solution can help showcase your product on AWS and benefit both your company and your customers, watch this webinar.
The time commitment for building a Partner Solution depends on your AWS CloudFormation and coding skills as well as the complexity of the architecture, and can range from 2 to 8 weeks. Having dedicated, experienced engineering resources who can focus on the project shortens that development time.
The turnaround time from finalizing the templates (all tests pass) to launch (publication on the AWS Partner Solution site) is at least four weeks. We have a rolling launch schedule throughout the year, so we are generally able to publish a Partner Solution four weeks after its completion. However, we always have multiple Partner Solutions in our publishing queue, so some launches might be delayed. If you would like your Partner Solution to go live on a specific date, let us know as soon as possible so we can hold a launch date for you, and make sure that your templates are complete at least two weeks before the requested launch date.
Partner Solutions support several options, depending on your software-licensing model, including the following:
- BYOL: The customer signs up for a license on your website, and the Partner Solution prompts for the license key. Example: Tableau Server Partner Solution.
- Trial: The Partner Solution automatically sets up a trial license for your software, or the customer signs up for one. Partner Solutions are for production use, so you should provide instructions for upgrading to a full license when the trial ends.
- Amazon Machine Image (AMI): The customer subscribes to your software in AWS Marketplace, and the Partner Solution installs it from there. Licensing is handled through AWS Marketplace. Example: NGINX Plus Partner Solution.
- No license: The Partner Solution deploys an open-source version of the software. Example: MongoDB Atlas Partner Solution.
When the code and documentation are complete, the Integration & Automation team publishes them in the following locations:
- Partner Solution templates in the Partner Solution S3 bucket and in GitHub
- Partner Solution landing page (example) and deployment guide (example)
- Links from Partner Solution homepage and APN portal
The Integration & Automation team publishes a landing page for the Partner Solution. We expect you, as an AWS Partner, to promote the solution on your own with blog posts, webpages, links, social media, and so on.
After the Partner Solution is published, as the builder and author, you're responsible for keeping it up to date:
- Fix any bugs or issues reported by customers or uncovered through our testing process.
- Respond to questions and suggestions posted by customers in the GitHub repository.
- Revise the Partner Solution with new versions of your software, new AMIs, new AWS Regions, and any other updates.
- Address any security vulnerabilities in a timely manner.
If the Partner Solution becomes stale or stops functioning properly, and you're unable to address the issues, we will unpublish it.
Yes! If you're a partner, check with your AWS Partner Development Manager (PDM) or Partner Solutions Architect (PSA) to get information about the number of launches and deployment guide downloads. If you're not an AWS Partner, email us (the AWS Integration & Automation team) for this information. We don't share personally identifiable information (PII) associated with launches.
If you have other questions, email us (the AWS Integration & Automation team).