AWS lambda documentation change
Summary
Changed 'AWS CloudFormation' to 'CloudFormation' in extensions configuration documentation
Security assessment
Consistency update in service naming. The mention of IAM permissions remains unchanged - no new security guidance added or modified.
Diff
diff --git a/lambda/latest/dg/lambda-extensions.md b/lambda/latest/dg/lambda-extensions.md index 3230e363b..978d9b0a0 100644 --- a//lambda/latest/dg/lambda-extensions.md +++ b//lambda/latest/dg/lambda-extensions.md @@ -15 +15 @@ An internal extension runs as part of the runtime process. Your function accesse -You can add extensions to a function using the Lambda console, the AWS Command Line Interface (AWS CLI), or infrastructure as code (IaC) services and tools such as AWS CloudFormation, AWS Serverless Application Model (AWS SAM), and Terraform. +You can add extensions to a function using the Lambda console, the AWS Command Line Interface (AWS CLI), or infrastructure as code (IaC) services and tools such as CloudFormation, AWS Serverless Application Model (AWS SAM), and Terraform. @@ -81 +81 @@ Extensions have access to the same resources as functions. Because extensions ar -For a .zip file archive, you can create an AWS CloudFormation template to simplify the task of attaching the same extension configuration—including AWS Identity and Access Management (IAM) permissions—to multiple functions. +For a .zip file archive, you can create an CloudFormation template to simplify the task of attaching the same extension configuration—including AWS Identity and Access Management (IAM) permissions—to multiple functions.