At the recently hosted Amazon AWS Summit, there was a topic I was more interested in: "Technical experience-how cloud backup and disaster recovery", a speaker of Amazon Web services gave attendees a history lesson, mainly about the Monte Cassino Monastery in Italy related to cloud backup. Although the main content is to preach Amazon AWS Advantages, but in the cloud backup to pay attention to what problems, how to meet these needs are given a good hint, there is a certain reference significance.
Why does the monastery of Monte Cassino in Italy have to implement "cloud backup"? In the early 20th century, Monte Cassino had a wealth of precious treasures, including papal documents, and paintings by Italian painters. In the 1944, during World War II, monasteries were bombed. But shortly before the bombing, the monastery's two staff members transferred it to the Vatican, Italy, in order to keep the treasures. Due to the implementation of this backup plan, the monastery was repaired in 1954. This is not to say that the monastery is really a cloud backup, but a metaphor.
Interestingly, the Monte Cassino Monastery's behavior actually illustrates several big needs for cloud backup. For example, to make sure that cloud backups are easy to access, cloud backups are worthless. So the monastery treasures are hidden above the Vatican heights in the north-west corner of the Italian capital, Rome. So how does AWS do that? Customers have full control over their backups and can access them without involving Amazon in the event of a disaster. There are many ways to achieve this, such as redundancy, AWS Import/export, AWS Storage gateways, and AWS connections that direct and provide backups.
Second, scalability is considered. AWS customers can extend backup data to multiple areas, and Amazon's simple object storage services, glacier, have extended cloud backups to prepare for the disaster.
Furthermore, ensure the security of the cloud backup. The Vatican is a safe place to store the treasures of the Monte Cassino monastery. However, if the cloud backup does not have the appropriate protection data, it is worthless. Security of backups can be secured by using Secure Sockets Layer endpoints, logon application interfaces, calls, and server-side encryption. AWS maintains sustainability through multiple backups of different data centers.
In addition, remember to work with the disaster recovery strategy. Back up your cloud data and applications, and always keep in mind the disaster recovery plan. If these backups are safe, they need to be restored, not as long as a monastery. To ensure that data can recover quickly after a disaster, you can consolidate storage and AWS to run services on its flexible Computing Cloud (EC2). Customers can back up snapshots on AWS, then accelerate EC2, adding capacity to service providers, allowing applications to start quickly and run in the cloud.
Finally, you need to know who cares most about the data. The Treasure of cloud users is their data, who are most concerned about the security of data, such as the monastery's staff cherish their treasures. Therefore, it is important to clearly identify who is responsible for the access strategy of the cloud environment. For example, you can use AWS identification and access management to set roles and permissions. This also makes it easier to understand who is accessing the data. This is also the importance of logging, and not only that, the log also helps to find vulnerabilities and fix them.
To this end, I see the story is finished, but the details need to be understood. In addition, Monte Cassino Monastery is a famous monastery in central Italy, in the Battle of the Romacassino during World War II, many people interested in this information may wish to search for understanding:).
(Responsible editor: The good of the Legacy)