AWS Security ChangesHomeSearch

AWS resilience-hub documentation change

Service: resilience-hub · 2025-10-25 · Documentation low

File: resilience-hub/latest/userguide/security-iam-resilience-hub-invoker-role.md

Summary

Removed detailed JSON role example and replaced with placeholder markers (JSON/****)

Security assessment

Change restructures IAM role documentation but doesn't address vulnerabilities. Maintains security documentation about required roles.

Diff

diff --git a/resilience-hub/latest/userguide/security-iam-resilience-hub-invoker-role.md b/resilience-hub/latest/userguide/security-iam-resilience-hub-invoker-role.md
index 08bee6049..6fdf8ebab 100644
--- a//resilience-hub/latest/userguide/security-iam-resilience-hub-invoker-role.md
+++ b//resilience-hub/latest/userguide/security-iam-resilience-hub-invoker-role.md
@@ -43,0 +44,6 @@ If your resources are in different accounts, you have to create a role in each o
+JSON
+    
+
+****
+    
+    
@@ -107,0 +115,6 @@ You can define the trust policy for the role using a separate JSON file and then
+JSON
+    
+
+****
+    
+    
@@ -126,21 +139,0 @@ You can define the trust policy for the role using a separate JSON file and then
-    
-    {
-        "Role": {
-            "Path": "/",
-            "RoleName": "AWSResilienceHubAssessmentRole",
-            "RoleId": "AROAQFOXMPL6TZ6ITKWND",
-            "Arn": "arn:aws:iam::123456789012:role/AWSResilienceHubAssessmentRole",
-            "CreateDate": "2020-01-17T23:19:12Z",
-            "AssumeRolePolicyDocument": {
-                "Version": "2012-10-17",
-                "Statement": [{
-                    "Effect": "Allow",
-                    "Principal": {
-                        "Service": "resiliencehub.amazonaws.com"
-                    },
-                    "Action": "sts:AssumeRole"
-                }]
-            }
-        }
-    }
-