# API Gateway Custom Authorizer not referencing 'provisioned' alias lambda when specifying provisioned concurrency

**URL:** <https://forum.serverless.com/t/api-gateway-custom-authorizer-not-referencing-provisioned-alias-lambda-when-specifying-provisioned-concurrency/11424>\
**Category:** Serverless Framework\
**Tags:** aws, lambda, api-gateway\
**Created:** [May 12, 2020, 10:04am UTC](https://forum.serverless.com/t/api-gateway-custom-authorizer-not-referencing-provisioned-alias-lambda-when-specifying-provisioned-concurrency/11424 "2020-05-12T10:04:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![howya](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@howya](https://forum.serverless.com/u/howya)\
**Post date:** [May 12, 2020, 10:04am UTC](https://forum.serverless.com/t/api-gateway-custom-authorizer-not-referencing-provisioned-alias-lambda-when-specifying-provisioned-concurrency/11424/1 "2020-05-12T10:04:15Z")

</div>

Hi,

Has anybody else come across this issue? I’m using:

```
Framework Core: 1.70.1
Plugin: 3.6.11
SDK: 2.3.0
Components: 2.30.10

```

I have a lambda function and custom authorizer, both using provisioned concurrency:  
…  
authenticator:  
general:  
name: authenticatorGeneral  
type: TOKEN  
# Cache authentication result for 5 minutes  
resultTtlInSeconds: 300  
identitySource: method.request.header.Authorization  
identityValidationExpression: Bearer (.\*)

```
functions:
  authenticatorGeneral:
    handler: src/authenticator.general
    provisionedConcurrency: 1
    reservedConcurrency: 10
    memorySize: 512
  proxy:
    handler: src/handler.server
    provisionedConcurrency: 1
    reservedConcurrency: 10
    memorySize: 1024
    events:
      - http:
          method: any
          path: /{proxy+}
          cors: true
          authorizer: ${self:custom.authenticator.general}
.....

```

Both these lambda functions are created with the provisioned alias and provisioning set as expected. API Gateway is mapping to the correctly aliased function for the proxy endpoint:

`aura-auth-service-prod-proxy:provisioned`

This works as expected, and does not suffer cold starts. If I check API Gateway for the custom authorizer mapping, it is not using the ‘provisioned’ alias:

`aura-auth-service-prod-authenticatorGeneral`

So I assume this will use ‘latest’, which is not provisioned? This is not working as expected and is suffering from cold starts.

Is this a known issue or am I configuring this incorrectly?

Cheers,

Rob

---

<div class="post-metadata">

**Author:** ![chrismcbride76](https://avatars.discourse-cdn.com/v4/letter/c/4da419/32.png) [@chrismcbride76](https://forum.serverless.com/u/chrismcbride76)\
**Post date:** [May 13, 2020, 7:37pm UTC](https://forum.serverless.com/t/api-gateway-custom-authorizer-not-referencing-provisioned-alias-lambda-when-specifying-provisioned-concurrency/11424/2 "2020-05-13T19:37:01Z")

</div>

I’m also encountering this same issue. Serverless is not configuring the references properly when using provisionedConcurrency for an authorizer.

---

<div class="post-metadata">

**Author:** ![chrismcbride76](https://avatars.discourse-cdn.com/v4/letter/c/4da419/32.png) [@chrismcbride76](https://forum.serverless.com/u/chrismcbride76)\
**Post date:** [May 13, 2020, 7:55pm UTC](https://forum.serverless.com/t/api-gateway-custom-authorizer-not-referencing-provisioned-alias-lambda-when-specifying-provisioned-concurrency/11424/3 "2020-05-13T19:55:24Z")

</div>

I submitted a bug report for this in github [https://github.com/serverless/serverless/issues/7726](https://github.com/serverless/serverless/issues/7726)

---

<div class="post-metadata">

**Author:** ![howya](https://avatars.discourse-cdn.com/v4/letter/h/87869e/32.png) [@howya](https://forum.serverless.com/u/howya)\
**Post date:** [May 14, 2020, 6:28am UTC](https://forum.serverless.com/t/api-gateway-custom-authorizer-not-referencing-provisioned-alias-lambda-when-specifying-provisioned-concurrency/11424/4 "2020-05-14T06:28:58Z")

</div>

Great, thanks for the link Chris.

---

<div class="post-metadata">

**Author:** ![dzorlu](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/dzorlu/32/6646_2.png) [@dzorlu](https://forum.serverless.com/u/dzorlu)\
**Post date:** [February 24, 2022, 7:26pm UTC](https://forum.serverless.com/t/api-gateway-custom-authorizer-not-referencing-provisioned-alias-lambda-when-specifying-provisioned-concurrency/11424/5 "2022-02-24T19:26:12Z")

</div>

Hi- This is a fairly old thread, but I ran into the same issue that API Gateway not referencing ‘provisioned’ alias lambda when specifying provisioned concurrency. Following the bug report link, it is not clear that it is fixed either.

What is the best way to handle this?  
Thank you.  
Deniz

---

<div class="post-metadata">

**Author:** ![krishay.baxter](https://avatars.discourse-cdn.com/v4/letter/k/51bf81/32.png) [@krishay.baxter](https://forum.serverless.com/u/krishay.baxter)\
**Post date:** [March 21, 2022, 2:21pm UTC](https://forum.serverless.com/t/api-gateway-custom-authorizer-not-referencing-provisioned-alias-lambda-when-specifying-provisioned-concurrency/11424/6 "2022-03-21T14:21:01Z")

</div>

Great, thanks for the link Chris.thanks for sharing  
[Showbox](https://showbox.bio/) [jiofi.local.html](https://jfi.uno/jiofilocalhtml)