AWS lake-formation documentation change
Summary
Standardized example account numbers and added JSON formatting markers
Security assessment
Example standardization without security implications
Diff
diff --git a/lake-formation/latest/dg/initial-lf-config.md b/lake-formation/latest/dg/initial-lf-config.md index bc3802d77..5cde9757f 100644 --- a//lake-formation/latest/dg/initial-lf-config.md +++ b//lake-formation/latest/dg/initial-lf-config.md @@ -156,0 +157,6 @@ Replace `<account-id>` with a valid AWS account number. +JSON + + +**** + + @@ -167 +173 @@ Replace `<account-id>` with a valid AWS account number. - "arn:aws:iam::<account-id>:role/LakeFormationWorkflowRole" + "arn:aws:iam::111122223333:role/LakeFormationWorkflowRole" @@ -176,0 +184,6 @@ A suggested name for the policy is `RAMAccess`. +JSON + + +**** + + @@ -270,0 +285,6 @@ Choose **Permissions**. +JSON + + +**** + + @@ -379,0 +401,6 @@ In the following policy, replace `<account-id>` with a valid AWS account number. +JSON + + +**** + + @@ -395 +422 @@ In the following policy, replace `<account-id>` with a valid AWS account number. - "arn:aws:iam::<account-id>:role/LakeFormationWorkflowRole" + "arn:aws:iam::111122223333:role/LakeFormationWorkflowRole"