AWS apigateway documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' in Lambda authorizer context
Security assessment
Terminology standardization in authorization documentation without security feature changes
Diff
diff --git a/apigateway/latest/developerguide/apigateway-lambda-authorizer-verified-permissions.md b/apigateway/latest/developerguide/apigateway-lambda-authorizer-verified-permissions.md index 4042bdf5c..48a19ac9c 100644 --- a//apigateway/latest/developerguide/apigateway-lambda-authorizer-verified-permissions.md +++ b//apigateway/latest/developerguide/apigateway-lambda-authorizer-verified-permissions.md @@ -42 +42 @@ Verified Permissions still creates a Lambda authorizer for you. The Lambda autho -**Attach the authorizer for you (AWS CloudFormation)** +**Attach the authorizer for you (CloudFormation)** @@ -45 +45 @@ Verified Permissions still creates a Lambda authorizer for you. The Lambda autho -In the Verified Permissions-generated AWS CloudFormation template, in the `Conditions` section, set `"Ref": "shouldAttachAuthorizer"` to `true`. +In the Verified Permissions-generated CloudFormation template, in the `Conditions` section, set `"Ref": "shouldAttachAuthorizer"` to `true`. @@ -47 +47 @@ In the Verified Permissions-generated AWS CloudFormation template, in the `Condi -**Don't attach the authorizer for you (AWS CloudFormation)** +**Don't attach the authorizer for you (CloudFormation)** @@ -50 +50 @@ In the Verified Permissions-generated AWS CloudFormation template, in the `Condi -In the Verified Permissions-generated AWS CloudFormation template, in the `Conditions` section, set `"Ref": "shouldAttachAuthorizer"` to `false`. +In the Verified Permissions-generated CloudFormation template, in the `Conditions` section, set `"Ref": "shouldAttachAuthorizer"` to `false`.