A large CSV object is stored in S3.
Analyze only selected columns without downloading the entire object each time.
Which feature is most appropriate?
Use S3 Select to filter rows and columns on the S3 side and reduce the amount of data transferred.
Detailed explanation
An archive-class transition is not a low-latency query optimization.
An archive-class transition is not a low-latency query optimization.
S3 Select filters object content on the service side and returns only the required data.
S3 Select filters object content on the service side and returns only the required data.
DNS records do not query the contents of an object.
DNS records do not query the contents of an object.
This transfers and processes unnecessary data, increasing bandwidth and compute use.
This transfers and processes unnecessary data, increasing bandwidth and compute use.
Check official documentation
Compare the following points with the official documentation.
Amazon S3 Selectの公式説明を確認する。
What to confirm
オブジェクト全体取得とサーバー側フィルタリングを比較できる。
Key points
- S3 Select
- CSV
- Server-side filtering
Notes
- Environment: AWS公式S3ドキュメントの確認
- Confirm current AWS service behavior in the official documentation.
Foundation review
Transfer reduction
Returning only selected rows and columns reduces network and client-processing work.
Query versus archive
An archive storage class addresses retention and cost, not interactive column selection.