AWS Partner Solutions (formerly Quick Starts)
General Information Guide
Amazon Web Services (AWS) Partner Solutions are automated reference deployments built by AWS solutions architects and AWS Partners. Partner Solutions help you deploy popular technologies on AWS according to AWS best practices. You can reduce hundreds of manual procedures to a few steps so that you can build and start using your environment within minutes.
Visit our GitHub organization for source files and to post feedback, report bugs, or submit feature ideas for Partner Solutions.
|Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on a Partner Solution.|
You are responsible for the cost of the AWS services and any third-party licenses used while running a Partner Solution. There is no additional cost for using the Partner Solution.
The AWS CloudFormation templates for Partner Solutions include configuration parameters that you can customize. Some of the settings, such as the instance type, affect the cost of deployment. For cost estimates, refer to the pricing pages for each AWS service you use. Prices are subject to change.
|After you deploy the Partner Solution, create AWS Cost and Usage Reports to deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. These reports provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, refer to What are AWS Cost and Usage Reports?|
After you successfully deploy a Partner Solution, confirm that your resources and services are updated and configured—including any required patches—to meet your security and other needs. For more information, refer to the AWS Shared Responsibility Model.
Planning the deployment
Partner Solution deployments require a moderate level of familiarity with AWS services. If you’re new to AWS, refer to Getting Started Resource Center and AWS Training and Certification. These sites provide materials for learning how to design, deploy, and operate your infrastructure and applications on the AWS Cloud.
If you don’t already have an AWS account, create one at https://aws.amazon.com by following the on-screen instructions. Part of the sign-up process involves receiving a phone call and entering a PIN using the phone keypad.
Your AWS account is automatically signed up for all AWS services. You are charged only for the services you use.
If necessary, request service quota increases for the resources deployed by the Partner Solution. You might request increases if your existing deployment is at risk of exceeding default quotas. The Service Quotas console displays your usage and quotas for some aspects of some services. For more information, refer to AWS service quotas and What is Service Quotas?
Supported AWS Regions
For any Partner Solution to work in a Region other than its default Region, all the services it deploys must be supported in that Region. You can launch a Partner Solution in any Region and see if it works. If you get an error such as "Unrecognized resource type," the Partner Solution is not supported in that Region.
For an up-to-date list of AWS Regions and the AWS services they support, refer to AWS Regional Services. Some Regions are available on an opt-in basis. For more information, refer to Managing AWS Regions.
Amazon EC2 key pairs
Some Partner Solutions deploy Amazon Elastic Compute Cloud (Amazon EC2) instances. If the Partner Solution you launch includes one or more EC2 instances, ensure that at least one Amazon EC2 key pair exists in your AWS account in your selected Region. Note the key-pair name because you will use it during deployment.
For testing or proof-of-concept purposes, create a new key pair instead of using one that’s already being used by a production instance. For more information, refer to Amazon EC2 key pairs and Linux instances or Amazon EC2 key pairs and Windows instances.
Before launching the Partner Solution, you must sign in to the AWS Management Console with IAM permissions for the resources that the templates deploy. The AdministratorAccess managed policy within IAM provides sufficient permissions, although your organization may choose to use a custom policy with more restrictions. For more information, refer to AWS managed policies for job functions.
To submit any issues about this guide, refer to the following links:
This document is provided for informational purposes only. It represents current AWS product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS products or services, each of which is provided "as is" without warranty of any kind, whether expressed or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.
The software included with this paper is licensed under the Apache License, version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at http://aws.amazon.com/apache2.0/ or in the accompanying "license" file. This code is distributed on an "as is" basis, without warranties or conditions of any kind, either expressed or implied. See the License for specific language governing permissions and limitations.