Aerospike Database Enterprise Edition on the AWS Cloud

Quick Start Reference Deployment

QS

November 2021
Marek Counts and Sourabh Bhagat, Aerospike Inc.
Andrew Gargan, AWS Quick Start team

Visit our GitHub repository for source files and to post feedback, report bugs, or submit feature ideas for this Quick Start.

This Quick Start was created by Aerospike Inc. in collaboration with Amazon Web Services (AWS). Quick Starts are automated reference deployments that use AWS CloudFormation templates to deploy key technologies on AWS, following AWS best practices.

Overview

This guide provides instructions for deploying the Aerospike Quick Start reference architecture on the AWS Cloud.

This Quick Start is for people who want to get started with Aerospike on the AWS Cloud using current best practices, high availability, and security-related features.

Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.

Aerospike Database Enterprise Edition on AWS

Aerospike is a real-time NoSQL data-storage platform. It delivers predictable performance at petabyte scale with microsecond latency across billions of transactions.

When you use Aerospike with data-intensive, geodistributed applications, it performs like a cache with the persistence of a NoSQL data platform. It provides multisite clustering, cross-datacenter replication, fast restarts, rapid rebalancing, and security-related features.

Aerospike features a hybrid memory architecture where indexes, including the primary index and optional secondary indexes, are stored by default in dynamic random-access memory (DRAM) for fast access. You can also store data on solid state drives (SSDs) by configuring each namespace separately. Small namespaces can take advantage of DRAM, and larger ones gain the cost benefits of SSDs.

Quick Starts are automated reference deployments that use AWS CloudFormation templates. You use Quick Starts to launch, configure, and run the AWS compute, network, storage, and other services required to deploy a specific workload on AWS. This Quick Start helps you build an Aerospike cluster.

AWS costs

You are responsible for the cost of the AWS services and any third-party licenses used while running this Quick Start. There is no additional cost for using the Quick Start.

The AWS CloudFormation templates for Quick Starts include configuration parameters that you can customize. Some of the settings, such as the instance type, affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you use. Prices are subject to change.

After you deploy the Quick Start, 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, see What are AWS Cost and Usage Reports?

Software licenses

The Quick Start requires a subscription to the Amazon Machine Image (AMI) for Aerospike Database Enterprise Edition in AWS Marketplace. Additional pricing, terms, and conditions may apply. For instructions, see Subscribe to the Aerospike AMI.

If you don’t have a license, the Quick Start deploys with a trial license. The Quick Start deploys with a single-node trial license unless you request a three-node trial license. The trial license gives you all the enterprise features in a nonproduction environment. If you want to upgrade to a production license, contact Aerospike.

Architecture

Deploying this Quick Start for a new virtual private cloud (VPC) with default parameters builds the following Aerospike environment in the AWS Cloud.

Architecture
Figure 1. Quick Start architecture for Aerospike on AWS

As shown in Figure 1, the Quick Start sets up the following:

  • A highly available architecture that spans two or more Availability Zones.*

  • A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*

  • In the public subnets:

    • Managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets.*

    • A Linux bastion host in an Auto Scaling group to allow inbound Secure Shell (SSH) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in public and private subnets.*

  • In the private subnets:

    • An Auto Scaling group of EC2 instances configured with Aerospike Database Enterprise Edition and Aerospike tools.

    • An Amazon Elastic Block Store (Amazon EBS) volume in each subnet.

  • Amazon CloudWatch for logging and monitoring the Aerospike instances.

  • Amazon Simple Queue Service (Amazon SQS) for Aerospike migration.

* The template that deploys the Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

Planning the deployment

Specialized knowledge

This deployment requires a moderate level of familiarity with AWS services. If you’re new to AWS, see 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.

There are many considerations for a production-grade Aerospike deployment. This Quick Start was designed for general-purpose use and is not intended as a high-performance configuration. To learn more about high-performance and fully resilient configurations, see Aerospike best practices for AWS instance types with locally attached SSDs as documented here: Aerospike on Amazon EC2 - Recommendations.

AWS account

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.

Technical requirements

Before you launch the Quick Start, review the following information and ensure that your account is properly configured. Otherwise, deployment might fail.

Resource quotas

If necessary, request service quota increases for the following resources. You might need to request increases if your existing deployment currently uses these resources and if this Quick Start deployment could result in exceeding the default quotas. The Service Quotas console displays your usage and quotas for some aspects of some services. For more information, see What is Service Quotas? and AWS service quotas.

Resource This deployment uses

VPC

1

Elastic IP addresses

3

Security groups

2

AWS Identity and Access Management (IAM) roles

2

Auto Scaling groups

2

EC2 instances

2 to 16

Supported AWS Regions

For any Quick Start 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 Quick Start in any Region and see if it works. If you get an error such as “Unrecognized resource type,” the Quick Start is not supported in that Region.

For an up-to-date list of AWS Regions and the AWS services they support, see AWS Regional Services.

Certain Regions are available on an opt-in basis. For more information, see Managing AWS Regions.

Amazon EC2 key pairs

Ensure that at least one Amazon EC2 key pair exists in your AWS account in the Region where you plan to deploy the Quick Start. Note the key-pair name because you will use it during deployment. To create a key pair, see Amazon EC2 key pairs and Linux instances.

For testing or proof-of-concept purposes, we recommend creating a new key pair instead of using one that’s already being used by a production instance.

IAM permissions

Before launching the Quick Start, 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, see AWS managed policies for job functions.

Prepare your AWS account

Ensure that your account has permissions required to create the resources listed in the Resource quotas section of this guide.

Prepare for the deployment

Obtain any necessary software licenses before you deploy this Quick Start. For details, see the Software licenses section of this guide.

Deployment options

This Quick Start provides two deployment options:

  • Deploy Aerospike into a new VPC. This option builds a new AWS environment consisting of the VPC, subnets, NAT gateways, security groups, bastion hosts, and other infrastructure components. It then deploys Aerospike into this new VPC.

  • Deploy Aerospike into an existing VPC. This option provisions Aerospike in your existing AWS infrastructure.

The Quick Start provides separate templates for these options. It also lets you configure Classless Inter-Domain Routing (CIDR) blocks, instance types, and Aerospike settings, as discussed later in this guide.

You can deploy either a single-node or three-node cluster. For more information, see Aerospike Quick Start for AWS.

Deployment steps

Confirm your AWS account configuration

  1. Sign in to your AWS account at https://aws.amazon.com with an IAM user role that has the necessary permissions. For details, see Planning the deployment earlier in this guide.

  2. Make sure that your AWS account is configured correctly, as discussed in the Technical requirements section.

Subscribe to the Aerospike AMI

This Quick Start requires a subscription to the AMI for Aerospike in AWS Marketplace.

  1. Sign in to your AWS account.

  2. Open the page for the Aerospike AMI in AWS Marketplace, and then choose Continue to Subscribe.

  3. Review the terms and conditions for software usage, and then choose Accept Terms.

    A confirmation page loads, and an email confirmation is sent to the account owner. For detailed subscription instructions, see the AWS Marketplace documentation.

  4. When the subscription process is complete, exit out of AWS Marketplace without further action. Do not provision the software from AWS Marketplace—the Quick Start deploys the AMI for you.

  5. If you’re deploying a three-node Aerospike cluster, request a license using this form. For additional tips and tools for configuring the settings, see Aerospike Quick Start for AWS.

Launch the Quick Start

If you’re deploying Aerospike into an existing VPC, make sure that your VPC has at least two private subnets in different Availability Zones for the workload instances and that the subnets aren’t shared. This Quick Start doesn’t support shared subnets. These subnets require NAT gateways in their route tables to allow the instances to download packages and software without exposing them to the internet. Also make sure that the domain name option in the DHCP options is configured as explained in DHCP options sets. You provide your VPC settings when you launch the Quick Start.

Each deployment takes about 15 minutes to complete.

  1. Sign in to your AWS account, and choose one of the following options to launch the AWS CloudFormation template. For help with choosing an option, see Deployment options earlier in this guide.

    Deploy Aerospike into a new VPC on AWS

    View template

    Deploy Aerospike into an existing VPC on AWS

    View template

  2. Check the AWS Region that’s displayed in the upper-right corner of the navigation bar, and change it if necessary. This Region is where the network infrastructure for Aerospike is built. The template is launched in the us-east-2 Region by default. For other choices, see Supported Regions earlier in this guide.

  3. On the Create stack page, keep the default setting for the template URL, and then choose Next.

  4. On the Specify stack details page, change the stack name if needed. Review the parameters for the template. Provide values for the parameters that require input. For all other parameters, review the default settings and customize them as necessary. For details on each parameter, see the Parameter reference section of this guide. When you finish reviewing and customizing the parameters, choose Next.

  5. On the Configure stack options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you finish, choose Next.

  6. On the Review page, review and confirm the template settings. Under Capabilities, select the two check boxes to acknowledge that the template creates IAM resources and might require the ability to automatically expand macros.

  7. Choose Create stack to deploy the stack.

  8. Monitor the status of the stack. When the status is CREATE_COMPLETE, the Aerospike deployment is ready.

  9. To view the created resources, see the values displayed in the Outputs tab for the stack.

Test the deployment

After the AWS CloudFormation stack is complete, test the deployment by checking whether the instances were properly enrolled with your Aerospike project.

To validate the system and verify the system configuration, follow these steps:

  1. From the bastion host, use SSH to log in to one of the Aerospike instances created by Quick Start template. Use SSH key forwarding for security purposes. For more info on SSH key forwarding, see Using SSH agent forwarding.

    $ ssh ec2-user@<aerospike-instance>
  2. Verify cluster information using asadm command. More information, see Aerospike Admin (asadm). A two-node cluster output looks like this:

    $ asadm
    Seed:        [('127.0.0.1', 3000, None)]
    Config_file: /home/ec2-user/.aerospike/astools.conf, /etc/aerospike/astools.conf
    Aerospike Interactive Shell, version 2.0.1
    
    Found 2 nodes
    Online:  10.0.3.128:3000, 10.0.35.3:3000
    
    Admin> summary
    Cluster  (Migrations in Progress)
    =================================
    
       1.   Server Version     :  E-5.5.0.4
       2.   OS Version         :  Amazon Linux 2 (4.14.231-173.361.amzn2.x86_64)
       3.   Cluster Size       :  2
       4.   Devices            :  Total 0, per-node 0
       5.   Memory             :  Total 16.000 GB, 0.00% used (0.000 B), 100.00% available (16.000 GB)
       6.   Disk               :  Total 0.000 B, 0.00% used (0.000 B), 0.00% available contiguous space (0.000 B)
       7.   Usage (Unique Data):  None
       8.   Active Namespaces  :  0 of 2
       9.   Features           :
    
    
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Namespaces~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Namespace|~~~Devices~~~~|~~~~~~~~Memory~~~~~~~|~~~~~~~~~Disk~~~~~~~~|Replication| Master|~~~~~~Usage~~~~~~~
             |Total|Per-Node|   Total|Used%|Avail%|   Total|Used%|Avail%|    Factors|Objects|~~(Unique-Data)~~~
             |     |        |        |     |      |        |     |      |           |       |In-Memory| On-Disk
    bar      |    0|       0|8.000 GB|    0|   100|0.000 B |    0|     0|          2|0.000  | 0.000 B |0.000 B
    test     |    0|       0|8.000 GB|    0|   100|0.000 B |    0|     0|          2|0.000  | 0.000 B |0.000 B
    Number of rows: 2
  3. Insert record using aql. The following commands insert a record in test namespace. Replace foo with the set name and bar with the bin name.

    $ aql
    Seed:         127.0.0.1
    User:         None
    Config File:  /etc/aerospike/astools.conf /home/ec2-user/.aerospike/astools.conf
    Aerospike Query Client
    Version 5.0.1
    C Client Version 4.6.17
    Copyright 2012-2020 Aerospike. All rights reserved.
    
    aql> insert into test.foo (PK, bar) values (123, 'you did it!')
    OK, 1 record affected.
    
    aql> select * from test.foo
    +---------------+
    | bar           |
    +---------------+
    | "you did it!" |
    +---------------+
    1 row in set (0.036 secs)
    
    OK

For more information on testing, see Benchmarks. With the benchmark application, you can exercise and demo load on the new Aerospike cluster.

Best practices for using Aerospike on AWS

Follow these best practices: Aerospike on Amazon EC2 - Recommendations.

Also set up a backup plan your Aerospike data. For details, see Backup and Recovery in AWS.

Security

When you run Aerospike in production, review and ensure that your security best practices are understood and followed. You’ll find some recommended security best practices in Aerospike on Amazon EC2 - Recommendations.

Other useful information

After your deployment is up and ready, read and understand the following sections of the Aerospike documentation. Use the navigation panel to open each subsection within these main sections.

For information on the architecture and system, see the Aerospike Architecture Overview and System Overview

For information on monitoring your stack, see Overview to the Aerospike Monitoring Stack.

For information on querying your database, see Query.

For information on setting up and using connectors to stream data into your new cluster, see Overview of Aerospike Connect.

FAQ

Q. I encountered a CREATE_FAILED error when I launched the Quick Start.

A. If AWS CloudFormation fails to create the stack, relaunch the template with Rollback on failure set to Disabled. This setting is under Advanced in the AWS CloudFormation console on the Configure stack options page. With this setting, the stack’s state is retained, and the instance keeps running so that you can troubleshoot the issue. (For Windows, look at the log files in %ProgramFiles%\Amazon\EC2ConfigService and C:\cfn\log.)

When you set Rollback on failure to Disabled, you continue to incur AWS charges for this stack. Delete the stack when you finish troubleshooting.

For more information, see Troubleshooting AWS CloudFormation.

Q. I encountered a size-limitation error when I deployed the AWS CloudFormation templates.

A. Launch the Quick Start templates from the links in this guide or from another S3 bucket. If you deploy the templates from a local copy on your computer or from a location other than an S3 bucket, you might encounter template-size limitations. For more information, see AWS CloudFormation quotas.

Q. I created a cluster of three machines, but they don’t seem to be clustering.

A. Most likely you did not get a production license. You can rerun the Quick Start ensuring that you apply your production license. If you don’t have a license, you can obtain one on the Get started with Aerospike page.

Customer responsibility

After you successfully deploy this Quick Start, confirm that your resources and services are updated and configured — including any required patches — to meet your security and other needs. For more information, see the AWS Shared Responsibility Model.

Parameter reference

Unless you are customizing the Quick Start templates for your own deployment projects, keep the default settings for the parameters labeled Quick Start S3 bucket name, Quick Start S3 bucket Region, and Quick Start S3 key prefix. Changing these parameter settings automatically updates code references to point to a new Quick Start location. For more information, see the AWS Quick Start Contributor’s Guide.

Parameters for deploying into an existing VPC

Table 1. VPC network configuration
Parameter label (name) Default value Description

EC2 key pair (KeyPairName)

Requires input

Name of the key pair to be used to connect to your EC2 instances by using SSH.

VPC ID (VPCID)

Requires input

ID of the VPC that you’re deploying this cluster into.

CIDR for the VPC (VPCCIDR)

10.0.0.0/16

VPC CIDR block in the format x.x.0.0/16.

Tenancy (Tenancy)

default

Tenancy of the Aerospike instances. Choose "dedicated" to change the host from shared (default).

NO_LABEL (AccessCIDR)

0.0.0.0/0

CIDR IP range permitted to access Aerospike. A value of 0.0.0.0/0 allows access from any IP address.

NO_LABEL (PublicSubnet1ID)

Blank string

ID of public subnet 1

NO_LABEL (PublicSubnet2ID)

Blank string

ID of public subnet 2

NO_LABEL (PrivateSubnet1ID)

Blank string

ID of private subnet 1

NO_LABEL (PrivateSubnet2ID)

Blank string

ID of private subnet 2

NO_LABEL (PrivateSubnet3ID)

Blank string

(Optional) ID of private subnet 3

Table 2. Aerospike configuration
Parameter label (name) Default value Description

Namespace file (NamespaceFile)

Blank string

(Optional) Location of your namespace-definition file. Must be publically downloadable. Appends to aerospike.conf.

Feature key file (FeatureKeyFile)

Blank string

Base64 encoding of the feature key file. This is the Aerospike key to use for this deployment. Keeping this blank works only for single node cluster.

Number of instances (NumberOfInstances)

1

Number of instances to provision for the Aerospike cluster.

Enable CloudWatch logging (EnableCloudWatch)

no

Choose "yes" to enable CloudWatch logging for the Aerospike cluster, which adds basic Aerospike metrics to Amazon CloudWatch. This incurs CloudWatch expenses.

Instance type (InstanceType)

m5d.xlarge

Type of EC2 instance to deploy for the Aerospike cluster.

EBS volume size (EBS)

50

Size of the EBS SSD volume in GB. The volume attaches under /dev/sdg. Limit of 16000. Enter 0 if you do not want to use EBS.

Table 3. Linux bastion configuration
Parameter label (name) Default value Description

Bastion AMI operating system (BastionAMIOS)

Amazon-Linux2-HVM

Linux distribution for the AMI to be used for the bastion instances.

Bastion instance type (BastionInstanceType)

t3.micro

Type of EC2 instance for the bastion hosts.

Number of bastion hosts (NumBastionHosts)

1

Number of bastion hosts to create.

Table 4. AWS Quick Start configuration
Parameter label (name) Default value Description

Quick Start S3 bucket name (QSS3BucketName)

aws-quickstart

Name of the S3 bucket for your copy of the Quick Start assets. Keep the default name unless you are customizing the template. Changing the name updates code references to point to a new Quick Start location. This name can include numbers, lowercase letters, uppercase letters, and hyphens, but do not start or end with a hyphen (-). See https://aws-quickstart.github.io/option1.html.

Quick Start S3 key prefix (QSS3KeyPrefix)

quickstart-aerospike/

S3 key prefix that is used to simulate a directory for your copy of the Quick Start assets. Keep the default prefix unless you are customizing the template. Changing this prefix updates code references to point to a new Quick Start location. This prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), and forward slashes (/). End with a forward slash. See https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html and https://aws-quickstart.github.io/option1.html.

Quick Start S3 bucket Region (QSS3BucketRegion)

us-east-1

AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. Keep the default Region unless you are customizing the template. Changing this Region updates code references to point to a new Quick Start location. When using your own bucket, specify the Region. See https://aws-quickstart.github.io/option1.html.

Parameters for deploying into a new VPC

Table 5. VPC network configuration
Parameter label (name) Default value Description

Availability Zones (AvailabilityZones)

Requires input

Availability Zones to use for the VPC subnets. At least two Availability Zones are required.

Number of Availability Zones (NumberOfAZs)

3

Number of Availability Zones to use in the VPC. This number must match the number of Availability Zones you chose for the AvailabilityZones parameter.

VPC CIDR (VPCCIDR)

10.0.0.0/16

CIDR block for the VPC.

Private subnet 1 CIDR (PrivateSubnet1CIDR)

10.0.0.0/19

CIDR block for private subnet 1 located in Availability Zone 1.

Private subnet 2 CIDR (PrivateSubnet2CIDR)

10.0.32.0/19

CIDR block for private subnet 2 located in Availability Zone 2.

Private subnet 3 CIDR (PrivateSubnet3CIDR)

10.0.64.0/19

CIDR block for private subnet 3 located in Availability Zone 3.

Public subnet 1 CIDR (PublicSubnet1CIDR)

10.0.128.0/20

CIDR block for public DMZ subnet 1 located in Availability Zone 1.

Public subnet 2 CIDR (PublicSubnet2CIDR)

10.0.144.0/20

CIDR block for public DMZ subnet 2 located in Availability Zone 2.

Public subnet 3 CIDR (PublicSubnet3CIDR)

10.0.160.0/20

CIDR block for public DMZ subnet 3 located in Availability Zone 3.

Allowed bastion external access CIDR (AccessCIDR)

0.0.0.0/0

CIDR IP range permitted to access Aerospike. A value of 0.0.0.0/0 allows access from any IP address.

Tenancy (Tenancy)

default

Tenancy of the Aerospike instances. Choose "dedicated" to change the host from shared (default).

Table 6. Aerospike configuration
Parameter label (name) Default value Description

EC2 key pair (KeyPairName)

Requires input

Name of the key pair to be used to connect to your EC2 instances by using SSH.

Number of instances (NumberOfInstances)

1

Number of instances to provision for the Aerospike cluster.

Tenancy (Tenancy)

default

Tenancy of the Aerospike instances. Choose "dedicated" to change the host from shared (default).

Enable CloudWatch logging (EnableCloudWatch)

no

Choose "yes" to enable CloudWatch logging for the Aerospike cluster, which adds basic Aerospike metrics to Amazon CloudWatch. This incurs CloudWatch expenses.

Instance type (InstanceType)

m5d.xlarge

Type of EC2 instance to deploy for the Aerospike cluster.

EBS volume size (EBS)

50

Size of the EBS SSD volume in GB. The volume attaches under /dev/sdg. Limit of 16000. Enter 0 if you do not want to use EBS.

Namespace file (NamespaceFile)

Blank string

(Optional) Location of your namespace-definition file. Must be publically downloadable. Appends to aerospike.conf.

Feature key file (FeatureKeyFile)

Blank string

Base64 encoding of the feature key file. This is the Aerospike key to use for this deployment. Keeping this blank works only for a single node cluster.

Table 7. Linux bastion configuration
Parameter label (name) Default value Description

Bastion AMI operating system (BastionAMIOS)

Amazon-Linux2-HVM

Linux distribution for the AMI to be used for the bastion instances.

Bastion instance type (BastionInstanceType)

t3.micro

Type of EC2 instance for the bastion hosts.

Number of bastion hosts (NumBastionHosts)

1

Number of bastion hosts to create.

Table 8. AWS Quick Start configuration
Parameter label (name) Default value Description

Quick Start S3 bucket name (QSS3BucketName)

aws-quickstart

Name of the S3 bucket for your copy of the Quick Start assets. Keep the default name unless you are customizing the template. Changing the name updates code references to point to a new Quick Start location. This name can include numbers, lowercase letters, uppercase letters, and hyphens, but do not start or end with a hyphen (-). See https://aws-quickstart.github.io/option1.html.

Quick Start S3 key prefix (QSS3KeyPrefix)

quickstart-aerospike/

S3 key prefix that is used to simulate a directory for your copy of the Quick Start assets. Keep the default prefix unless you are customizing the template. Changing this prefix updates code references to point to a new Quick Start location. This prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), and forward slashes (/). End with a forward slash. See https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html and https://aws-quickstart.github.io/option1.html.

Quick Start S3 bucket Region (QSS3BucketRegion)

us-east-1

AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. Keep the default Region unless you are customizing the template. Changing this Region updates code references to point to a new Quick Start location. When using your own bucket, specify the Region. See https://aws-quickstart.github.io/option1.html.

Send us feedback

To post feedback, submit feature ideas, or report bugs, use the Issues section of the GitHub repository for this Quick Start. To submit code, see the Quick Start Contributor’s Guide.

Quick Start reference deployments

GitHub repository

Visit our GitHub repository to download the templates and scripts for this Quick Start, to post your comments, and to share your customizations with others.


Notices

This document is provided for informational purposes only. It represents AWS’s current 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’s 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.