AWS firehose documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in error logging configuration section
Security assessment
Terminology standardization. The change doesn't modify security aspects of CloudWatch logging configuration or access control requirements.
Diff
diff --git a/firehose/latest/dev/monitoring-with-cloudwatch-logs.md b/firehose/latest/dev/monitoring-with-cloudwatch-logs.md index bd6f383eb..40361eabc 100644 --- a//firehose/latest/dev/monitoring-with-cloudwatch-logs.md +++ b//firehose/latest/dev/monitoring-with-cloudwatch-logs.md @@ -15 +15 @@ For example, if you create a Firehose stream "MyStream" with Amazon Redshift as -You can enable Amazon Data Firehose error logging through the AWS CLI, the API, or AWS CloudFormation using the `CloudWatchLoggingOptions` configuration. To do so, create a log group and a log stream in advance. We recommend reserving that log group and log stream for Amazon Data Firehose error logging exclusively. Also ensure that the associated IAM policy has `"logs:putLogEvents"` permission. For more information, see [Controlling access with Amazon Data Firehose](./controlling-access.html). +You can enable Amazon Data Firehose error logging through the AWS CLI, the API, or CloudFormation using the `CloudWatchLoggingOptions` configuration. To do so, create a log group and a log stream in advance. We recommend reserving that log group and log stream for Amazon Data Firehose error logging exclusively. Also ensure that the associated IAM policy has `"logs:putLogEvents"` permission. For more information, see [Controlling access with Amazon Data Firehose](./controlling-access.html).