The same Glue job runs with several code versions.
Determine whether an abnormal result came from a code change and be able to reproduce or roll back the run.
Which monitoring and maintenance approach is most appropriate?
Record job, configuration, and input versions in structured logs and output metadata so runs can be compared and reproduced.
Detailed explanation
A timestamp cannot distinguish two code versions running in the same period.
A timestamp cannot distinguish two code versions running in the same period.
The API caller does not describe the job code or configuration version.
The API caller does not describe the job code or configuration version.
Removing historical versions prevents reproduction and weakens the audit trail.
Removing historical versions prevents reproduction and weakens the audit trail.
The execution ID can be linked to the exact code, settings, and manifest for comparison and rollback.
The execution ID can be linked to the exact code, settings, and manifest for comparison and rollback.
Check official documentation
Compare the following points with the official documentation.
AWS Glue job versioning、CloudWatch structured logs、data pipeline reproducibilityの公式説明を確認する。
What to confirm
実行時刻だけの監視と再現可能な版管理の違いを説明できる。
Key points
- Code version
- Input version
- Reproducibility
- Rollback
Notes
- Environment: AWS公式DEA-C01試験ガイドと各サービスの公式ドキュメントの確認
- Confirm current AWS service behavior in the official DEA-C01 documentation.
Foundation review
Correlation metadata
Combine execution ID, commit, configuration hash, and input manifest in one run record.
Safe maintenance
Pin versions for replay and rehearse a staged rollback procedure.