Explains the minimal hardware, network, and configuration prerequisites for launching and operating an Amazon Redshift cluster.
Amazon Redshift offers dc2.large and ra3.xlplus as the entry node types. A single dc2.large node (2 vCPU, 15 GiB RAM, 160 GB SSD) is the lowest-cost, production-supported configuration. For RA3, one ra3.xlplus node (4 vCPU, 32 GiB RAM) is the minimum.
Both node families support a one-node cluster.Multi-node clusters start at two nodes, but a single-node dc2.large is fully functional for light workloads or development.
Estimate raw data size and apply 3× compression. A Orders + OrderItems dataset totaling 500 GB raw usually compresses to ~170 GB, fitting in a dc2.large node. For larger catalogs, scale nodes or switch to RA3 with managed storage.
Open TCP 5439 from client IPs or VPCs.Attach the cluster to private subnets with a NAT gateway for internet traffic. Enable AWS IAM or database-native users for authentication, enforce SSL, and rotate passwords regularly.
Run system catalog queries after load. Compare total table size to available capacity and check slot concurrency. Example below shows a quick size check for typical ecommerce tables.
Use elastic resize
to add nodes or switch node types.Downtime is minutes, and data redistributes automatically. Always snapshot before resizing.
.
Yes, but it lacks high availability. For fault tolerance, use at least two nodes or Redshift Serverless with multi-AZ.
RA3 separates compute and storage. You pay for managed storage used, so start with one ra3.xlplus node and let storage scale automatically.
Absolutely. Use the Redshift console or CLI to modify-cluster
and switch node type. Elastic resize keeps the cluster online during the move.