AWS vpc documentation change
Summary
Updated branding from 'Amazon VPC Transit Gateways' to 'AWS Transit Gateway' throughout documentation, standardized capitalization in section headers, and updated IAM role references
Security assessment
Changes are primarily branding/naming convention updates and capitalization fixes. No security vulnerabilities or new security features are introduced. Existing security references to IAM roles/permissions remain unchanged in substance.
Diff
diff --git a/vpc/latest/tgw/tgw-flow-logs.md b/vpc/latest/tgw/tgw-flow-logs.md index 37d4e6006..568fbb370 100644 --- a//vpc/latest/tgw/tgw-flow-logs.md +++ b//vpc/latest/tgw/tgw-flow-logs.md @@ -7 +7 @@ LimitationsTransit Gateway Flow Log recordsControl the use of flow logsTransit G -# Amazon VPC Transit Gateways Flow Logs +# AWS Transit Gateway Flow Logs @@ -9 +9 @@ LimitationsTransit Gateway Flow Log recordsControl the use of flow logsTransit G -Transit Gateway Flow Logs is a feature of Amazon VPC Transit Gateways that enables you to capture information about the IP traffic going to and from your transit gateways. Flow log data can be published to Amazon CloudWatch Logs, Amazon S3, or Firehose. After you create a flow log, you can retrieve and view its data in the chosen destination. Flow log data is collected outside of the path of your network traffic, and therefore does not affect network throughput or latency. You can create or delete flow logs without any risk of impact to network performance. Transit Gateway Flow Logs capture information related only to transit gateways, described in Transit Gateway Flow Log records. If you want to capture information about IP traffic going to and from network interfaces in your VPCs, use VPC Flow Logs. See [Logging IP traffic using VPC Flow Logs](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html) in the _Amazon VPC User Guide_ for more information. +Transit Gateway Flow Logs is a feature of AWS Transit Gateway that enables you to capture information about the IP traffic going to and from your transit gateways. Flow log data can be published to Amazon CloudWatch Logs, Amazon S3, or Firehose. After you create a flow log, you can retrieve and view its data in the chosen destination. Flow log data is collected outside of the path of your network traffic, and therefore does not affect network throughput or latency. You can create or delete flow logs without any risk of impact to network performance. Transit Gateway Flow Logs capture information related only to transit gateways, described in Transit Gateway Flow Log records. If you want to capture information about IP traffic going to and from network interfaces in your VPCs, use VPC Flow Logs. See [Logging IP traffic using VPC Flow Logs](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html) in the _Amazon VPC User Guide_ for more information. @@ -30 +30 @@ You can apply tags to your flow logs. Each tag consists of a key and an optional -If you no longer require a flow log, you can delete it. Deleting a flow log disables the flow log service for the resource, and no new flow log records are created or published to CloudWatch Logs or Amazon S3. Deleting the flow log does not delete any existing flow log records or log streams (for CloudWatch Logs) or log file objects (for Amazon S3) for a transit gateway. To delete an existing log stream, use the CloudWatch Logs console. To delete existing log file objects, use the Amazon S3 console. After you've deleted a flow log, it can take several minutes to stop collecting data. For more information, see [Delete an Amazon VPC Transit Gateways Flow Logs record](./delete-flow-log.html). +If you no longer require a flow log, you can delete it. Deleting a flow log disables the flow log service for the resource, and no new flow log records are created or published to CloudWatch Logs or Amazon S3. Deleting the flow log does not delete any existing flow log records or log streams (for CloudWatch Logs) or log file objects (for Amazon S3) for a transit gateway. To delete an existing log stream, use the CloudWatch Logs console. To delete existing log file objects, use the Amazon S3 console. After you've deleted a flow log, it can take several minutes to stop collecting data. For more information, see [Delete an AWS Transit Gateway Flow Logs record](./delete-flow-log.html). @@ -34 +34 @@ You can create flow logs for your transit gateways that can publish data to Clou - * [Create a flow log that publishes to CloudWatch Logs ](./flow-logs-cwl-create-flow-log.html) + * [Create a Flow Log that publishes to CloudWatch Logs ](./flow-logs-cwl-create-flow-log.html) @@ -36 +36 @@ You can create flow logs for your transit gateways that can publish data to Clou - * [Create a flow log that publishes to Amazon S3](./flowlog-s3-create.html) + * [Create a Flow Log that publishes to Amazon S3](./flowlog-s3-create.html) @@ -38 +38 @@ You can create flow logs for your transit gateways that can publish data to Clou - * [Create a flow log that publishes to Firehose](./flow-logs-kinesis-create.html) + * [Create a Flow Log that publishes to Firehose](./flow-logs-kinesis-create.html) @@ -175 +175 @@ JSON -Some additional IAM role and permission configuration is required, depending on whether you're publishing to CloudWatch Logs or Amazon S3. For more information, see [Transit Gateway Flow Logs records in Amazon CloudWatch Logs](./flow-logs-cwl.html) and [ Transit Gateways Flow Logs records in Amazon S3 ](./flow-logs-s3.html). +Some additional IAM role and permission configuration is required, depending on whether you're publishing to CloudWatch Logs or Amazon S3. For more information, see [AWS Transit Gateway Flow Logs records in Amazon CloudWatch Logs](./flow-logs-cwl.html) and [AWS Transit Gateway Flow Logs records in Amazon S3 ](./flow-logs-s3.html). @@ -189 +189 @@ Example: Manage static group member configurations -Create or update a flow log IAM role +Create or update a Flow Logs IAM role