reference deployment

Modular architecture for Amazon Redshift

Deploy an Amazon Redshift data warehouse on the AWS Cloud for big data and analytics

This Quick Start automatically deploys a modular, highly available environment for Amazon Redshift on the Amazon Web Services (AWS) Cloud.

Amazon Redshift is a fast, fully managed data warehouse that makes it simple and cost-effective to analyze all your data using standard structured query language (SQL) and your existing business intelligence tools. It enables you to run complex analytic queries against petabytes of structured data, using sophisticated query optimization, columnar storage on high-performance local disks, and massively parallel query execution.   

Traditional data warehouses require significant time and resources to administer, especially for large datasets. In addition, the financial cost associated with building, maintaining, and growing self-managed, on-premises data warehouses is very high. Amazon Redshift not only significantly lowers the cost and operational overhead of a data warehouse but, with Redshift Spectrum, also makes it easy to analyze large amounts of data in its native format, without requiring you to load the data.

portworx logo

This Quick Start was developed by AWS.

AWS Service Catalog administrators can add this architecture to their own catalog.  

  •  What you'll build
  • Use this Quick Start to automatically set up the following Amazon Redshift environment on AWS:

    • A highly available virtual private cloud (VPC) architecture that spans two 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.*
      • 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 the public and private subnets.*
    • In a private subnet, an Amazon Redshift cluster and its components, such as a cluster subnet group, parameter group, workload management (WLM), and a security group that allows access to the VPC. This is the default behavior. However, you can also opt to create the cluster and its components in the public subnets, so that they are publicly accessible.
    • An Amazon Simple Storage Service (Amazon S3) bucket for audit logs.
    • A VPC endpoint for Amazon S3, so that Amazon Redshift and other AWS resources that are run in a private subnet can have controlled access to Amazon S3 buckets.
    • The Quick Start uses a key from AWS Key Management Service (AWS KMS) to enable encryption at rest for the Amazon Redshift cluster, and creates a default master key when no other key is defined. 
    • Amazon CloudWatch alarms to monitor the CPU on the bastion host, to monitor the CPU and disk space of the Amazon Redshift cluster, and to send an Amazon SNS notification, when the alarm is triggered.
    • An AWS Identity and Access Management (IAM) role that grants minimum permissions required to use Redshift Spectrum with Amazon S3, Amazon CloudWatch Logs, AWS Glue, and Amazon Athena.
    • An AWS Glue Catalog as a metadata store.

    *  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.

  •  How to deploy
  • To deploy the Amazon Redshift environment in your AWS account, follow the instructions in the deployment guide. The deployment process takes 10–15 minutes and includes these steps:

    1. If you don't already have an AWS account, sign up at, and sign in to your account.
    2. Launch the Quick Start, choosing from the following options:
    3. Test the deployment and confirm that the Amazon Redshift cluster and Linux bastion host are accepting connections.
    To customize your deployment, you can configure your VPC, bastion host, and database settings, and optionally set database tags.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on this solution.  

  •  Cost and licenses
  • 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 the Quick Start.

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

    Tip: After you deploy the Quick Start, we recommend that you enable the AWS Cost and Usage Report to track costs associated with the Quick Start. This report delivers billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. It provides cost estimates based on usage throughout each month, and finalizes the data at the end of the month. For more information about the report, see the AWS documentation.