AWS dms documentation change
Summary
Added JSON code blocks and updated VPC endpoint documentation link
Security assessment
JSON examples for IAM policies and encryption keys add security documentation. The VPC endpoint link change is editorial.
Diff
diff --git a/dms/latest/userguide/CHAP_Target.S3.md b/dms/latest/userguide/CHAP_Target.S3.md index ced4eee3e..208531774 100644 --- a//dms/latest/userguide/CHAP_Target.S3.md +++ b//dms/latest/userguide/CHAP_Target.S3.md @@ -102 +102 @@ Before using Amazon S3 as a target, check that the following are true: - * 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). + * 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). @@ -108,0 +109,6 @@ To set up this account access, ensure that the role assigned to the user account +JSON + + +**** + + @@ -459,0 +467,6 @@ Choose any other permissions you need, and then choose **Collapse all** to colla +JSON + + +**** + + @@ -537,0 +552,6 @@ When you create this key, you can only create a symmetric key, because all AWS s +JSON + + +**** + + @@ -844,0 +866,6 @@ For Amazon Athena to index your Amazon S3 data, and for you to query your data u +JSON + + +**** + +