AWS launchwizard documentation change
Summary
Updated IAM policy example with concrete account ID (111122223333) and improved JSON formatting
Security assessment
The change demonstrates proper IAM policy configuration by replacing a placeholder account ID, improving security documentation but not addressing an active vulnerability. This helps prevent accidental misconfiguration risks.
Diff
diff --git a/launchwizard/latest/userguide/launch-wizard-getting-started.md b/launchwizard/latest/userguide/launch-wizard-getting-started.md index 45487485e..0fa41b809 100644 --- a//launchwizard/latest/userguide/launch-wizard-getting-started.md +++ b//launchwizard/latest/userguide/launch-wizard-getting-started.md @@ -163,0 +164,6 @@ Launch Wizard uses AWS Secrets Manager to manage your domain and SQL Server acco +JSON + + +**** + + @@ -167 +173,2 @@ Launch Wizard uses AWS Secrets Manager to manage your domain and SQL Server acco - "Statement" : [ { + "Statement": [ + { @@ -171 +178 @@ Launch Wizard uses AWS Secrets Manager to manage your domain and SQL Server acco - "arn:aws:iam::<account-id>:role/service-role/AmazonEC2RoleForLaunchWizard" + "arn:aws:iam::111122223333:role/service-role/AmazonEC2RoleForLaunchWizard" @@ -179 +185,0 @@ Launch Wizard uses AWS Secrets Manager to manage your domain and SQL Server acco - } ] @@ -180,0 +187,3 @@ Launch Wizard uses AWS Secrets Manager to manage your domain and SQL Server acco + ] + } +