AWS prescriptive-guidance documentation change
Summary
Updated AWS Well-Architected and AWS DMS links with double slashes in URLs
Security assessment
Changes only involve URL path formatting corrections without modifying security-related content or introducing new security features.
Diff
diff --git a/prescriptive-guidance/latest/best-practices-migration-cutover/cutover-stage.md b/prescriptive-guidance/latest/best-practices-migration-cutover/cutover-stage.md index ce5ed3f04..5987838e2 100644 --- a//prescriptive-guidance/latest/best-practices-migration-cutover/cutover-stage.md +++ b//prescriptive-guidance/latest/best-practices-migration-cutover/cutover-stage.md @@ -91 +91 @@ It might not be possible to test all scenarios that will happen in production du -Before you cut over your application to AWS, we recommend that you perform an operational readiness review. This is where you evaluate the completeness of the testing, validate the ability of your team to monitor and obtain alerts, and confirm that your stakeholders understand how to support and maintain the workload. This will likely require working with both business and technical teams. For more information on operational readiness, see the _Operational Excellence Pillar_ of the AWS Well-Architected Tool Framework from [AWS Well-Architected](https://aws.amazon.com/architecture/well-architected/) in the AWS documentation. +Before you cut over your application to AWS, we recommend that you perform an operational readiness review. This is where you evaluate the completeness of the testing, validate the ability of your team to monitor and obtain alerts, and confirm that your stakeholders understand how to support and maintain the workload. This will likely require working with both business and technical teams. For more information on operational readiness, see the _Operational Excellence Pillar_ of the AWS Well-Architected Tool Framework from [AWS Well-Architected](https://aws.amazon.com//architecture/well-architected/) in the AWS documentation. @@ -114 +114 @@ If a rollback is initiated after a successful cutover and your application has r - * **Fail-forward approach** – Your on-premises database is likely to become stale post-cutover since the post-migration AWS database becomes the main database. You can use [AWS Database Migration Service (AWS DMS)](https://aws.amazon.com/dms/) to set up a fail-forward database, which will replicate the data to a new on-premises database. In the event of any issues, AWS DMS rolls back your applications to a designated fail-forward database rather than to a stale on-premises database. + * **Fail-forward approach** – Your on-premises database is likely to become stale post-cutover since the post-migration AWS database becomes the main database. You can use [AWS Database Migration Service (AWS DMS)](https://aws.amazon.com//dms/) to set up a fail-forward database, which will replicate the data to a new on-premises database. In the event of any issues, AWS DMS rolls back your applications to a designated fail-forward database rather than to a stale on-premises database.