mirror of
https://github.com/serverless/serverless.git
synced 2026-01-25 15:07:39 +00:00
7abb23edc8
There are use cases where an API creator does not have permissions to add permissions to the custom authorizer lambda; one example is when the custom authorizer lambda exists in a separate AWS account. In these cases, we need to be able to omit the `AWS::Lambda::Permission` resource from the stack. This change adds the `managedExternally` attribute to the `authorizer`. When `managedExternally` is `true`, the stack will not create the `AWS::Lambda::Permission` resource. **Important note:** The permission does still need to be created before the stack is deployed, or creating the authorizer will fail.