AWS Best Practices – Managing Cloud Resident Data in AWS

The DevOps team had called the CIO and were complaining that they were not getting copies of their Oracle database for testing in a timely manner.


To make matters worse, somebody mistakenly dropped a table in a MS SQL database which brought down a critical application. The DR team were relying on EBS snapshots stored in S3 for recovery, but the restoration times were far longer than expected for a 9TB MS-SQL database.

The security team was complaining to the CIO because both production and DR data copies are stored in the same AWS account.  The use of one account creates a significant security risk, and so they were demanding that DR data be moved to a separate account from production. Read more about the case study here: