Frequently asked questions
If you have a question about Quick Starts that isn't covered on this page, please contact us.
What is a Quick Start?
AWS Quick Starts are automated reference deployments for key workloads on the AWS Cloud. Each Quick Start launches, configures, and runs the AWS compute, network, storage, and other services required to deploy a specific workload on AWS, using AWS best practices for security and availability.
Quick Starts are accelerators that condense hundreds of manual procedures into just a few steps. They are fast, low-cost, and customizable. They are fully functional and designed for production.
Quick Starts include:
- A reference architecture for the deployment
- AWS CloudFormation templates (JSON or YAML scripts) that automate and configure the deployment
- A deployment guide, which explains the architecture and implementation in detail, and provides instructions for customizing the deployment
Quick Starts also include integrations that extend the cloud-based contact center functionality provided by Amazon Connect with key services and solutions from APN Partners—for customer relationship management (CRM), workforce optimization (WFO), analytics, unified communications (UC), and other use cases.
See the Quick Start catalog for a complete list of Quick Starts. Check back frequently for updates—we publish new Quick Starts on a regular basis.
What are the advantages of using a Quick Start?
Quick Starts can help save you time by eliminating hundreds of manual installation and configuration steps in the deployment of key technologies on the cloud. They implement AWS best practices, so they're designed with your security and availability needs in mind.
Here are some of the ways you can use Quick Starts:
- To deploy the technology on AWS with the least amount of effort and time.
- To develop your own solutions, using patterns and practices from the Quick Starts as a baseline.
- To accelerate solutions for your customers. The Quick Starts are modular and customizable. You can speed up your deployments by using the default automation or by stacking on top of existing Quick Starts. You can choose to build from the ground up, or you can deploy the workload into an existing virtual private cloud (VPC).
What's the difference between a Quick Start and a Marketplace AMI?
AWS Marketplace offers Amazon Machine Images (AMIs) for deploying software into your AWS account. Here are some of the differences between the two programs:
AWS Quick Start AWS Marketplace AMI Single-vendor or multi-vendor accelerators Single-vendor solutions Simple or complex deployments Low-friction, self-contained deployments Modular and customizable No customization BYOL, or leverage AWS Marketplace* and/or publicly available assets Billed to buyer's AWS account
* AWS Quick Starts use Marketplace AMIs whenever they are available. For example, the Trend Micro Deep Security Quick Start uses the Trend Micro Deep Security AMI.
What’s the difference between Quick Starts and an AWS Solutions Consulting Offer?
AWS Quick Starts are automated, customizable reference deployments of a popular technology. Built by AWS solutions architects and APN Partners, Quick Starts are deployed in the AWS Cloud using AWS best practices.
AWS Solutions Consulting Offers are vetted solutions to common business and technical problems deployed with help from AWS Competency Partners. Some AWS Solutions Consulting Offers include an AWS Quick Start as an accelerator to deployment in the AWS Cloud.
How much does it cost to deploy a Quick Start?
You are responsible for all costs related to the AWS services you use while running Quick Start reference deployments, and for any license fees. However, there is no additional cost for using the Quick Start.
For full pricing information, see the pricing pages for specific AWS services that the Quick Start uses.
After you deploy the Quick Start, we recommend that you set up the AWS Cost and Usage Report to track costs associated with the Quick Start.
How long does it take to deploy a Quick Start?
Most AWS Quick Start reference deployments enable you to spin up a fully functional architecture in less than an hour. A few can take longer, depending on the scope of the deployment. For information about deployment times for specific Quick Starts, see the deployment guides in the Quick Start catalog.
Note that the estimated deployment times do not include the setup and configuration of any technical prerequisites.
Which technologies are currently supported?
AWS Quick Starts provide automated deployments for DevOps, compliance, and Amazon Connect integrations, including:
The Quick Start catalog also includes Quick Starts for technologies from Microsoft, SAP, and Oracle, as well as Quick Starts for security, blockchain, machine learning, data lake, and big data and analytics technologies. Here are just a few:
- Trend Micro Deep Security
- Corda Enterprise
- Predictive Data Science with Amazon SageMaker and a Data Lake on AWS
- Cloudera Enterprise Data Hub (EDH)
For the full, and growing, list of automated reference deployments, see the Quick Start catalog.
What are the licensing requirements for Quick Starts?
Licensing requirements vary by Quick Start, but whenever possible, Quick Starts provide licensing options that give you the most flexibility and cost savings. Most Quick Start reference deployments use the Bring Your Own License (BYOL) model. This means that you can use your existing licenses for SAP HANA, Microsoft software, and so on. Using this model, you can move your existing workload to the AWS Cloud without paying additional software licensing fees. Some Quick Starts use trial licenses that you can upgrade to full licenses when you're ready for production.
To get licensing information for specific Quick Starts, see the deployment guides. For more information about using your existing licenses for Microsoft technologies, see the Microsoft License Mobility program.
Where can I find detailed technical information about a reference deployment?
Each deployment is discussed in detail in the guide that's provided with the Quick Start. The deployment guide describes the architecture, implementation details, best practices, customizations, and extensions.
The Quick Start templates are maintained in separate GitHub repos in the Quick Start organization. If you have any technical questions or suggestions, please post your feedback in the Issues section of the relevant Quick Start repo.
The default architecture doesn't work for me. Can I configure my deployment differently?
Yes, you can. Quick Starts allow you to tailor deployment settings to meet your requirements. For details, follow the instructions in the deployment guides.
You can also customize the Quick Start templates directly, by downloading them from the GitHub repo. We invite you to share your code to make your customizations available to others. See the Quick Start Contributor's Guide for details.
I'd like to build a Quick Start. How do I get started?
Where can I send my feedback or ideas for new Quick Starts?
Are Quick Starts supported at multiple commit levels (or different release tags)?
No, Quick Start reference deployments are supported only at the latest version (HEAD of master branch). Quick Starts are constantly tested and patched. Because of the continuous release cycle, bug reports are allowed only against the latest master. The aws-quickstart bucket is always in sync with the master branch. This ensures that the customers who launch the Quick Start from the Quick Start homepage always get the most up-to-date version of the Quick Start.
How can I lock a Quick Start to a specific version?
Quick Starts are designed to be modular and portable. This means that you can freeze the Quick Start content to a specific version or commit level by staging the content of the GitHub repository in a customer-owned bucket and updating the QSS3BucketName and QSS3KeyPrefix parameters. We recommend that you fork the Quick Start repo so that you can pull down updates from upstream:master at your own release cadence.
Note that if you plan to do stack updates, staging the Quick Start is mandatory to achieve cohesion within nested stacks.