Redshift can query S3 data lakes in other Regions, with traffic kept in your VPC!

Hello everyone, Shii-chan here! Here's good news for anyone doing data analytics!

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, Amazon Redshift now supports querying Amazon S3 data lake tables located in a different AWS Region.

Also, with enhanced VPC routing, data lake query traffic between Amazon S3 and Amazon Redshift stays within your own VPC. Both capabilities are powered by the integrated data lake query engine that runs directly on the compute of RG provisioned and Serverless clusters.

Why it matters

These features are aimed at enterprises with globally distributed data and at security-sensitive customers who need tight control over how their data travels.

What changes

• Query S3 data in another Region directly, without first copying or replicating it
• Easier global analytics and reporting consolidated across Regions
• Query data that must remain in a specific Region for residency requirements

Dive Deep

Because the query engine runs on your cluster's compute, data moving between S3 and Redshift flows entirely over your VPC when you use enhanced VPC routing, never over public networks. Regulated industries such as financial services, healthcare, and government benefit because it keeps queries within the network boundaries their compliance requires.

Note that cross-Region queries incur standard data transfer charges.

Both capabilities are available in all Regions where RG provisioned and Serverless clusters are available.

Wrap-up

• Redshift can query S3 data lake tables in other Regions
• Enhanced VPC routing keeps S3 traffic inside your VPC
• Cross-Region queries incur standard data transfer charges
• Available wherever RG provisioned and Serverless clusters are

This is for analysts with data across Regions and for regulated industries!