Skip to main content
In this lesson we explore Amazon Redshift: what it is, why you would use it, and the core concepts to design and operate an analytical data warehouse on AWS. To understand Redshift, first review what a data warehouse is and how it differs from a traditional transactional database. What is a data warehouse?
  • Purpose-built to consolidate data from many sources—databases, logs, streaming systems, and cloud storage—into a unified, queryable repository.
  • Optimized for analytical workloads: complex queries, aggregations, reporting and historical analysis over large datasets.
  • Often includes ETL (extract, transform, load) capabilities to clean and transform data on ingestion, ensuring consistent data for analytics.
  • Designed to scale compute and storage independently and to retain historical data for trend analysis and BI.
Why a data warehouse vs. a transactional database
A slide titled "Why do we need Data Warehouse?" with an illustration of people working on a hexagonal data grid and stacked servers. To the right are colored boxes listing benefits like Data Integration, Optimized for Analytics, Historical Analysis, Data Transformation, Structured Data, Scalability, and Cost Efficiency.
What is Amazon Redshift? Amazon Redshift is a fully managed, petabyte-scale data warehouse service on AWS. It provides an enterprise-class, columnar relational engine optimized for analytics and integrates with a broad ecosystem of BI, reporting, and data tools. Redshift focuses on efficient storage, compression, and query performance for large analytical workloads. Core Redshift components
A labeled diagram titled "AWS Redshift – Components" showing Amazon Redshift serverless or provisioned architecture with a cloud-based serverless data warehouse and a cluster containing a leader node and multiple compute nodes. It also shows storage integrations (Redshift managed storage and Amazon S3) and a data-sharing cluster.
Compatibility and design considerations Redshift is based on PostgreSQL and supports many PostgreSQL client tools and SQL constructs. However, Redshift includes implementation differences and SQL extensions tailored for analytical processing. When migrating or developing for Redshift, focus on Redshift-specific performance practices:
  • Distribution keys and distribution styles to co-locate rows used together.
  • Sort keys to optimize range-restricted and equality queries.
  • COPY command optimizations for high-performance bulk loading from S3 or other sources.
  • Compression encodings and vacuum/ANALYZE patterns to maintain performance.
Redshift is PostgreSQL-compatible for many client tools and SQL constructs, but it has its own performance and distribution characteristics. Test queries and indexing/distribution strategies in Redshift rather than assuming PostgreSQL defaults.
Key Redshift features and capabilities
  • Columnar storage: Reads only needed columns to reduce I/O for analytics.
  • Massively parallel processing (MPP): Distributes query execution across compute nodes for large-scale performance.
  • Compression: Automatic sampling and recommended encodings minimize storage and I/O.
  • Elastic scaling: Add or remove nodes, change node types, or use Redshift Managed Storage (RA3/serverless) to decouple compute and storage scaling.
  • Integration and ingestion: Native COPY from Amazon S3, integrations with RDS, EMR, data pipelines, and compatibility with common BI tools.
  • SQL support: Standard SQL and Redshift-specific enhancements for analytics.
  • Security: AES-256 encryption at rest, SSL/TLS in transit, IAM integration, and fine-grained access controls, including column-level permissions.
  • High availability and backups: Automated/manual snapshots, replication options, and features to minimize downtime.
  • Workload management: Query queues, resource allocation, concurrency scaling, and tools to monitor and tune performance.
Common Redshift use cases
  • Forecasting and analytics: Financial, demand, and trend forecasting often tied into ML workflows.
  • Secure data sharing: Share curated datasets across accounts, organizations, and partners.
  • Business intelligence: Power dashboards and reports with QuickSight, Tableau, Looker, Power BI.
  • Centralized analytics: Consolidate logs and operational data to simplify analytics and multi-language access.
A presentation slide titled "Redshift – Use Cases" with four colorful panels. Each panel lists a use case: improve financial and demand forecasts; collaborate and share data; optimize business intelligence; and increase developer productivity.
Summary — what to remember about provisioned Redshift
  • Node types and roles: Leader node (query coordination and planning) and compute nodes (data storage and query execution).
  • Storage and performance: Columnar storage, MPP architecture, compression encodings, and local caches enable fast analytics at scale.
  • Security and availability: Encryption (AES-256), secure transport (SSL/TLS), fine-grained IAM/column access, and automated snapshots/backups.
A presentation slide titled "Summary Redshift Provisioned" with a brief overview of Amazon Redshift. It states Redshift is a fully managed, petabyte-scale cloud data warehouse and outlines node types (leader and compute nodes) and their roles.
Additional highlights and operational tips
  • Automatic sampling and compression help reduce storage costs and improve query performance without manual tuning.
  • Fine-grained access controls and IAM integration protect sensitive columns and datasets.
  • Automatic cluster scaling features (concurrency scaling, elastic resize, managed-storage autoscaling) provide headroom for query peaks and unpredictable workloads.
  • Use automated and manual snapshots for point-in-time recovery and compliance-driven retention.
A presentation slide titled "Summary Redshift Provisioned" with a turquoise left panel and three numbered highlights on the right. The points note AES-256/SSL encryption, fine-grain column-level access controls, and automatic cluster capacity scaling.
References and further reading

Watch Video