AWS prescriptive-guidance documentation change
Summary
Updated Glacier storage class names and consolidated IAM credential rotation note
Security assessment
Changes involve product name updates (Amazon Glacier → S3 Glacier) and formatting improvements. The preserved IAM credential rotation recommendation is an existing security best practice, not a new addition. No vulnerability remediation.
Diff
diff --git a/prescriptive-guidance/latest/patterns/back-up-and-archive-data-to-amazon-s3-with-veeam-backup-replication.md b/prescriptive-guidance/latest/patterns/back-up-and-archive-data-to-amazon-s3-with-veeam-backup-replication.md index 0bf4088f8..d802bd8c2 100644 --- a//prescriptive-guidance/latest/patterns/back-up-and-archive-data-to-amazon-s3-with-veeam-backup-replication.md +++ b//prescriptive-guidance/latest/patterns/back-up-and-archive-data-to-amazon-s3-with-veeam-backup-replication.md @@ -15 +15 @@ This pattern details the process for sending backups created by Veeam Backup & R -Veeam supports multiple Amazon S3 storage classes to best fit your specific needs. You can choose the type of storage based on the data access, resiliency, and cost requirements of your backup or archive data. For example, you can store data that you don’t plan to use for 30 days or longer in Amazon S3 infrequent access (IA) for lower cost. If you’re planning to archive data for 90 days or longer, you can use Amazon Glacier (Amazon Glacier) Flexible Retrieval or Amazon Glacier Deep Archive with Veeam’s archive tier. You can also use S3 Object Lock to make backups that are immutable within Amazon S3. +Veeam supports multiple Amazon S3 storage classes to best fit your specific needs. You can choose the type of storage based on the data access, resiliency, and cost requirements of your backup or archive data. For example, you can store data that you don’t plan to use for 30 days or longer in Amazon S3 infrequent access (IA) for lower cost. If you’re planning to archive data for 90 days or longer, you can use S3 Glacier Flexible Retrieval or S3 Glacier Deep Archive with Veeam’s archive tier. You can also use S3 Object Lock to make backups that are immutable within Amazon S3. @@ -72 +72 @@ Warning: This scenario requires AWS Identity and Access Management (IAM) users w - * Amazon Glacier Flexible Retrieval (v11 and later only) + * S3 Glacier Flexible Retrieval (v11 and later only) @@ -74 +74 @@ Warning: This scenario requires AWS Identity and Access Management (IAM) users w - * Amazon Glacier Deep Archive (v11 and later only) + * S3 Glacier Deep Archive (v11 and later only) @@ -76 +76 @@ Warning: This scenario requires AWS Identity and Access Management (IAM) users w - * Amazon Glacier Instant Retrieval (v12 and later only) + * S3 Glacier Instant Retrieval (v12 and later only) @@ -117 +117 @@ The workflow consists of three primary components that are required for tiering -Starting with Veeam Backup & Replication v12.2, the Direct to Amazon Glacier feature makes the S3 capacity tier optional. A SOBR can be configured with a performance tier and a Amazon Glacier archive tier. This configuration is useful for users who have significant investments in local (on-premises) storage for the capacity tier and who require only long-term archive retention in the cloud. For more information, see the [Veeam Backup & Replication documentation](https://helpcenter.veeam.com/docs/backup/vsphere/archive_tier.html?ver=120). +Starting with Veeam Backup & Replication v12.2, the Direct to Amazon Glacier feature makes the S3 capacity tier optional. A SOBR can be configured with a performance tier and an Amazon Glacier archive tier. This configuration is useful for users who have significant investments in local (on-premises) storage for the capacity tier and who require only long-term archive retention in the cloud. For more information, see the [Veeam Backup & Replication documentation](https://helpcenter.veeam.com/docs/backup/vsphere/archive_tier.html?ver=120). @@ -163,4 +163 @@ Use the CloudFormation templates provided in the [VeeamHub GitHub repository](ht - * In accordance with IAM best practices, we strongly recommend that you regularly rotate long-term IAM user credentials, such as the IAM user that you use for writing Veeam Backup & Replication backups to Amazon S3. For more information, see [Security best practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#rotate-credentials) in the IAM documentation. - - - +In accordance with IAM best practices, we strongly recommend that you regularly rotate long-term IAM user credentials, such as the IAM user that you use for writing Veeam Backup & Replication backups to Amazon S3. For more information, see [Security best practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#rotate-credentials) in the IAM documentation. @@ -223 +220 @@ Add Amazon Glacier storage for the archive tier.| If you want to create an archi - * If you want to use Amazon Glacier Deep Archive as your archival storage class, choose **Use the Deep Archive Storage Class**. + * If you want to use S3 Glacier Deep Archive as your archival storage class, choose **Use the Deep Archive Storage Class**. @@ -264 +261 @@ Add a scale-out backup repository and configure capacity and archive tiers.| - * Choose **Archive GFS full backups to object storage**. For the object storage repository, choose the Amazon S3 Glacier storage you added in the previous epic. + * Choose **Archive GFS full backups to object storage**. For the object storage repository, choose the Amazon Glacier storage you added in the previous epic.