AWS Lambda and LaunchDarkly Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build developer tools workflows between AWS Lambda and LaunchDarkly on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about AWS Lambda and LaunchDarkly

Detailed info you need to know about AWS Lambda and LaunchDarkly integrations in WEXTL. Explore which modules apps support and how you connect them.

  • AWS Lambda

    • Developer Tools
    • 1 trigger
    • 38 searches
    • 49 actions

    Serverless compute that runs your code without managing servers.[5]

  • LaunchDarkly

    • Developer Tools
    • 2 triggers
    • 66 searches
    • 76 actions

    Feature flag and release management.[6]

How to connect AWS Lambda to LaunchDarkly

Set up your AWS Lambda and LaunchDarkly integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between AWS Lambda and LaunchDarkly work in WEXTL?

WEXTL exposes actions and triggers for AWS Lambda and LaunchDarkly that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

AWS Lambda triggersLaunchDarkly actions

AWS Lambda modules

  • Watch Durable Executions Polls a function and fires once for every durable execution that began since the previous check. Use Status to watch only one state, and Limit for how many the first check emits.
  • Add a Function Permission Lets another service, account or role use a function by adding a statement to its resource policy. Use Action and Principal to say who may do what, and Source ARN to limit it to one calling resource.
  • Add a Layer Version Permission Shares a layer version with an account by adding a policy statement. Use Principal * with Organization ID to open it to one organization, and Revision ID to skip the change if the policy moved on since you read it.
  • Add Tags to a Resource Attaches Tags to the resource behind the Resource ARN. A tag whose key already exists gets the new value.
  • Cancel a Durable Execution Stops a durable execution. Use Error Message to record why it was stopped, and Error Type, Error Data or Stack Trace to attach error details. Output is the Stop Timestamp.
  • Create a Capacity Provider Sets up a capacity provider that runs functions on compute instances in your own subnets. It needs VPC Config and Permissions Config. Use Scaling Config to set how it scales and Instance Requirements to limit the instance types.
  • Create a Code Signing Config Defines which signing profiles may sign code for functions, through Allowed Publishers. Use Code Signing Policies to decide what happens when a signature check fails.
  • Create a Durable Execution Checkpoint Saves progress of a durable execution against its current Checkpoint Token. Use Updates for state changes such as completing a step or starting a wait. Output includes the next Checkpoint Token.
  • Create a Function Deploys a new Lambda function under a Role, from your Code. For zip packages add a Runtime and Handler, and for container images an image URI. Use Timeout and Memory Size to replace the defaults of 3 seconds and 128 MB.
  • Create a Function URL Config Gives a function a dedicated HTTPS endpoint. Use Auth Type to choose between AWS IAM and open access, Invoke Mode for buffered or streamed answers, and Cors for cross-origin rules.
  • Create an Alias Adds a named alias that points to a version of a function. Use Routing Config to send a share of the traffic to a second version.
  • Create an Event Source Mapping Connects a function to a stream, queue or broker and has records delivered in batches. Use Event Source ARN for a Kinesis or DynamoDB stream, an SQS queue or another source, and Batch Size to bound each batch.
  • Delete a Capacity Provider Removes a capacity provider from the account and returns its final Capacity Provider record.
  • Delete a Code Signing Config Deletes a code signing config from your Lambda account.
  • Delete a Function Deletes a function. Use Qualifier to delete a single version, otherwise the function goes with all of its versions and aliases.
  • Delete a Function Code Signing Config Unlinks a function from the code signing config that it was bound to.
  • Delete a Function Concurrency Clears the reserved concurrency set on a function.
  • Delete a Function Event Invoke Config Removes the retry and destination settings for asynchronous calls. Use Qualifier to target a version or alias, or leave it empty for the latest version.
  • Delete a Function URL Config Removes the HTTPS endpoint of a function, or of one alias when Qualifier names it.
  • Delete a Layer Version Deletes a numbered version of a layer from Lambda.
  • Delete a Provisioned Concurrency Config Removes the warm capacity set on one version or alias, chosen with Qualifier.
  • Delete a Resource Policy Removes the policy that sits on a function or layer version. Use Revision ID to delete only if the current revision matches, or leave it empty to delete regardless.
  • Delete an Alias Deletes one alias of a function by its name.
  • Delete an Event Source Mapping Removes the link between a function and its stream, queue or broker. The final mapping settings are returned.
  • Get a Capacity Provider Looks up a capacity provider and returns its full Capacity Provider record.
  • Get a Code Signing Config Retrieves a code signing config, including its allowed publishers and policy, as Code Signing Config.
  • Get a Durable Execution Shows the status of one durable execution with its start and end timestamps. Turn off Include Execution Data to leave out the input, result and error and get a smaller response.
  • Get a Durable Execution History Lists the events recorded for a durable execution, such as when it started, succeeded or failed. Use Newest First to reverse the order, and Include Execution Data to turn step results and callback payloads on or off.
  • Get a Durable Execution State Returns the operations of a durable execution as of a given Checkpoint Token, with the Status and details of each step, wait or callback. Use Limit to bound a run.
  • Get a Function Returns a function in full, with its Configuration, Code details and Tags. Add a Qualifier to read one version or alias, and expect environment variable values in the output.
  • Get a Function Code Signing Config Checks which code signing config is attached to a function and returns its Code Signing Config ARN.
  • Get a Function Concurrency Looks up how many concurrent executions are reserved for a function, as Reserved Concurrent Executions.
  • Get a Function Configuration Pulls the settings of a function, such as its Runtime, Handler, Timeout and Memory Size, without the code details. Add a Qualifier to pick a version or alias, and environment variable values are included.
  • Get a Function Event Invoke Config Reads how a function handles asynchronous calls: Maximum Retry Attempts, Maximum Event Age In Seconds and the Destination Config.
  • Get a Function Policy Returns the resource-based policy of a function as Policy, along with its Revision ID for later guarded changes.
  • Get a Function Recursion Config Shows what Lambda does with a function that calls itself in a loop, as the Recursive Loop setting.
  • Get a Function Scaling Config Returns the Applied Function Scaling Config and the Requested Function Scaling Config of a given version or alias.
  • Get a Function URL Config Reads the function URL configuration of a function. Output includes the Function URL, Auth Type, Invoke Mode and Cors.
  • Get a Layer Version Retrieves one version of a layer, its Description, Compatible Runtimes and License Info, plus a Content location.
  • Get a Layer Version by ARN Looks up a layer version from its full Layer Version ARN, including its Description, Compatible Runtimes and License Info.
  • Get a Layer Version Policy Returns the permissions granted on a layer version as Policy, together with its Revision ID.
  • Get a Provisioned Concurrency Config Checks warm capacity of a function alias or version. It compares Requested Provisioned Concurrent Executions with Available Provisioned Concurrent Executions and gives the Status.
  • Get a Resource Policy Reads the access policy of a Lambda function or layer version, found from its Resource ARN. Output includes the Policy and Revision ID.
  • Get a Runtime Management Config Shows how a function picks up runtime updates through Update Runtime On, along with its Runtime Version ARN.
  • Get Account Settings Reads the Lambda limits for your account together with how much of them is in use, as Account Limit and Account Usage.
  • Get an Alias Fetches an alias of a function, giving the version it points to, its Routing Config and its Revision ID.
  • Get an Event Source Mapping Reads the settings of a mapping between a function and an event source, such as its Batch Size and Starting Position.
  • Invoke a Function Runs a Lambda function with a JSON Payload as its input, up to 6 MB. Use Invocation Type to wait for the result or return at once, and Qualifier to run a version or alias. Turn off Stop On Function Error to branch on failures.
  • List Aliases Shows the aliases of one function, each with its Name, Function Version and Routing Config. Use Function Version to keep only aliases that point to one version.
  • List Capacity Providers Lists the capacity providers of your account along with their State and VPC Config. Use State to keep only providers in one state.

LaunchDarkly modules

  • Add a Flag Follower Subscribes a member to a feature flag in one environment of a LaunchDarkly project. Output includes the Flag Key and Member ID.
  • Add a Flag Prerequisite Sets up a dependency between flags using Prerequisite Flag and Prerequisite Variation. Add a Comment for the history of the change.
  • Add a Member to Teams Puts an account member into one or more teams at once. Output includes the Role, Email and Teams of the member.
  • Add Flag Targets Serves one Variation of a feature flag to chosen Context Keys. Set Context Kind for a kind other than user, and add a Comment for the change history.
  • Add Members by Email Sends invitations to a list of Emails, giving every invitee the same base Role. Add Custom Roles or Teams to give invitees extra roles and team places. Blank rows are skipped.
  • Add Segment Excluded Targets Excludes Context Keys of one Context Kind from a segment. A key cannot be both included and excluded, and up to 1,500 keys go in per call.
  • Add Segment Included Targets Includes Context Keys of a given Context Kind in a segment. Each call takes up to 1,500 keys, and you can add a Comment to explain the change.
  • Apply an Approval Request Applies an approval request so its changes take effect. Add a Comment to describe the change.
  • Archive a Feature Flag Archives a feature flag in a project. Use Comment to record the reason in the history.
  • Copy Feature Flag Settings Copies flag targeting from the From Environment over to the To Environment, overwriting what is there. Use Only Copy to move only some parts, or leave it empty to copy everything.
  • Create a Big Segment Export Starts exporting a big segment of one environment. Output includes the Export ID.
  • Create a Code Reference Repository Registers a repository for code references under a Name. Use Type for where it is hosted, Source Link for its address, and Default Branch for the main branch.
  • Create a Custom Role Defines a role with a Name, a Key that cannot be changed later, and a Policy of statements. Each statement lists Actions and Resources to allow or deny.
  • Create a Feature Flag Makes a feature flag from a Name and Key. Set Flag Type to boolean for automatic true and false variations, or to string or number and list your own Variations. Turn on Temporary for a flag you will remove later.
  • Create a Flag Approval Request Opens an approval request for a flag Change. Use Description to tell reviewers what changes and why, Notify Members and Notify Teams to ask people to review, and Run At to apply it once approved.
  • Create a Flag Link Links a flag to an outside address, a feature LaunchDarkly marks as beta. Give the link a Title and a Deep Link, and add a Description, Integration Key or Key if needed.
  • Create a Flag Trigger Creates a trigger URL for a flag in one environment. Use Integration to say who calls it and Action to turn the flag on or off when it is called. The result includes the Trigger URL.
  • Create a Metric Defines a metric for experiments. Give it a Name, Key and Kind, and use Success Criteria to say whether a higher or lower value counts as a win.
  • Create a Project Starts a new project with its environments, under a Name plus a Key that cannot be changed later. Add Tags, and enable Include Flags in Client-side Snippets to make new flags available to client-side snippets by default.
  • Create a Segment Sets up a segment for one environment under a Name and Key. Turn on Big Segment for a very large list of context keys, which needs a Big Segment Context Kind.
  • Create a Team Forms a new team. Give it a Name and a Key that cannot be changed later. Use Members to add people and Custom Roles for the roles the team grants to its members.
  • Create a Webhook Registers a webhook that posts LaunchDarkly changes to a URL. Use Resource Kind to say which changes are sent and turn on Sign Requests to sign each delivery. The result also shows the Secret.
  • Create an Access Token Issues an access token that has a Name and Role. The token value is shown once. Turn on Service Token to tie it to the account instead of a member, and use Expires At to end it on a date.
  • Create an Environment Sets up an environment inside a project. Give it a Name, Key and Color, and use Copy Settings From to start from an existing environment. Use Default TTL to set how many minutes clients cache flag values.
  • Delete a Code Reference Repository Deletes a repository that was registered to report code references.
  • Delete a Custom Role Removes a custom role defined from policy statements.
  • Delete a Data Export Destination Removes a data export destination from one environment of a project.
  • Delete a Feature Flag Removes a feature flag from its project. No undo exists.
  • Delete a Flag Link Removes a link attached to a flag, a feature LaunchDarkly marks as beta.
  • Delete a Flag Trigger Deletes a trigger URL attached to a flag in one environment.
  • Delete a Flag Workflow Removes a release workflow belonging to a flag, in one of its environments.
  • Delete a Member Deletes a person from your LaunchDarkly account.
  • Delete a Metric Removes a metric used by experiments in a project.
  • Delete a Project Removes a project, the container of environments and flags, from LaunchDarkly.
  • Delete a Relay Proxy Config Removes a Relay Proxy configuration from your account.
  • Delete a Scheduled Flag Change Removes a change scheduled for a flag in an environment.
  • Delete a Segment Deletes a segment belonging to an environment.
  • Delete a Team Deletes a team, the group that holds members and roles.
  • Delete a Webhook Removes a webhook that delivers LaunchDarkly changes to a URL.
  • Delete an Access Token Deletes an access token from LaunchDarkly, whether it is a member token or a service token.
  • Delete an Application Deletes an application, a feature LaunchDarkly marks as beta.
  • Delete an Approval Request Deletes an approval request that is waiting for a decision or is approved but not yet applied.
  • Delete an Environment Deletes one of the environments listed under a project.
  • Evaluate Flags for Context Evaluates all flags of an environment for one context, built from Context Kind and Context Key. Add Attributes for extra attributes that targeting rules read. Each value comes with its Reason.
  • Get a Big Segment Export Looks up the status of a big segment export started earlier, with its Size Bytes and Creation Time.
  • Get a Big Segment Membership for Context Checks whether a context belongs to a big segment, using Context Key. Output says whether it is Included or Excluded.
  • Get a Code Reference Repository Pulls the Source Link, Type and Default Branch of a code reference repository.
  • Get a Custom Role Reads a custom role, covering its Policy, Base Permissions and Assigned To.
  • Get a Data Export Destination Reads a data export destination of an environment, with its Kind, Config and whether it is On.
  • Get a Feature Flag Returns a feature flag with its targeting. Use Environment to limit the settings to that environment alone.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with AWS Lambda and LaunchDarkly integrations. Pick any from the list below if the current combination isn't the one you need.

Automate AWS Lambda and LaunchDarkly on WEXTL®

Claim your 3-day trial to build AWS Lambda with LaunchDarkly integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Lambda and LaunchDarkly.

How do I connect AWS Lambda and LaunchDarkly?

Connect your AWS Lambda and LaunchDarkly accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between AWS Lambda and LaunchDarkly?

Example: when the "Watch Durable Executions" trigger in AWS Lambda fires, WEXTL can "Add a Flag Follower" in LaunchDarkly. AWS Lambda has 1 trigger (including Watch Durable Executions). LaunchDarkly has 142 actions (including Add a Flag Follower, Add a Flag Prerequisite, and Add a Member to Teams). Add filters and transforms between steps when you need them.[1]

Can AWS Lambda trigger actions in LaunchDarkly, and LaunchDarkly in AWS Lambda?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate AWS Lambda and LaunchDarkly?

No. AWS Lambda-to-LaunchDarkly automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does AWS Lambda integrate with LaunchDarkly in real time?

Yes. Trigger-based automations start the moment AWS Lambda (or LaunchDarkly) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a AWS Lambda + LaunchDarkly integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect AWS Lambda with LaunchDarkly?

You can build your AWS Lambda + LaunchDarkly automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the AWS Lambda and LaunchDarkly integration.

  1. AWS Lambda and LaunchDarkly integration source code, module specs and credentials implementation.
  2. Our AWS Lambda and LaunchDarkly integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for AWS Lambda and LaunchDarkly, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. AWS Lambda integration information
  6. LaunchDarkly integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted AWS Lambda and LaunchDarkly integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore AWS Lambda and LaunchDarkly, or get started