Blog
- Home /
- Blog
Hybrid Lab-to-Cloud: a Go-Live and Recovery Checklist
The pilot worked for one instrument on a quiet Tuesday. Cutover week added three instruments, a VPN blip, and a KMS key rotation—and the only recovery plan was “call the person who built the agent.”
Read MoreObserving and Debugging Hybrid Data Transfers
Slack said “files aren’t in S3.” The agent host said “fine.” CloudWatch had three log groups and no shared id. Twenty minutes later someone found the run under a different instrument prefix—and a completion marker that never wrote.
Read MoreIdempotent Pollers, Retries, and Quarantine Paths
The agent crashed after uploading 40 of 42 files. On restart it uploaded everything again, overwrote nothing useful, emitted two completion markers, and the pipeline ran twice—once on a partial set that somehow got marked ready during the race.
Read MoreIAM and KMS Across the Hybrid Lab–Cloud Boundary
Transfer logs said AccessDenied. The bucket policy “allowed S3.” Someone added s3:* on the role and it still failed—because the objects used SSE-KMS and the key policy never trusted the transfer identity.
Read MoreMoving Instrument Data to S3 Reliably
The object existed in S3. Size looked right. Downstream parsing failed because the transfer cut off mid-write and a later retry never ran—or ran into a different key. Metrics said “uploaded.” Science said “garbage.”
Read MoreHybrid Lab-to-Cloud: Map the Data Path Before Building It
The transfer agent was “done.” S3 had objects. Downstream Batch jobs still saw empty prefixes for hours. Nobody could say whether the instrument was late, the poller was stuck, or a completion marker never arrived.
Read More