AWS drs documentation change
Summary
Removed two JSON trust policy examples for DRS service roles
Security assessment
The deleted examples showed role trust relationships for disaster recovery service principals. While role configuration is security-sensitive, the removal of these examples does not demonstrate resolution of a specific security issue. This seems like routine documentation maintenance rather than security-related updates.
Diff
diff --git a/drs/latest/userguide/getting-started-initializing.md b/drs/latest/userguide/getting-started-initializing.md index 8c7abf399..4e1898063 100644 --- a//drs/latest/userguide/getting-started-initializing.md +++ b//drs/latest/userguide/getting-started-initializing.md @@ -120,31 +119,0 @@ Example 1: creating a role for the **AWSElasticDisasterRecoveryAgentRole** with -JSON - - -**** - - - - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "Service": "drs.amazonaws.com" - }, - "Action": [ - "sts:AssumeRole", - "sts:SetSourceIdentity" - ], - "Condition": { - "StringLike": { - "sts:SourceIdentity": "s-*", - "aws:SourceAccount": "1234567891011" - } - } - } - ] - } - - - @@ -162,31 +130,0 @@ Example 2: creating a role for the **AWSElasticDisasterRecoveryFailbackRole** wi -JSON - - -**** - - - - { - "Version": "2012-10-17", - "Statement": [ - { - "Effect": "Allow", - "Principal": { - "Service": "drs.amazonaws.com" - }, - "Action": [ - "sts:AssumeRole", - "sts:SetSourceIdentity" - ], - "Condition": { - "StringLike": { - "aws:SourceAccount": "1234567891011", - "sts:SourceIdentity": "i-*" - } - } - } - ] - } - - -