We have announce the adoption of AWS Backup last week and now we would like to announce an improved version of our SOP. We have also addressed some of the questions in the last Wednesday sharing session.
[SOP] Backing Up Resources with AWS Backup
[SOP] Restoring Resources with AWS Backup
All Teams can start tagging their resources according to the SOP right now. See timeline for more details.
For all Engineers in Product Teams
Tag resources with the Key: OrgAWSBackup and Value as one of the following: Hourly or Daily. This allows them to be backed up into the Backup Vault automatically. Read this SOP for further information.
If you haven’t join the sharing session on last Wednesday. Please join the sharing session about this on Mar 22, 2022 at 03:00PM UTC+7
Different teams are implementing their own backup policies, tools and processes, which eliminates visibility. AWS Backup Manager allows us to centrally monitor and manage backups, so we can easily create auditing reports and ensure they’re being backed up according to their respective policies.
Mar 7, 2022 : Organization-wide backup policies are rolled out.
Mar 14, 2022 - Mar 22, 2022 : Socialization and sharing sessions are held.
Mar 17, 2022 : Teams start tagging their resources.
Apr 1, 2022 : All teams should have tagged their resources.
Please contact the Cloud Infra team through #site-infra-channel and through Jira Service Desk [2].
Vincent, on behalf of the Cloud Infra Team