Skip to content

Make APIs available as functions in lambdas #3427

@mooreds

Description

@mooreds

Make APIs available as functions in lambdas

Problem

When I want to make an API call in a lambda, there's all kinds of incidental complexity. I can do so by using the fetch command, but:

  • I'm worried about which transaction it is occurring in
  • I need to be prepared to handle HTTP failure
  • It negatively affects performance, even over loopback

Solution

Make APIs available as functions in lambdas. Now I'm making API calls directly in the context of the lambda execution, negating all the issues above.

Probably don't need to expose all the APIs, a subset would be enough. Suggested subset:

  • JWT Vend
  • Groups
  • Entities

Alternatives/workarounds

As mentioned, use fetch and deal.

Additional context

Came up on a prospect call.

Internal: https://inversoft.slack.com/archives/C0A3NPAS8F7/p1775582730379019?thread_ts=1775582665.582039&cid=C0A3NPAS8F7

Community guidelines

All issues filed in this repository must abide by the FusionAuth community guidelines.

How to vote

Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions