AWS dms documentation change
Summary
Updated link title for VPC endpoints and added JSON formatting in IAM policy examples
Security assessment
Link title update is editorial. JSON formatting in IAM policies improves documentation clarity but does not resolve security issues.
Diff
diff --git a/dms/latest/userguide/CHAP_Source.S3.md b/dms/latest/userguide/CHAP_Source.S3.md index 49d85dbb6..d8cd8fdb3 100644 --- a//dms/latest/userguide/CHAP_Source.S3.md +++ b//dms/latest/userguide/CHAP_Source.S3.md @@ -258 +258 @@ Following is an example CDC file for a table named `employee`. -To use Amazon S3 as a source for AWS DMS, your source S3 bucket must be in the same AWS Region as the DMS replication instance that migrates your data. In addition, the AWS account you use for the migration must have read access to the source bucket. For AWS DMS version 3.4.7 and higher, DMS must access the source bucket through a VPC endpoint or a public route. For information about VPC endpoints, see [Configuring VPC endpoints as AWS DMS source and target endpoints](./CHAP_VPC_Endpoints.html). +To use Amazon S3 as a source for AWS DMS, your source S3 bucket must be in the same AWS Region as the DMS replication instance that migrates your data. In addition, the AWS account you use for the migration must have read access to the source bucket. For AWS DMS version 3.4.7 and higher, DMS must access the source bucket through a VPC endpoint or a public route. For information about VPC endpoints, see [Configuring VPC endpoints for AWS DMS](./CHAP_VPC_Endpoints.html). @@ -261,0 +262,6 @@ The AWS Identity and Access Management (IAM) role assigned to the user account u +JSON + + +**** + + @@ -289,0 +297,6 @@ The AWS Identity and Access Management (IAM) role assigned to the user account u +JSON + + +**** + +