---
title: Amazon Redshift
description: Fully managed cloud data warehouse for running fast SQL analytics on petabyte-scale datasets.
url: https://www.factualminds.com/glossary/amazon-redshift/
publishDate: 2026-06-13
updateDate: 2026-06-13
---

# Amazon Redshift

> Fully managed cloud data warehouse for running fast SQL analytics on petabyte-scale datasets.

## Definition

Amazon **Redshift** is AWS's managed **columnar data warehouse** for analytic SQL at scale. Data is stored column-by-column with automatic compression; **massively parallel processing (MPP)** spreads query fragments across nodes coordinated by a leader. **Sort keys** and **distribution styles** (`KEY`, `ALL`, `EVEN`, `AUTO`) determine I/O pruning and join behavior — tuning matters more than in OLTP engines.

Deploy as **Redshift Serverless** (RPU-hours, auto pause) or **provisioned RA3** clusters with **Managed Storage** in S3 for separated compute/storage scaling. **Redshift Spectrum** queries external tables on S3 without loading data. **Zero-ETL integrations** from **DynamoDB** (and other sources) replicate operational data for analytics without custom CDC. **Streaming ingestion** from Kinesis or MSK lands near-real-time rows for dashboards without a batch landing zone.

## When to use it

- **BI and reporting** — complex aggregations, window functions, and joins across billions of rows.
- **Data lake queries** via Spectrum or native tables on **S3 Tables / Parquet** without duplicating entire datasets locally.
- Intermittent analytics teams that prefer **Serverless** over 24/7 clusters — pay when queries run.
- Operational analytics fed by **DynamoDB zero-ETL** when you need warehouse SQL on live app data.

## When not to use it

- Application **OLTP** — use RDS, Aurora, or DynamoDB; Redshift locks and MVCC behave poorly for high-frequency single-row updates.
- Low-volume monthly reports on modest data — **Athena** on S3 Tables may be cheaper without cluster baseline cost.
- Sub-second keyed lookups — Redshift is scan/aggregate optimized, not point-read optimized.

## Tips

- Set **`DISTKEY`** on large fact tables to the column most often joined — avoid `EVEN` on huge tables that always join on `customer_id`.
- Run **`ANALYZE`** after large loads; enable automatic analyze and vacuum unless you have a reason to micromanage.
- Use **Redshift Serverless** workgroup **base capacity** floors for predictable SLAs; let it burst RPUs for ad hoc spikes.
- **UNLOAD** cold historical partitions to S3 Parquet and query via Spectrum — keeps hot cluster storage lean.
- Connect BI through **QuickSight SPICE** or aggregate tables to shield Redshift from dashboard-driven query storms.

## Gotchas

- **Serious:** **Broadcasting huge dimension tables** because `DISTSTYLE ALL` was chosen lazily — memory errors and 100× slower joins follow.
- **Serious:** Using Redshift as the **system of record** for mutable app state — updates are soft-delete heavy; storage bloat and vacuum debt accumulate fast.
- **Regular:** **Sort key mismatch** with common `WHERE` clauses forces full column scans — zone maps never help.
- **Regular:** **Concurrency scaling** costs surprise teams during Black Friday — cap concurrent scaling clusters if budget-bound.
- **Regular:** **Zero-ETL lag** is not zero — dashboards need freshness SLAs and monitoring on replication delay, not assumption of instant sync.

## Official references

- [Redshift distribution styles](https://docs.aws.amazon.com/redshift/latest/dg/t_Distributing_data.html) — KEY, ALL, EVEN, AUTO guidance.
- [Zero-ETL integrations](https://docs.aws.amazon.com/redshift/latest/mgmt/zero-etl-using.html) — supported sources and limits.

## Related FactualMinds content

- [AWS Data Analytics Services](/services/aws-data-analytics/)
- [Amazon DynamoDB](/glossary/amazon-dynamodb/) — zero-ETL source
- [S3 Tables](/glossary/s3-tables/) — lakehouse table format
- [FinOps Consulting](/services/finops-consulting/)
- [AWS Cloud Migration](/services/aws-migration/)

## Related AWS Services

- aws-data-analytics
- finops-consulting

## Related Posts

- aws-well-architected-framework-6-pillars-explained

---

*Source: https://www.factualminds.com/glossary/amazon-redshift/*