AWS kendra documentation change
Summary
Updated sign-up verification options (added text message) and added JSON formatting/separators in IAM policy documentation sections
Security assessment
Adding text message as a verification option improves multi-factor authentication (MFA) capabilities, which is a security feature. However, there is no evidence this addresses a specific security vulnerability. The JSON formatting changes appear to be documentation structure improvements without security implications.
Diff
diff --git a/kendra/latest/dg/gs-prerequisites.md b/kendra/latest/dg/gs-prerequisites.md index 235d96634..b1dd9780a 100644 --- a//kendra/latest/dg/gs-prerequisites.md +++ b//kendra/latest/dg/gs-prerequisites.md @@ -21 +21 @@ If you do not have an AWS account, complete the following steps to create one. -Part of the sign-up procedure involves receiving a phone call and entering a verification code on the phone keypad. +Part of the sign-up procedure involves receiving a phone call or text message and entering a verification code on the phone keypad. @@ -100,0 +101,6 @@ First, you must attach the below permissions to your IAM user. +JSON + + +**** + + @@ -170,0 +178,6 @@ Second, if you use the CLI or SDK, you must also create an IAM role and policy t +JSON + + +**** + + @@ -233,0 +248,6 @@ Second, if you use the CLI or SDK, you must also create an IAM role and policy t +JSON + + +**** + + @@ -261,0 +283,6 @@ Third, if you use an Amazon S3 to store your documents or you are using S3 to te +JSON + + +**** + + @@ -311,0 +340,6 @@ Third, if you use an Amazon S3 to store your documents or you are using S3 to te +JSON + + +**** + +