AWS aws-backup documentation change

Service: aws-backup · 2025-11-22 · Documentation low

File: aws-backup/latest/devguide/restore-auroradsql.md

Summary

Modified JSON formatting in CLI examples and added IAM role ARN parameter

Security assessment

The changes appear to be syntax corrections (removing line breaks in JSON) and adding an explicit IAM role parameter. While IAM roles relate to security, there's no evidence this addresses a specific vulnerability or weakness. The change improves documentation accuracy but doesn't introduce new security features or address known issues.

Diff

diff --git a/aws-backup/latest/devguide/restore-auroradsql.md b/aws-backup/latest/devguide/restore-auroradsql.md
index a3442d2b6..37d40a2c6 100644
--- a//aws-backup/latest/devguide/restore-auroradsql.md
+++ b//aws-backup/latest/devguide/restore-auroradsql.md
@@ -70,9 +70 @@ AWS CLI
-        --metadata '{
-            "regionalConfig": [
-                {
-                    "region": "us-east-1",
-                    "isDeletionProtectionEnabled": true,
-                    "kmsKeyId": "my_key"
-                }
-            ]
-        }' \
+        --metadata '{"regionalConfig":"[{\"region\":\"us-east-1\",\"isDeletionProtectionEnabled\":true,\"kmsKeyId\":\"my_key\"}]"}' \
@@ -192,0 +185 @@ Both the primary cluster and peer cluster must be in Regions within the same gro
+    --iam-role-arn "arn:aws:iam::123456789012:role/service-role/AWSBackupDefaultServiceRole" \
@@ -195,2 +188,2 @@ Both the primary cluster and peer cluster must be in Regions within the same gro
-        "useMultiRegionOrchestration": true,
-        "peerRegion": ["us-east-2"],
+        "useMultiRegionOrchestration":"true",
+        "peerRegion":"[\"us-east-2\"]",
@@ -198 +191,2 @@ Both the primary cluster and peer cluster must be in Regions within the same gro
-    }'
+    }' \
+    --copy-source-tags-to-restored-resource