All Services

Analytics

Amazon Redshift

Amazon Redshift is a managed massively parallel, columnar data warehouse available as provisioned clusters or serverless workgroups for SQL analytics across warehouse and supported lake data.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Redshift.

Amazon Redshift pricing and cost programs

Pricing model: Managed data warehouse usage

On-Demand
Available
Reserved Instances or reserved capacity
Available
Savings Plans
Service-specific
Spot
Not applicable

Billing dimensions: Node or RPU time · Managed storage · Spectrum scans · Data transfer

Programs and modes: On-Demand Nodes · Reserved Instances · Redshift Serverless · Concurrency Scaling

Reserved Instances apply to eligible provisioned nodes; Serverless is billed in RPUs.

Free Tier: Service-specific — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Redshift?

  • Runs large analytical scans, joins, and aggregations using columnar storage and massively parallel processing instead of scaling a transactional database for warehouse queries.
  • Supports managed provisioned capacity or serverless workgroups, automated backups, workload management, concurrency features, data sharing, Spectrum, and integrations with AWS data services.
  • Provides SQL access for BI and analytics with encryption, VPC controls, IAM integration, database permissions, row or column controls, audit logging, and monitoring.

How to implement Amazon Redshift

  1. Run a representative proof of concept, choose Serverless or Provisioned from workload isolation and control needs, and model data volume, ingest windows, concurrency, query shapes, recovery, and cost constraints.
  2. Create private encrypted namespaces and workgroups or clusters, configure database identities and least-privilege roles, then design schemas with appropriate types, compression, distribution, sort, and automatic table optimization options.
  3. Load data in parallel with COPY or managed integrations, organize workload queues and query monitoring, enable logs and alarms, and test concurrency, skew, spill, pause or resize behavior, snapshots, restore, and regional recovery.

Amazon Redshift best practices

  • Design for Redshift's MPP and columnar architecture rather than copying transactional schemas unchanged; use compression, set-based operations, selective columns, parallel loads, and representative proof-of-concept data.
  • Use automatic table optimization and Advisor where appropriate, monitor workload queues, skew, disk, spill, long queries and locks, keep statistics current, and tune SQL before adding capacity.
  • Keep endpoints private where possible, require encrypted connections, separate IAM and database privileges, protect snapshots, audit access, apply row or column security deliberately, and test restore plus credential rotation.

Amazon Redshift use cases and server impact

  • Enterprise BI and dimensional warehouses
  • High-concurrency analytical SQL
  • Federated warehouse and S3 lake analytics

Replaces data-warehouse database hosts and much backup or scaling infrastructure, while dimensional modeling, ingestion quality, SQL tuning, workload governance, and recovery objectives remain customer responsibilities.

Official implementation resources

Commonly paired AWS services

Planning guides that use Amazon Redshift