AWS dms documentation change
Summary
Added JSON code blocks and updated VPC endpoint documentation link
Security assessment
JSON sections provide IAM policy examples (security documentation). The VPC endpoint link update improves clarity but does not indicate a security fix.
Diff
diff --git a/dms/latest/userguide/CHAP_Target.Kinesis.md b/dms/latest/userguide/CHAP_Target.Kinesis.md index 3c7fd1b06..28a4d2a23 100644 --- a//dms/latest/userguide/CHAP_Target.Kinesis.md +++ b//dms/latest/userguide/CHAP_Target.Kinesis.md @@ -232,0 +233,6 @@ Before you set up a Kinesis data stream as a target for AWS DMS, make sure that +JSON + + +**** + + @@ -251,0 +259,6 @@ The role that you use for the migration to a Kinesis data stream must have the f +JSON + + +**** + + @@ -273 +287 @@ In AWS DMS version 3.4.7 and higher, to connect to an Kinesis endpoint, you must - * Configure DMS to use VPC endpoints. For information about configuring DMS to use VPC endpoints, see [Configuring VPC endpoints as AWS DMS source and target endpoints](./CHAP_VPC_Endpoints.html). + * Configure DMS to use VPC endpoints. For information about configuring DMS to use VPC endpoints, see [Configuring VPC endpoints for AWS DMS](./CHAP_VPC_Endpoints.html).