The auditors found that the market could lose its records in a dozen ways. Fix all of them. You have the bucket market-vault-k4hie6, the role s3-replication for S3 to copy with, and two servers with Session Manager: vault-k4hie6 in us-east-1a and standby-k4hie6 in us-east-1b, both in the group vault-servers-k4hie6. vault-k4hie6 keeps the accounts in /srv/ledger/accounts.csv.

1. The bucket keeps history and gets cheaper with age. market-vault-k4hie6 keeps every version. A lifecycle rule for the whole bucket moves objects to Standard-IA at 30 days and Glacier at 90, and deletes old versions 30 days after they are replaced.
2. A copy in Ireland. New objects are replicated to a bucket market-vault-eu-k4hie6 in eu-west-1. Prove it with ~/ledger.csv, uploaded to the vault bucket as ledger.csv after replication is on.
3. The accounts survive a zone. Put the accounts on a data disk of vault-k4hie6 (a new volume mounted on /ledger, with accounts.csv copied onto it). Snapshot that disk, restore it as a volume named vault-restore in the standby's zone, and mount it on /restore on standby-k4hie6 so the accounts can be read there.
4. A shared folder. An EFS file system named vault-share, mounted on /mnt/share on both servers. Give its mount targets a security group of their own that admits vault-servers-k4hie6 on the NFS port.