A public-works work-order application still requires iSCSI block volumes during a multi-year hybrid transition, even as newer permit systems already write to Amazon S3. Which storage pattern should architects use so the legacy app can keep its block interface while data lands in AWS?
Select an answer to reveal the explanation.
Short Explanation
Some old apps still want a SCSI cable, not an object URL. Volume Gateway is the translator that keeps iSCSI on the floor while AWS holds the disks behind the scenes. Don't pretend S3 or Glacier speak iSCSI, and don't force a rewrite just to start the move.
Full Explanation
During hybrid transition, AWS Storage Gateway Volume Gateway presents iSCSI block volumes to applications that cannot yet change storage protocols, while storing volume data in AWS. That pattern lets public-works keep the legacy work-order stack online without treating S3 HTTP URLs or Glacier archives as live block devices. Forcing an EFS rewrite as a gate, or using Glacier snapshots as fake iSCSI, delays a controlled 7R transition.