aws AWS Big Data Blog ·

AWS Redshift: Upgrade DC2 clusters to Graviton-powered RG instances

blogdataawsaws-redshift
announcement

Amazon Redshift is detailing the upgrade path from older DC2 clusters to new RG instances powered by AWS Graviton processors. This upgrade offers significant advantages including managed storage, data sharing, zero-ETL integrations, and a built-in data lake engine for querying Iceberg and Parquet tables. RG instances provide better performance and lower cost compared to RA3, making them the recommended migration target for DC2 customers facing storage limitations or seeking enhanced capabilities. The post outlines node mapping guidance, available upgrade methods like elastic resize, and necessary prerequisites for a smooth transition.

  • Integrated data lake engine in RG instances
  • Benefits of upgrading from DC2 to RG instances
  • RG instance details and node mapping guidance
  • Prerequisites and upgrade methods for DC2 to RG migration
Features (1)
  • Integrated data lake engine in RG instances

    RG instances feature a built-in data lake engine that processes queries directly on cluster compute nodes, eliminating the per-TB scanning cost associated with Amazon Redshift Spectrum on DC2 clusters. This integrated engine natively supports Apache Iceberg queries and automatically collects statistics using JIT-Analyze, without requiring Spectrum or manual collection, consolidating warehouse and data lake workloads.

Notes (3)
  • Benefits of upgrading from DC2 to RG instances

    Upgrading to RG instances provides access to managed storage that decouples storage from compute, allowing independent scaling of data volume and node count. RG instances run on AWS Graviton processors, offering higher throughput and lower cost per vCPU compared to RA3. They also include enhanced features like data sharing, zero-ETL integrations, streaming ingestion, concurrency scaling for writes, cross-AZ cluster relocation, multi-AZ deployments, and faster query compilation.

  • RG instance details and node mapping guidance

    The post provides a table detailing RG instance configurations (rg.large, rg.xlarge, rg.4xlarge, rg.12xlarge) with their respective vCPUs and memory. It also includes a node mapping table to guide users in determining the recommended starting RG node configuration based on their current DC2 node type and count, emphasizing that extra nodes might be needed based on specific workload requirements.

  • Prerequisites and upgrade methods for DC2 to RG migration

    Before upgrading, users must ensure snapshot availability for their DC2 cluster, verify network configuration (VPC, subnet groups, security groups), and confirm the cluster is running a supported Amazon Redshift version. Three upgrade methods are available: Elastic resize (recommended for speed and minimal downtime), Classic resize, and another method depending on operational constraints like write access during migration and elastic resize support.

Read the original announcement →

https://aws.amazon.com/blogs/big-data/upgrade-amazon-redshift-dc2-clusters-to-the-new-amazon-redshift-rg/

Related releases