AWS eks documentation change
Summary
Updated service name references from 'Kinesis Data Firehose' to 'Amazon Data Firehose' in log delivery documentation
Security assessment
This change only updates branding/service naming. The security content about IAM policies and cross-account permissions remains unchanged and is not enhanced or modified for security reasons.
Diff
diff --git a/eks/latest/userguide/auto-managed-component-logs.md b/eks/latest/userguide/auto-managed-component-logs.md index 18c2e17a1..0d431a7b8 100644 --- a//eks/latest/userguide/auto-managed-component-logs.md +++ b//eks/latest/userguide/auto-managed-component-logs.md @@ -60 +60 @@ Setting up logging requires three steps: -You can configure the details of the destination for Auto Mode’s logs using the deliveryDestinationConfiguration object in the CloudWatch PutDeliveryDestination API. It takes the ARN of either a CloudWatch log group, S3 bucket, or Kinesis Data Firehose delivery stream. +You can configure the details of the destination for Auto Mode’s logs using the deliveryDestinationConfiguration object in the CloudWatch PutDeliveryDestination API. It takes the ARN of either a CloudWatch log group, S3 bucket, or Amazon Data Firehose delivery stream. @@ -66 +66 @@ You can configure a single Auto Mode capability (delivery source) to send logs t -Depending on the destination selected, you may need to configure IAM Policies or Roles for the CloudWatch log group, S3 bucket, and Kinesis Data Firehose to ensure successful log delivery. Additionally, if you’re sending logs across AWS accounts, you’ll need to use the PutDeliveryDestinationPolicy API to configure an IAM policy that allows delivery to the destination. See the [CloudWatch Vended Logs permissions documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html#AWS-logs-infrastructure-V2-CloudWatchLogs) for additional information. +Depending on the destination selected, you may need to configure IAM Policies or Roles for the CloudWatch log group, S3 bucket, and Amazon Data Firehose to ensure successful log delivery. Additionally, if you’re sending logs across AWS accounts, you’ll need to use the PutDeliveryDestinationPolicy API to configure an IAM policy that allows delivery to the destination. See the [CloudWatch Vended Logs permissions documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/AWS-logs-and-resource-policy.html#AWS-logs-infrastructure-V2-CloudWatchLogs) for additional information.