AWS drs documentation change

Service: drs · 2026-05-04 · Documentation low

File: drs/latest/userguide/failback-failover-cross-account.md

Summary

Updated diagram captions to provide clearer descriptions of cross-account disaster recovery architecture components and data flows.

Security assessment

The changes refine visual documentation about DR processes without mentioning security vulnerabilities, threat mitigations, or new security features. Caption updates focus on architectural clarity rather than security controls.

Diff

diff --git a/drs/latest/userguide/failback-failover-cross-account.md b/drs/latest/userguide/failback-failover-cross-account.md
index 5f5baec00..3153269ac 100644
--- a//drs/latest/userguide/failback-failover-cross-account.md
+++ b//drs/latest/userguide/failback-failover-cross-account.md
@@ -17 +17 @@ The failback process starts after the failover process ends. During failover, AW
-![Diagram showing AWS failback process with source and recovery accounts, regions, and EC2 instances.](/images/drs/latest/userguide/images/drs-after-failover-resources-state-cross-account.png)
+![EC2 source instances in source account replicate to DRS source servers and recovery instances in recovery account.](/images/drs/latest/userguide/images/drs-after-failover-resources-state-cross-account.png)
@@ -54 +54 @@ Once replication has reached a healthy state, failing back to the source account
-![AWS disaster recovery setup with source and recovery accounts, regions, and data replication flow.](/images/drs/latest/userguide/images/drs-failback-initiate-data-replication-1-cross-account.png)
+![DRS architecture showing EC2 instances in source account replicating to recovery account.](/images/drs/latest/userguide/images/drs-failback-initiate-data-replication-1-cross-account.png)
@@ -84 +84 @@ Make sure that your applications (A4) are working as expected. If you run into a
-![AWS disaster recovery setup with source and recovery accounts, regions, and instances.](/images/drs/latest/userguide/images/drs-failback-diagram-2-cross-account.png)
+![Disaster recovery architecture with source and recovery AWS accounts connected via Route 53.](/images/drs/latest/userguide/images/drs-failback-diagram-2-cross-account.png)
@@ -100 +100 @@ The newly launched failed-back instances (A4) are not protected. In order to pro
-![AWS disaster recovery setup with source and recovery accounts, regions, and instances.](/images/drs/latest/userguide/images/drs-after-failback-resources-state-cross-account.png)
+![EC2 instances failing back from Recovery AWS Account to Source AWS Account via Route 53.](/images/drs/latest/userguide/images/drs-after-failback-resources-state-cross-account.png)
@@ -152 +152 @@ After a successful drill your AWS environment should look like this:
-![AWS disaster recovery setup with source and recovery accounts, regions, and EC2 instances.](/images/drs/latest/userguide/images/drs-after-drill-resources-state-cross-account.png)
+![Architecture diagram showing EC2 source instances and DRS source servers in source account, with DRS recovery servers and EC2 recovered instances in recovery account.](/images/drs/latest/userguide/images/drs-after-drill-resources-state-cross-account.png)