AWS prescriptive-guidance documentation change
Summary
Updated formatting, fixed typos, restructured Glacier storage documentation, corrected links, and updated image paths
Security assessment
Changes involve formatting adjustments (table structure, note section), typo fixes ('architecture' to 'archiecture'), and updated terminology for Glacier storage classes. No security vulnerabilities, patches, or security features are mentioned. The existing security statement about data remaining 'secure and accessible' in Glacier is retained but not modified in substance.
Diff
diff --git a/prescriptive-guidance/latest/modern-data-centric-use-cases/best-practices.md b/prescriptive-guidance/latest/modern-data-centric-use-cases/best-practices.md index ae0a5603a..07419905a 100644 --- a//prescriptive-guidance/latest/modern-data-centric-use-cases/best-practices.md +++ b//prescriptive-guidance/latest/modern-data-centric-use-cases/best-practices.md @@ -11 +11 @@ Storage best practices for big dataTechnical best practices -We recommend that you follow storage and technical best practices. These best practices can help you get the most out of your data-centric architecture. +We recommend that you follow storage and technical best practices. These best practices can help you get the most out of your data-centric archicture. @@ -17 +17 @@ The following table describes a common best practice to store files for a big da -**Data layer name** | **Description** | **Example lifecycle policy strategy** +Data layer name| Description| Example lifecycle policy strategy @@ -19 +19,5 @@ The following table describes a common best practice to store files for a big da -Raw | Contains raw, unprocessed data**Note** : For an external data source, the raw data layer is typically a 1:1 copy of the data, but on AWS the data can be partitioned by keys based on AWS Region or date during the ingestion process. | After one year, move files into the S3 Standard-IA [storage class](https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html). After two years in S3 Standard-IA, archive the files in [Amazon Simple Storage Service Glacier (Amazon S3 Glacier)](https://docs.aws.amazon.com/amazonglacier/latest/dev/introduction.html). Amazon Glacier (original standalone vault-based service) will no longer accept new customers starting December 15, 2025, with no impact to existing customers. Amazon Glacier is a standalone service with its own APIs that stores data in vaults and is distinct from Amazon S3 and the Amazon S3 Glacier storage classes. Your existing data will remain secure and accessible in Amazon Glacier indefinitely. No migration is required. For low-cost, long-term archival storage, AWS recommends the [Amazon S3 Glacier storage classes](https://aws.amazon.com/s3/storage-classes/glacier/), which deliver a superior customer experience with S3 bucket-based APIs, full AWS Region availability, lower costs, and AWS service integration. If you want enhanced capabilities, consider migrating to Amazon S3 Glacier storage classes by using our [AWS Solutions Guidance for transferring data from Amazon S3 vaults to Amazon S3 Glacier storage classes.](https://aws.amazon.com/solutions/guidance/data-transfer-from-amazon-s3-glacier-vaults-to-amazon-s3/) +Raw| Contains raw, unprocessed data + +###### Note + +For an external data source, the raw data layer is typically a 1:1 copy of the data, but on AWS the data can be partitioned by keys based on AWS Region or date during the ingestion process.| After one year, move files into the S3 Standard-IA [storage class](https://docs.aws.amazon.com/AmazonS3/latest/userguide/storage-class-intro.html). After two years in S3 Standard-IA, archive the files in [Amazon Simple Storage Service Glacier (Amazon S3 Glacier)](https://docs.aws.amazon.com/amazonglacier/latest/dev/introduction.html).Amazon Glacier (original standalone vault-based service) will no longer accept new customers starting December 15, 2025, with no impact to existing customers. Amazon Glacier is a standalone service with its own APIs that stores data in vaults and is distinct from Amazon S3 and the Amazon Glacier storage classes. Your existing data will remain secure and accessible in Amazon Glacier indefinitely. No migration is required. For low-cost, long-term archival storage, AWS recommends the [Amazon Glacier storage classes](https://aws.amazon.com/s3/storage-classes/glacier/), which deliver a superior customer experience with S3 bucket-based APIs, full AWS Region availability, lower costs, and AWS service integration. If you want enhanced capabilities, consider migrating to Amazon Glacier storage classes by using our [AWS Solutions Guidance for transferring data from Amazon Glacier vaults to Amazon Glacier storage classes](https://aws.amazon.com/solutions/guidance/data-transfer-from-amazon-s3-glacier-vaults-to-amazon-s3/). @@ -25 +29 @@ The following diagram shows an example of a partitioning strategy (corresponding - + @@ -31 +35 @@ Technical best practices depend on the specific AWS services and processing tech -**Area** | **Best practice** +Area| Best practice @@ -37 +41 @@ Data pruning | Use [server-side partition pruning](https://docs.aws.amazon.com/g -Scaling | Understand and implement [horizontal scaling](https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.horizontal-scaling.en.html). +Scaling| Understand and implement [horizontal scaling](https://aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.horizontal-scaling.en.html).