AWS apigateway documentation change
Summary
Fixed typo from 'identify' to 'identity' in authorization documentation
Security assessment
The change corrects a spelling error without altering security functionality. There is no evidence of addressing vulnerabilities or security incidents.
Diff
diff --git a/apigateway/latest/developerguide/apigateway-lambda-authorizer-cross-account-lambda-authorizer.md b/apigateway/latest/developerguide/apigateway-lambda-authorizer-cross-account-lambda-authorizer.md index 0ad6aae6c..82edc52fd 100644 --- a//apigateway/latest/developerguide/apigateway-lambda-authorizer-cross-account-lambda-authorizer.md +++ b//apigateway/latest/developerguide/apigateway-lambda-authorizer-cross-account-lambda-authorizer.md @@ -57 +57 @@ The default **TTL** value is 300 seconds. The maximum value is 3600 seconds; thi -API Gateway uses the specified identity sources as the request authorizer caching key. When caching is enabled, API Gateway calls the authorizer's Lambda function only after successfully verifying that all the specified identity sources are present at runtime. If a specified identify source is missing, null, or empty, API Gateway returns a `401 Unauthorized` response without calling the authorizer Lambda function. +API Gateway uses the specified identity sources as the request authorizer caching key. When caching is enabled, API Gateway calls the authorizer's Lambda function only after successfully verifying that all the specified identity sources are present at runtime. If a specified identity source is missing, null, or empty, API Gateway returns a `401 Unauthorized` response without calling the authorizer Lambda function.