1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
Hi There
You can also consider using a managed filesystem like Amazon EFS to store the data instead of S3 or EBS. Take a look at the WordPress on AWS Reference Architecture
https://docs.aws.amazon.com/whitepapers/latest/best-practices-wordpress/reference-architecture.html
To answer your question, you can use AWS Backup to create backups of your S3 bucket and a lifecycle policy to transition objects to other storage classes like Glacier. See https://docs.aws.amazon.com/aws-backup/latest/devguide/s3-backups.html
With AWS Backup, you can create the following types of backups of your S3 buckets, including object data, tags, Access Control Lists (ACLs), and user-defined metadata:
Continuous backups, allowing you to restore to any point in time within the last 35 days. Continuous backups for an S3 bucket should only be configured in one backup plan.
See Point-in-Time Recovery for a list of supported services and instructions on how to use AWS Backup to take continuous backups.
Periodic backups, which allow you to retain data for your specified duration, including indefinitely. You can schedule periodic backups in frequencies such as 1 hour, 12 hours, 1 day, 1 week, or 1 month. AWS Backup takes periodic backups during the backup window you define in your backup plan.
See Creating a backup plan to understand how AWS Backup applies your backup plan to your resources.
Thank you for your answer and suggestion. I was aware of the guidelines but I didn't know about the EFS. Now it seems pretty clear to me. Thank you.
ps, the architecture shows a single domain that grows in terms of resources/instances according to user requests/load/region. I will adapt this to a single EC2 per domain behind a single LB, I hope it will work fine.