AWS vpc documentation change
Summary
Updated product naming to 'AWS Transit Gateway', standardized 'Flow Log' capitalization in text and links
Security assessment
Changes are terminological improvements without introducing new security concepts. IAM role requirements were already documented
Diff
diff --git a/vpc/latest/tgw/flow-logs-kinesis-create.md b/vpc/latest/tgw/flow-logs-kinesis-create.md index e78d3318c..354aa2d7a 100644 --- a//vpc/latest/tgw/flow-logs-kinesis-create.md +++ b//vpc/latest/tgw/flow-logs-kinesis-create.md @@ -5 +5 @@ -# Create a Transit Gateway Flow Logs record that publishes to Amazon Data Firehose +# Create an AWS Transit Gateway Flow Logs record that publishes to Amazon Data Firehose @@ -7 +7 @@ -Create a Transit Gateway Flow Log that publishes to Amazon Data Firehose. Before you can create the flow log, ensure that you've set up the source and destination IAM account roles for cross-account delivery and that you've created the Firehose delivery stream. See [Amazon Data Firehose flow logs](./flow-logs-kinesis.html) for more information. You can create a Firehose flow log using either the Amazon VPC Console or the AWS CLI. +Create a Transit Gateway Flow Log that publishes to Amazon Data Firehose. Before you can create the flow log, ensure that you've set up the source and destination IAM account roles for cross-account delivery and that you've created the Firehose delivery stream. See [Amazon Data Firehose Flow Logs](./flow-logs-kinesis.html) for more information. You can create a Firehose flow log using either the Amazon VPC Console or the AWS CLI. @@ -75 +75 @@ Create the destination account role -Create and manage flow logs using the APIs or CLI +Create and manage Flow Logs using the APIs or CLI