QingCloud KubeSphere on the AWS Cloud
Quick Start Reference Deployment
November 2020
Xiaosi Zhou, Pengfei Zhou, Shuang Yu, and Sherlock Xu, QingCloud
Troy Ameigh, 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 QingCloud 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 Quick Start reference guide provides step-by-step instructions for deploying KubeSphere with Amazon EKS on the AWS Cloud. It is for AWS Identity and Access Management (IAM) users of Amazon EKS who are looking for a web console to manage daily Kubernetes workloads.
| Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start. |
QingCloud KubeSphere on AWS
KubeSphere is a multitenant, enterprise-grade, container platform with full-stack automation, operation, and DevOps workflows. It provides developer-friendly web interfaces, which can help enterprises build more robust and feature-rich platforms that includes the most common functionalities needed for enterprise Kubernetes workloads.
This Quick Start is powered by AWS CloudFormation templates that help IAM users automatically provision Amazon EKS environments on a new or existing VPC. This gives IAM users the ability to manage Amazon EKS clusters through the KubeSphere console, which provides the following capabilities:
-
Kubernetes resource management
-
Multicloud and multicluster management
-
DevOps (continuous integration and continuous delivery based on Jenkins)
-
Application lifecycle management
-
An app store
-
Rich observability for monitoring, logging, auditing, alerting, and notifying
-
A service mesh for distributed microservices (based on Istio and Jaeger)
-
Enterprise multitenancy
-
Storage, network, and registry management
-
Automatic scaling
-
Role-based access control
-
Kubernetes Network Policies
Cost
You are responsible for the cost of the AWS services 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
KubeSphere is open source and doesn’t require a license. It is free for all Amazon EKS users. For any KubeSphere issues, see the KubeSphere GitHub community and raise an issue. Alternatively, contact KubeSphere through the Slack community or its mailing list.
For KubeSphere users with production environments who want technical support, you must have a support subscription. To get started, contact your account executive or fill out KubeSphere’s Commercial Support form.
You are responsible for the cost of the AWS infrastructure, storage, and data services used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.
QingCloud is an AWS Partner, and is the KubeSphere project sponsor and maintainer, which means they can provide technical KubeSphere support.
Architecture
Deploying this Quick Start for a new virtual private cloud (VPC) with default parameters builds the following KubeSphere environment in the AWS Cloud.
As shown in figure 1, the Quick Start sets up the following:
-
A highly available VPC architecture that spans three Availability Zones. The VPC is 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.*
-
Linux bastion hosts in an Auto Scaling group to allow inbound Secure Shell (SSH) access to administer the KubeSphere platform and Amazon EKS environment.*
-
-
In the private subnets:
-
Amazon Elastic Compute Cloud (Amazon EC2) instances in an Auto Scaling group. KubeSphere core components and your applications run on worker nodes.
-
-
An Amazon EKS cluster, which provides the Kubernetes control plane.
-
AWS IAM roles to help you securely control access to AWS resources.
-
Elastic Load Balancing to distribute incoming application or network traffic across multiple targets.
*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, visit Getting Started with AWS and Training and Certification. These sites provide materials for learning how to design, deploy, and operate your infrastructure and applications on the AWS Cloud.
This Quick Start assumes that you have working knowledge of Docker and Kubernetes.
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, your account must be configured as specified in the following table. Otherwise, deployment might fail.
Resource quotas
If necessary, request service quota increases for the following resources. You might request quota increases to avoid exceeding the default limits for any resources that are shared across multiple deployments. 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 |
|---|---|
VPCs |
1 |
Elastic IP addresses |
4 |
AWS Identity and Access Management (IAM) security groups |
3 |
IAM roles |
21 |
Auto Scaling groups |
2 |
Application Load Balancers |
1 |
Network Load Balancers |
2 |
NAT gateway |
3 |
t2.medium instances |
3 |
t2.micro instances |
1 |
Supported Regions
This deployment includes Amazon EKS, which may not be supported in all AWS Regions. For more information, see Amazon Elastic Kubernetes Service endpoints and quotas.
| Certain Regions are available on an opt-in basis. See Managing AWS Regions. |
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.
Deployment options
This Quick Start provides two deployment options:
-
Deploy KubeSphere into a new VPC (end-to-end deployment). 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 KubeSphere into this new VPC.
-
Deploy KubeSphere into an existing VPC. This option provisions Amazon EKS and KubeSphere 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 KubeSphere settings, as discussed later in this guide.
Deployment steps
Sign in to your AWS account
-
Sign in to your AWS account at https://aws.amazon.com with an IAM user role that has the necessary permissions. For more information, see Planning the deployment, earlier in this guide.
-
Ensure that your AWS account is configured correctly, as discussed in the Technical requirements section.
Launch the Quick Start
| You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using this Quick Start. For full details, see the pricing pages for each AWS service used by this Quick Start. Prices are subject to change. |
-
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 KubeSphere into a new VPC on AWS into CN-North-1 Region |
|
Deploy KubeSphere into a existing VPC on AWS into CN-Northwest-1 Region |
|
If you deploy KubeSphere into an existing VPC, ensure that your VPC has three 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. To allow the instances to download packages and software without exposing them to the internet, the subnets require NAT gateways in their route tables. Also, ensure that the domain name in the DHCP options is configured, as explained in the DHCP options sets. When you launch the Quick Start, provide your VPC settings. |
Each deployment takes about 40–50 minutes to complete.
-
Check the AWS Region that’s displayed in the upper-right corner of the navigation bar, and change it if necessary. This is where the network infrastructure for KubeSphere is built. The template launches in the us-east-1 Region by default.
| This deployment includes Amazon EFS, which isn’t currently supported in all AWS Regions. For a current list of supported Regions, see Amazon Elastic File System endpoints and quotas. |
-
On the Create stack page, keep the default setting for the template, and then choose Next.
-
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.
-
On the Configure stack options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you’re finished, choose Next.
-
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.
-
Choose Create stack to deploy the stack.
-
Monitor the status of the stack. When the status is CREATE_COMPLETE, the KubeSphere deployment is ready.
-
Use the values displayed in the Outputs tab for the stack, as shown in KubeSphere outputs after successful deployment, to view the created resources.
Test the deployment
-
Log in to the bastion host using your configured key pair and the user name
ec2-user. You can get the IP address of the bastion host from the Outputs tab of the AWS CloudFormation console.ssh -i "~/.ssh/cap.pem" ec2-user@12.23.34.45
-
Verify that the client software was installed through the bastion host:
-
Kubectl version:
$ kubectl version
-
Helm version:
$ helm version
-
AWS CLI version:
$ aws -version
-
Cf version:
$ cf -version
-
Git version
$ git version
-
-
Verify the health of the Amazon EKS cluster through the bastion host. Use the installed
kubectlandhelmcommands to verify access to the environment and the running state of the cluster and packages. The installation was successful if you see the welcome-information outputs in the log.$ kubectl cluster-info
$ kubectl get nodes
$ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='\{.items[0].metadata.name}') -f
-
Retrieve the generated URL of the KubeSphere console from the outputs list. Access it in your browser, and log in to the KubeSphere console using the administrator account and password defined by
KubeSphereConsolePassword.
Best practices for using KubeSphere on AWS
As mentioned in the table KubeSphere System and Pluggable Configuration of Step3, KubeSphere has 11 pluggable components, which can be enabled individually. If you don’t enable them, KubeSphere starts with a minimal installation by default. Ensure that you have the necessary CPU and memory requirements in your cluster. For more information, see the KubeSphere Overview.
The optimal configuration for running KubeSphere Container Platform on an Amazon EKS cluster requires a minimum of one worker node that has at least 16 GiB RAM and 4 CPUs. We recommended that you enable these pluggable components to discover the full-stack features and capabilities provided by KubeSphere. If you already have a minimal KubeSphere setup, you can still enable the pluggable components by editing the cluster’s configuration as follows:
Use an administrative account to access Cluster Management. Choose the EKS cluster, and select CRDs from the left-hand menu. Search for ClusterConfiguration.
Choose the ClusterConfiguration resource page. Choose ··· from the list, and select Edit YAML.
Scroll down to the spec section, and change the pluggable components from false to true for the features you want. Finally, choose Update to save your changes. The installation automatically starts at the backend.
Open the Web kubectl from Toolbox (bottom right), and inspect the installation logs:
$ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='\{.items[0].metadata.name}') -f
When you see welcome information in the output logs, the pluggable components are ready to use.
Security
Set up the TLS: This Quick Start automatically sets up Elastic Load Balancing (ELB) to support the critical services of a KubeSphere container platform cluster. We recommend that you set up the TLS for you Network Load Balancer to establish a secure connection between the client and server. This helps to ensure that all data passed between the client and your load balancer is private, for more information, see TLS listeners for your Network Load Balancer.
Keep the secret private: KubeSphere supports multicluster management in a unified control plane. Save the secrets used to connect to the external cluster. For more information, see Direct Connection.
Create proper multitenant management policies: KubeSphere is a multitenant platform. Multitenancy in KubeSphere refers to one or more clusters that are shared between tenants. Ensure that you set the proper roles, permissions, and projects for tenants. For more information, see Create Workspace, Project, Account and Role.
Create proper network policies: KubeSphere allows administrators to set network policies for different projects (namespaces) and workspaces. To control network communication between pods in each cluster’s projects and workspaces, create network policies based on your tenants' requirements. We recommend that you block traffic among projects that host different tenant applications. Also, deny all incoming traffic to avoid pods from one project mistakenly sending traffic to another project’s services or databases.
Get started with KubeSphere
When you finish deploying this Quick Start, refer to the
https://kubesphere.io/docs/quick-start/create-workspace-and-project/[KubeSphere Getting Started Guide^]. It has hands-on labs and tutorials that can help you get started with KubeSphere.
Central control plane for multicloud and multicluster management
If you want to build a hybrid cloud for multicloud and multicluster management, enable Kubernetes federation to set up a central control plane using KubeSphere. KubeSphere supports application distribution across multiple clusters and cloud providers. It also provides disaster recovery and cross-cluster observability. For more information, see How to enable a multicluster feature.
Additional resources
AWS resources
AWS services
KubeSphere
FAQ
Q. I encountered a CREATE_FAILED error when I launched the Quick Start.
A. If AWS CloudFormation fails to create the stack, we recommend that you relaunch the template with Rollback on failure set to Disabled. (This setting is under Advanced in the AWS CloudFormation console, Options page.) With this setting, the stack’s state is retained, and the instance remains running so 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 the stack. Ensure that you 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. We recommend that you 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 the AWS CloudFormation quotas.
Q. How to change the language.
A. Choose the user name from the top-right corner of the console, and choose User settings for language options. KubeSphere console supports English, Spanish, simplified Chinese, and traditional Chinese.
Q. Deploying second cluster into a Region causes the "Regional Resource" stack to fail.
A. When deploying a stack into a Region where you already deployed a cluster using the Quick Start. You need to set "PerRegionSharedResources" to "No", this stack once deployed will be used by all subsequent deployments in that Region.
Q. Deploying second cluster into an Account causes the "Account Resource" stack to fail.
A. When deploying a stack into an Account where you already deployed a cluster using the Quick Start. You need to set "PerAccountSharedResources" to "No", this stack once deployed will be used by all subsequent deployments in that Account.
Parameter reference
Unless you are customizing the Quick Start templates for your own deployment projects, we recommend that you 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.
|
Launch into new VPC
| Parameter label (name) | Default value | Description |
|---|---|---|
Number of Availability Zones
( |
|
Number of Availability Zones to use in the VPC. This must match your selections in the list for the "AvailabilityZones" parameter. |
Availability Zones
( |
|
List of Availability Zones to use for the VPC subnets. Two or three Availability Zones are used for this deployment, and each one should match the "NumberOfAZs" parameter. |
VPC CIDR
( |
|
CIDR block for the VPC |
Private subnet 1 CIDR
( |
|
CIDR block for private subnet 1, located in Availability Zone 1. |
Private subnet 2 CIDR
( |
|
CIDR block for private subnet 2, located in Availability Zone 2. |
Private subnet 3 CIDR
( |
|
CIDR block for private subnet 3, located in Availability Zone 3. |
Public subnet 1 CIDR
( |
|
CIDR block for the public DMZ subnet 1, located in Availability Zone 1. |
Public subnet 2 CIDR
( |
|
CIDR block for the public DMZ subnet 2, located in Availability Zone 2. |
Public subnet 3 CIDR
( |
|
CIDR block for the public DMZ subnet 3, located in Availability Zone 3. |
Allowed external access CIDR
( |
|
CIDR IP range that is permitted to access the instances. We recommend that you set this value to a trusted IP range. |
| Parameter label (name) | Default value | Description |
|---|---|---|
Provision bastion host
( |
|
Skip creating a bastion host by choosing "Disabled." |
| Parameter label (name) | Default value | Description |
|---|---|---|
Node instance type
( |
|
Type of EC2 instance for the nodes. |
Number of nodes
( |
|
Number of Amazon EKS node instances. The default is one for each Availability Zone. |
| Parameter label (name) | Default value | Description |
|---|---|---|
Quick Start S3 bucket name
( |
|
S3 bucket name for the Quick Start assets. This string can include numbers, lowercase letters, uppercase letters, and hyphens (-). It cannot start or end with a hyphen (-). |
Quick Start S3 key prefix
( |
|
The S3 key prefix for the Quick Start assets. Quick Start key prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), periods (.) and forward slashes (/). |
Quick Start S3 bucket Region
( |
|
AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. If you use your own bucket, you must specify this value. |
ConfigSetName
( |
|
Name for the configuration set. This applies if you launched the advanced configuration stack. The name must match the "ConfigSetName" parameter. |
Per-account shared resources
( |
|
Choose "No" if you already deployed another EKS Quick Start stack in this AWS account. |
Per region shared resources
( |
|
Choose "No" if you already deployed another EKS Quick Start stack in this Region. |
| Parameter label (name) | Default value | Description |
|---|---|---|
KubeSphereConsolePassword
( |
|
Password of KubeSphere console must be at least 8 characters, including numbers, uppercase letters, lowercase letters, and special characters (!@#$%^&*?). |
Openpitrix
( |
|
(Optional) An application store to package, deploy, and manage cloud-native applications in a multicloud environment. |
Devops
( |
|
(Optional) Provides out-of-the-box CI/CD, based on Jenkins, and offers automated workflow tools including binary-to-image (B2I) and source-to-image (S2I). |
Servicemesh
( |
|
(Optional) Provides resource-level management, observability, and tracing for distributed microservice applications. It also provides visualization for traffic topology. |
Notification
( |
|
(Optional) Sends alert messages to responders via email, Slack, WeChat, etc. |
Alerting
( |
|
(Optional) Users can customize alerting policies to send messages with different time intervals and alerting levels. |
Auditing
( |
|
(Optional) DevOps console for developers to automatically create, build, test, and release applications. |
Logging
( |
|
(Optional) Flexible logging functions are provided for query, collection, and management. Additional log collectors can be added, such as Amazon Elasticsearch, Kafka, and Fluentd. |
Events
( |
|
(Optional) Events that happen inside a cluster are recorded, such as container running status, image pulling failures, and node scheduling activities. |
Multicluster
( |
|
(Optional) Users can create projects to run across clusters, which builds a container environment with rapid iterations and high availability. |
Networkpolicy
( |
|
(Optional) Network policy configuration allows for network isolation within a cluster, which means firewalls can be set up between pods. |
MetricsServer
( |
|
(Optional) Users can install "MetricsServer" to enable HPA (Horizontal Pod Autoscaler), which automatically scales the number of pods, deployments, or stateful sets based on observed CPU utilization. |
Launch into existing VPC
| Parameter label (name) | Default value | Description |
|---|---|---|
Number of Availability Zones
( |
|
Number of Availability Zones to use in the VPC. This must match your selections in the list for the "AvailabilityZones" parameter. |
Availability Zones
( |
|
List of Availability Zones to use for the VPC subnets. Two or three Availability Zones are used for this deployment, and each one should match the "NumberOfAZs" parameter. |
VPC ID
( |
|
ID of your existing VPC (e.g., vpc-0343606e) |
VPC CIDR
( |
|
CIDR block for the VPC |
Private subnet 1 ID
( |
|
ID of the private subnet in Availability Zone 1 of your existing VPC (e.g., subnet-fe9a8b32). |
Private subnet 2 ID
( |
|
ID of the private subnet in Availability Zone 2 of your existing VPC (e.g., subnet-be8b01ea). |
Private subnet 3 ID
( |
|
ID of the private subnet in Availability Zone 3 of your existing VPC (e.g., subnet-abd39039). |
Public subnet 1 ID
( |
|
ID of the public subnet in Availability Zone 1 of your existing VPC (e.g., subnet-a0246dcd). |
Public subnet 2 ID
( |
|
ID of the public subnet in Availability Zone 2 of your existing VPC (e.g., subnet-b1236eea). |
Public subnet 3 ID
( |
|
ID of the public subnet in Availability Zone 3 of your existing VPC (e.g., subnet-c3456aba). |
Allowed external access CIDR
( |
|
CIDR IP range that is permitted to access the instances. We recommend that you set this value to a trusted IP range. |
| Parameter label (name) | Default value | Description |
|---|---|---|
Provision bastion host
( |
|
Skip creating a bastion host by choosing "Disabled." |
| Parameter label (name) | Default value | Description |
|---|---|---|
Node instance type
( |
|
Type of EC2 instance for the nodes. |
Number of nodes
( |
|
Number of Amazon EKS node instances. The default is one for each Availability Zones. |
| Parameter label (name) | Default value | Description |
|---|---|---|
Quick Start S3 bucket name
( |
|
S3 bucket name for the Quick Start assets. This string can include numbers, lowercase letters, uppercase letters, and hyphens (-). It cannot start or end with a hyphen (-). |
Quick Start S3 key prefix
( |
|
S3 key prefix for the Quick Start assets. The Quick Start key prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), periods (.) and forward slashes (/). |
Quick Start S3 bucket region
( |
|
AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. If you use your own bucket, you must specify this value. |
ConfigSetName
( |
|
Name for the configuration set. This applies if you launched the advanced configuration stack. The name must match the "ConfigSetName" parameter. |
Per-account shared resources
( |
|
Choose "No" if you already deployed another EKS Quick Start stack in this AWS account. |
Per region shared resources
( |
|
Choose "No" if you already deployed another EKS Quick Start stack in this Region. |
| Parameter label (name) | Default value | Description |
|---|---|---|
KubeSphereConsolePassword
( |
|
Password of KubeSphere console must be at least 8 characters, including numbers, uppercase letters, lowercase letters, and special characters (!@#$%^&*?). |
Openpitrix
( |
|
(Optional) An application store to package, deploy, and manage cloud-native applications in a multicloud environment. |
Devops
( |
|
(Optional) Provides out-of-the-box CI/CD, based on Jenkins, and offers automated workflow tools including binary-to-image (B2I) and source-to-image (S2I). |
Servicemesh
( |
|
(Optional) Provides resource-level management, observability, and tracing for distributed microservice applications. It also provides visualization for traffic topology. |
Notification
( |
|
(Optional) Sends alert messages to responders via email, Slack, WeChat, etc. |
Alerting
( |
|
(Optional) Users can customize alerting policies to send messages with different time intervals and alerting levels. |
Auditing
( |
|
(Optional) DevOps console for developers to automatically create, build, test, and release applications. |
Logging
( |
|
(Optional) Flexible logging functions are provided for query, collection, and management. Additional log collectors can be added, such as Amazon Elasticsearch, Kafka and Fluentd. |
Events
( |
|
(Optional) Events that happen inside a cluster are recorded, such as container running status, image pulling failures, and node scheduling activities. |
Multicluster
( |
|
(Optional) Users can create projects to run across clusters, which builds a container environment with rapid iterations and high availability. |
Networkpolicy
( |
|
(Optional) Network policy configuration allows for network isolation within a cluster, which means firewalls can be set up between pods. |
MetricsServer
( |
|
(Optional) Users can install "MetricsServer" to enable HPA (Horizontal Pod Autoscaler), which automatically scales the number of pods, deployments, or stateful sets based on observed CPU utilization. |
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
See the AWS Quick Start home page.
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.