AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation link, changed section title for clarity, fixed apostrophe usage, and corrected AWS Health Dashboard URL and 'Regionwide' spelling.
Security assessment
Changes are editorial improvements and URL updates without addressing security vulnerabilities or weaknesses. The content discusses disaster recovery automation best practices but doesn't introduce new security features or address specific security incidents.
Diff
diff --git a/prescriptive-guidance/latest/strategy-database-disaster-recovery/automating.md b/prescriptive-guidance/latest/strategy-database-disaster-recovery/automating.md index 7bc87d8a0..1c283c636 100644 --- a//prescriptive-guidance/latest/strategy-database-disaster-recovery/automating.md +++ b//prescriptive-guidance/latest/strategy-database-disaster-recovery/automating.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Disaster recovery strategy for databases on AWS](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Disaster recovery strategy for databases on AWS](introduction.html) @@ -9 +9 @@ Disaster event detectionFailover -# Automating your DR strategy +# Automating your disaster recovery strategy @@ -11 +11 @@ Disaster event detectionFailover -You can optionally choose to implement full or partial automation to gain better control of disaster recovery. If you’re using the backup and restore DR option, you can automate your backups by using [AWS Backup](https://aws.amazon.com/backup/), which supports all Amazon RDS databases as well as DynamoDB, Amazon DocumentDB, and Amazon Neptune tables. +You can optionally choose to implement full or partial automation to gain better control of disaster recovery. If you're using the backup and restore DR option, you can automate your backups by using [AWS Backup](https://aws.amazon.com/backup/), which supports all Amazon RDS databases as well as DynamoDB, Amazon DocumentDB, and Amazon Neptune tables. @@ -15 +15 @@ You can optionally choose to implement full or partial automation to gain better -To shorten the recovery time, you can consider automating the detection of a Regionwide event, which can then initiate failover to the DR Region. To implement automated detection to achieve an aggressive RTO, you can build a solution based on [health checks](https://aws.amazon.com/builders-library/implementing-health-checks/). These health checks do not stop at heartbeats (which check whether the control plane and data plane modules within a network can communicate with one another), but go deeper to evaluate the interrelated nature of application components to achieve an accurate prediction. However, an automated solution can carry the risk of false alarms, which can lead to unnecessary failovers. You should exercise caution in this case, because unnecessary failovers introduce availability issues for your business. You also can build manual overrides in the workflow to confirm that the failover has been carried out. You can subscribe to the [Service Health Dashboard](https://docs.aws.amazon.com/health/latest/ug/aws-health-dashboard-status.html) RSS feed to stay informed of service-level disruptions. Additionally, you can use the [AWS Health Dashboard](https://phd.aws.amazon.com/phd/home#/) (requires an AWS account) within your primary Region and account to stay aware of events that can affect your account. These can help you make an informed decision to fail over in the case of a Regionwide event. +To shorten the recovery time, you can consider automating the detection of a Regionwide event, which can then initiate failover to the DR Region. To implement automated detection to achieve an aggressive RTO, you can build a solution based on [health checks](https://aws.amazon.com/builders-library/implementing-health-checks/). These health checks do not stop at heartbeats (which check whether the control plane and data plane modules within a network can communicate with one another), but go deeper to evaluate the interrelated nature of application components to achieve an accurate prediction. However, an automated solution can carry the risk of false alarms, which can lead to unnecessary failovers. You should exercise caution in this case, because unnecessary failovers introduce availability issues for your business. You also can build manual overrides in the workflow to confirm that the failover has been carried out. You can subscribe to the [Service Health Dashboard](https://docs.aws.amazon.com/health/latest/ug/aws-health-dashboard-status.html) RSS feed to stay informed of service-level disruptions. Additionally, you can use the [AWS Health Dashboard ](https://aws.amazon.com/health/home)(requires an AWS account) within your primary Region and account to stay aware of events that can affect your account. These can help you make an informed decision to fail over in the case of a Region-wide event.