Join existing Redshift analytics with current operational rows in RDS for PostgreSQL.
Avoid a nightly copy ETL and run ad hoc analysis that reflects updates in RDS.
Which design or service is most appropriate?
A Redshift federated query can query an external RDS PostgreSQL database and combine current rows without a copy step.
Detailed explanation
Redshift can query the external RDS source and join current rows without waiting for a copy.
Redshift can query the external RDS source and join current rows without waiting for a copy.
It adds a replication and schema-conversion pipeline instead of querying the current RDS source.
It adds a replication and schema-conversion pipeline instead of querying the current RDS source.
This fails the freshness and automation requirements and creates unnecessary copies.
This fails the freshness and automation requirements and creates unnecessary copies.
Spectrum targets external data in S3; it is not the direct connection method for RDS tables.
Spectrum targets external data in S3; it is not the direct connection method for RDS tables.
Check official documentation
Compare the following points with the official documentation.
Amazon Redshift federated query、Redshift Spectrum、外部スキーマの公式ドキュメントを確認する。
What to confirm
RDSへのFederated queryとS3向けSpectrumの適用範囲を区別できる。
Key points
- Federated query
- Redshift Spectrum
- External schema
- Data freshness
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm the relevant DEA-C01 Skill and current AWS service documentation.
Foundation review
External source
Choose the feature that matches the database or object-store location.
Copy tradeoff
Avoid recurring ETL when direct reads meet latency, load, and security requirements.