Has anyone run into an issue using versioned lambd...
# help
j
Has anyone run into an issue using versioned lambda ARNs for AppSync’s Custom Lambda Authorizer
t
Haven't tried this yet but what issue are you seeing?
j
The use case is to prevent cold starts by using provisioned concurrency. Provisioned concurrency is only available to Versioned ARNs. This is the graphQL response:
Copy code
{
  "error": {
    "errors": [
      {
        "errorType": "BadRequestException"
      }
    ]
  }
}
This is indicative of a Java error so it is internal to AWS as my CloudWatch logs for the Authorizer are empty.
Switching to non-versioned ARN fixes this, although it means cold starts
I have opened a support ticket with AWS
t
Hm strange
I actually am avoiding this by using a middleware pattern inside my application code 🤫
Didn't want the added latency of invoking two functions