AWS prescriptive-guidance documentation change
Summary
Updated 'Amazon S3 Glacier' to 'Amazon Glacier' in archival storage references and service names
Security assessment
Nomenclature update without security implications. Governance/compliance aspects mentioned remain unaffected by the naming change.
Diff
diff --git a/prescriptive-guidance/latest/oracle-exadata-blueprint/performing-homogeneous.md b/prescriptive-guidance/latest/oracle-exadata-blueprint/performing-homogeneous.md index 90cefe04b..bb6c4c9fb 100644 --- a//prescriptive-guidance/latest/oracle-exadata-blueprint/performing-homogeneous.md +++ b//prescriptive-guidance/latest/oracle-exadata-blueprint/performing-homogeneous.md @@ -57 +57 @@ For example, let's say you have a table that consumes multiple tebibytes of unco -Users often store active data, infrequently accessed data, and archive data in a single Oracle database. During your Oracle database migration to AWS, you can migrate infrequently accessed data, historical audit data, and archive data directly into [Amazon S3](https://aws.amazon.com/s3/) or [Amazon S3 Glacier](https://aws.amazon.com/s3/storage-classes/glacier/). This helps you meet your governance and compliance needs for long-term data retention without impacting database performance. As data ages in the relational database, it can be archived to [Amazon S3](https://aws.amazon.com/s3/) or [Amazon S3 Glacier](https://aws.amazon.com/s3/storage-classes/glacier/). You can easily query the archived data by using [Amazon Athena](https://aws.amazon.com/athena/) or [Amazon S3 Glacier Select](https://docs.aws.amazon.com/prescriptive-guidance/latest/archiving-mysql-data/read-s3-glacier-storage-class.html). +Users often store active data, infrequently accessed data, and archive data in a single Oracle database. During your Oracle database migration to AWS, you can migrate infrequently accessed data, historical audit data, and archive data directly into [Amazon S3](https://aws.amazon.com/s3/) or [Amazon Glacier](https://aws.amazon.com/s3/storage-classes/glacier/). This helps you meet your governance and compliance needs for long-term data retention without impacting database performance. As data ages in the relational database, it can be archived to [Amazon S3](https://aws.amazon.com/s3/) or [Amazon Glacier](https://aws.amazon.com/s3/storage-classes/glacier/). You can easily query the archived data by using [Amazon Athena](https://aws.amazon.com/athena/) or [Amazon Glacier Select](https://docs.aws.amazon.com/prescriptive-guidance/latest/archiving-mysql-data/read-s3-glacier-storage-class.html).