AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb links, improved section headings, removed code formatting from API terms, fixed grammatical errors, and enhanced clarity around DNS CNAME usage for database recovery.
Security assessment
Changes are editorial improvements and clarifications about backup/recovery procedures. No security vulnerabilities or incidents are mentioned. The DNS CNAME clarification focuses on reducing client impact during recovery, not addressing security flaws.
Diff
diff --git a/prescriptive-guidance/latest/backup-recovery/rds.md b/prescriptive-guidance/latest/backup-recovery/rds.md index 01359e357..016721433 100644 --- a//prescriptive-guidance/latest/backup-recovery/rds.md +++ b//prescriptive-guidance/latest/backup-recovery/rds.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Backup and recovery approaches on AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Backup and recovery approaches on AWS](introduction.html) @@ -7 +7 @@ -Using DNS CNAME +Using DNS CNAME records to reduce client impact during a database recovery @@ -17 +17 @@ Amazon RDS provides two different options for backing up and restoring your DB i -Amazon RDS performs a daily backup of your data during a backup window that you define when you create the DB instance. You can configure a retention period of up to 35 days for the automated backup. Amazon RDS also uploads the transaction logs for DB instances to Amazon S3 every 5 minutes. Amazon RDS uses your daily backups along with your database transaction logs to restore your DB instance. You can restore the instance to any second during your retention period, up to the `LatestRestorableTime` (typically, the last five minutes). +Amazon RDS performs a daily backup of your data during a backup window that you define when you create the DB instance. You can configure a retention period of up to 35 days for the automated backup. Amazon RDS also uploads the transaction logs for DB instances to Amazon S3 every 5 minutes. Amazon RDS uses your daily backups along with your database transaction logs to restore your DB instance. You can restore the instance to any second during your retention period, up to the LatestRestorableTime (typically, the last five minutes). @@ -19 +19 @@ Amazon RDS performs a daily backup of your data during a backup window that you -To find the latest restorable time for your DB instances, use the `DescribeDBInstances` API call. Or look on the **Description** tab for the database on the Amazon RDS console. +To find the latest restorable time for your DB instances, use the DescribeDBInstances API call. Or look on the **Description** tab for the database on the Amazon RDS console. @@ -23 +23 @@ When you initiate a PITR, transaction logs are combined with the most appropriat - * **DB snapshots** are user-initiated backups that you can use to restore your DB instance to a known state as frequently as you like. You can then restore to that state at any time. You can use the Amazon RDS console or the `CreateDBSnapshot` API call to create DB snapshots. These snapshots are kept until you use the console or the `DeleteDBSnapshot` API call to explicitly delete them. + * **DB snapshots** are user-initiated backups that you can use to restore your DB instance to a known state as frequently as you like. You can then restore to that state at any time. You can use the Amazon RDS console or the CreateDBSnapshot API call to create DB snapshots. These snapshots are kept until you use the console or the DeleteDBSnapshot API call to explicitly delete them. @@ -28 +28 @@ When you initiate a PITR, transaction logs are combined with the most appropriat -Both of these backup options are supported for Amazon RDS in AWS Backup, which also provides other features. Consider using AWS Backup to set up a standard backup plan for your Amazon RDS databases, and use the user-initiated instance backup options when your backup plans for a particular database are unique. +Both of these backup options are supported for Amazon RDS in AWS Backup, which also provides other features. Consider using AWS Backup to set up a standard backup plan for your Amazon RDS databases, and use the user-initiated instance backup options when your backup plan for a particular database are unique. @@ -44 +44 @@ Applications and client operating systems might also cache DNS information that -When you initiate a database restore and shift traffic to your restored instance, verify that all your clients are writing to your restored instance instead of your prior instance. Your data architecture might support restoring your database, updating DNS to shift traffic to your restored instance, and then remediating any data that may still be written to your prior instance. If this isn’t the case, you can stop your existing instance before you update the DNS CNAME record. Then all access is from your newly restored instance. This may temporarily cause connection problems for some of your database clients that you can handle individually. To reduce client impact, you can perform the database restore during a maintenance window. +When you initiate a database restore and shift traffic to your restored instance, verify that all your clients are writing to your restored instance instead of your prior instance. Your data architecture might support restoring your database, updating DNS to shift traffic to your restored instance, and then remediating any data that may still be written to your prior instance. If this isn't the case, you can stop your existing instance before you update the DNS CNAME record. Then all access is from your newly restored instance. This may temporarily cause connection problems for some of your database clients that you can handle individually. To reduce client impact, you can perform the database restore during a maintenance window. @@ -56 +56 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Cloud-native AWS services +Backup and recovery of cloud-native AWS services @@ -58 +58 @@ Cloud-native AWS services -DynamoDB +Backup and recovery for DynamoDB