Here's a quick list that you can use to check off your development tasks:
- Complete the items listed in the Prerequisites section.
- Work with us to set up a Git repository for your Quick Start files.
- Build your Quick Start templates:
- Use the templates we've provided as building blocks.
- Design your code.
- Use existing AMIs.
- Design template parameters.
- Follow best practices.
- Add Quick Start IDs.
- Create a deployment guide.
- Create a parameters file and configuration file.
- Test and debug your code.
To find out how building a Quick Start will help showcase your product on AWS and benefit both your company and your customers, watch the Quick Start webinar.
The time commitment for building a Quick Start 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 will make a big difference in shortening that development time.
The turnaround time from finalizing the templates (all tests pass) to launch (publication on the AWS Quick Start site) is at least four weeks. We have a rolling launch schedule throughout the year, so we are generally able to publish a Quick Start four weeks after its completion. However, we always have multiple Quick Starts in our publishing queue, so some launches might be delayed. If you would like your Quick Start 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.
Quick Starts support several options, depending on your software licensing model, including:
- BYOL: The user signs up for a license on your website, and the Quick Start prompts for the license key. For example: Tableau Server Quick Start.
- Trial: The Quick Start automatically sets up a trial license for your software, or the user signs up for one. Quick Starts are for production use, so you should provide instructions for upgrading to a full license when the trial ends. For example: Cloudera Quick Start.
- AMI: The user subscribes to your software in AWS Marketplace, and the Quick Start installs it from there. Licensing is handled through AWS Marketplace. For example: NGINX Plus Quick Start.
- No license: The Quick Start deploys an open-source version of the software. For example: MongoDB Quick Start.
The Quick Start team coordinates the launch with the AWS marketing team. Promotional content includes:
- What's new page on the AWS website (example)
- Social media (Facebook, Twitter, LinkedIn)
- Optional blog post (for example, see the APN blog or AWS blog)
- AWS internal announcement
We expect that you will also promote the Quick Start on your own website with blog posts, web pages, links, and social media. This makes a big difference in visibility and user adoption.
After the Quick Start is published, as the builder and author, you're responsible for keeping it up to date:
- Fix any bugs or issues reported by users or uncovered through our testing process.
- Respond to questions and suggestions posted by users in the GitHub repository.
- Revise the Quick Start with new versions of your software, new AMIs, new AWS Regions, and any other updates.
If the Quick Start becomes stale or stops functioning properly, and you're unable to fix it, we will remove it from the Quick Start catalog.
If you have small changes or updates to the Quick Start, give the Quick Start team at least one week's notice. Significant changes will require legal and IP review, and we may not be able to publish the update without at least two week's notice.
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 a partner, you can contact us at email@example.com for this information. Note that we don't share personally identifiable information (PII) associated with launches.