A script downloads data, transforms it, and publishes the result.
A failed intermediate command must prevent publication rather than make the script look successful.
Which setting is most appropriate?
Enable pipefail and inspect the resulting exit status so a failed pipeline stage propagates to the script.
Detailed explanation
A failure in any pipeline component can then affect the pipeline's status and stop publication.
A failure in any pipeline component can then affect the pipeline's status and stop publication.
Object-retention rules do not change Bash exit-status behavior.
Object-retention rules do not change Bash exit-status behavior.
CloudTrail records AWS API calls and does not control a local shell's status.
CloudTrail records AWS API calls and does not control a local shell's status.
An intermediate transformation failure could be treated as success and publish bad data.
An intermediate transformation failure could be treated as success and publish bad data.
Check official documentation
Compare the following points with the official documentation.
Bashのpipefail、PIPESTATUS、set -eの公式マニュアルを確認する。
What to confirm
パイプラインの終了ステータスと、AWS監視・保存設定の違いを説明できる。
Key points
- Bash
- pipefail
- Exit status
- Error propagation
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Error propagation
Shell, ETL, and orchestration layers must all receive an accurate failure status.
set -e caveat
Conditional commands and expected failures need explicit handling when automatic exit is enabled.