AWS AWSCloudFormation low security documentation change
Summary
Added LoggingConfig property documentation and updated branding references from 'AWS CloudFormation' to 'CloudFormation'
Security assessment
The addition of LoggingConfig documentation introduces security-relevant configuration for CloudWatch Logs monitoring. Proper logging configuration helps detect and investigate security incidents, making this a security feature addition. However, there is no evidence of addressing a specific vulnerability.
Diff
diff --git a/AWSCloudFormation/latest/TemplateReference/aws-resource-lambda-eventsourcemapping.md b/AWSCloudFormation/latest/TemplateReference/aws-resource-lambda-eventsourcemapping.md index 8b3c1dfb1..3e922a33e 100644 --- a//AWSCloudFormation/latest/TemplateReference/aws-resource-lambda-eventsourcemapping.md +++ b//AWSCloudFormation/latest/TemplateReference/aws-resource-lambda-eventsourcemapping.md @@ -5 +5 @@ SyntaxPropertiesReturn valuesExamples -This is the new _AWS CloudFormation Template Reference Guide_. Please update your bookmarks and links. For help getting started with CloudFormation, see the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html). +This is the new _CloudFormation Template Reference Guide_. Please update your bookmarks and links. For help getting started with CloudFormation, see the [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html). @@ -32 +32 @@ For details about each event source type, see the following topics. In particula -To declare this entity in your AWS CloudFormation template, use the following syntax: +To declare this entity in your CloudFormation template, use the following syntax: @@ -50,0 +51 @@ To declare this entity in your AWS CloudFormation template, use the following sy + "LoggingConfig" : [LoggingConfig](./aws-properties-lambda-eventsourcemapping-loggingconfig.html), @@ -91,0 +93,2 @@ To declare this entity in your AWS CloudFormation template, use the following sy + LoggingConfig: + [LoggingConfig](./aws-properties-lambda-eventsourcemapping-loggingconfig.html) @@ -320,0 +324,11 @@ _Minimum_ : `12` +`LoggingConfig` + + +The function's Amazon CloudWatch Logs configuration settings. + +_Required_ : No + + _Type_ : [LoggingConfig](./aws-properties-lambda-eventsourcemapping-loggingconfig.html) + + _Update requires_ : [No interruption](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks-update-behaviors.html#update-no-interrupt) + @@ -520 +534 @@ A list of tags to add to the event source mapping. -You must have the `lambda:TagResource`, `lambda:UntagResource`, and `lambda:ListTags` permissions for your [IAM principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html) to manage the AWS CloudFormation stack. If you don't have these permissions, there might be unexpected behavior with stack-level tags propagating to the resource during resource creation and update. +You must have the `lambda:TagResource`, `lambda:UntagResource`, and `lambda:ListTags` permissions for your [IAM principal](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_terms-and-concepts.html) to manage the CloudFormation stack. If you don't have these permissions, there might be unexpected behavior with stack-level tags propagating to the resource during resource creation and update.