AWS b2bi documentation change
Summary
Added text message verification option in sign-up docs and inserted JSON formatting markers in S3 bucket policy examples
Security assessment
Text message verification expansion improves MFA options documentation but doesn't introduce new security features. JSON formatting changes are structural and don't alter security policies.
Diff
diff --git a/b2bi/latest/userguide/b2bi-prereq.md b/b2bi/latest/userguide/b2bi-prereq.md index 4b7b8ded0..c7c3d401d 100644 --- a//b2bi/latest/userguide/b2bi-prereq.md +++ b//b2bi/latest/userguide/b2bi-prereq.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. @@ -167,0 +168,8 @@ Example Amazon S3 input bucket policy copied from the **Trading capabilities** p +JSON + +JSON + + +**** + + @@ -196,0 +206,8 @@ Example Amazon S3 output bucket policy copied from the **Trading capabilities** +JSON + +JSON + + +**** + + @@ -233,0 +252,8 @@ The following example policy is for use with an encrypted input/source bucket. I +JSON + +JSON + + +**** + + @@ -264,0 +292,8 @@ The following example policy is for use with an encrypted output bucket. It incl +JSON + +JSON + + +**** + + @@ -292,0 +329,6 @@ If you are using the same bucket for input and output, you can use either exampl +JSON + + +**** + +