Recent aggregates are in Redshift and raw history remains in S3.
Join both sources with SQL without loading every historical file into Redshift.
Which configuration is most appropriate?
Use Redshift Spectrum and an external schema to query S3 external tables alongside Redshift tables.
Detailed explanation
Spectrum lets Redshift SQL read S3 external tables and join them with internal tables.
Spectrum lets Redshift SQL read S3 external tables and join them with internal tables.
Archive objects require restoration and are not an immediate SQL join source.
Archive objects require restoration and are not an immediate SQL join source.
Access Analyzer evaluates permissions and does not execute external-table SQL.
Access Analyzer evaluates permissions and does not execute external-table SQL.
Streams deliver item-change events and do not join Redshift tables with S3 data.
Streams deliver item-change events and do not join Redshift tables with S3 data.
Check official documentation
Compare the following points with the official documentation.
Redshift Spectrum、外部スキーマ、Glue Data Catalog、S3外部テーブルの公式説明を確認する。
What to confirm
外部テーブル分析と、アーカイブ復元・変更イベント・権限分析の違いを説明できる。
Key points
- Redshift Spectrum
- External schema
- S3 table
- External data
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Hot and cold data
Keep frequently queried data inside the warehouse and historical raw data in economical storage.
External query cost
S3 format, partition pruning, and data scanned influence Spectrum performance and cost.