Calling Jira Edit Issue API from AWS Lambda Times out

[ted_s]

Hi,

I am running into an issue where calling my lambda function locally through serverless offline runs smoothly and updates the Jira Issue successfully with the payload I passed in.

But when I deploy the Lambda to AWS and then trigger the function through Postman with the same payload, the connection to the Jira API times out.

Here is a snippet of my lambda service:

import { Version3Client } from "jira.js";

export const client = new Version3Client({

  host: process.env["JIRA_HOST"],

  authentication: {

    basic: {

      email: process.env["JIRA_USERNAME"],

      apiToken: process.env["JIRA_API_TOKEN"],

    },

  },

  newErrorHandling: true,

});

      client.issues.editIssue(

        {

          issueIdOrKey: issueKey,

          fields: {

            ...convertedPayload,

          },

        },

      );

As I stated above, when triggered locally through Postman and serverless offline, this code will update the ticket on my board on Jira within a second without any issues.

But when deploying to AWS Lambda and calling the API Gateway endpoint that triggers the lambda through Postman, the call to Jira will hang until it times out.

Does anyone know what may be happening? I figure that Jira is blocking the call.

Any help is appreciated. Cheers

[ted_s]

I ended up solving the issue. It turned out to be an async issue where a call was never returned correctly, so the Lambda service calling the Jira API just timed out waiting for a response.