Using a Data Connection to trigger an AWS API Gateway

[shardern_kpmg]

We want to utilise JSM's Data Connections for use in forms, however many of the API endpoints we want to hit have features that Data Connections cannot manage:

• Pagination
• Services within private VPC
• Tokens that need regenerating

I want to use AWS Proxy Lambdas in order to remove these limitations and gain the benefit of Data Connections. The last puzzle piece that needs sorting is triggering the AWS Lambdas through Data Connections.

The 3 built in authentication methods: Basic, Digest and Custom, have not yet worked to trigger our lambdas, which require an x-api-key header. 

Wondering if anyone has had success using this authentication method or knows of an alternative auth method that can be configured on AWS's side to get this to work.

Thanks in advance.

[shardern_kpmg · Accepted solution]

For anyone that comes across this post, I eventually settled on using the "Custom" authentication method on Jira's side and removing any authentication from the AWS API Endpoint.

Since I'm using proxy lambdas, data from the request is sent to the lambda, including the custom token in the headers. Using this, I just compared against a value in a parameter store and carried on with the lambda if they matched, or just returned "Unauthorised" if they didn't.

So yes, the way to authenticate in this case is to not have any authentication at all.