AWS Lambda and Buildkite Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Connect AWS Lambda and Buildkite to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about AWS Lambda and Buildkite
Detailed info you need to know about AWS Lambda and Buildkite integrations in WEXTL. Explore which modules apps support and how you connect them.
AWS Lambda

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

Continuous integration and delivery platform for running fast, secure pipelines.[6]
How to connect AWS Lambda to Buildkite
Set up your AWS Lambda and Buildkite integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect AWS Lambda and Buildkite
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected AWS Lambda and Buildkite nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between AWS Lambda and Buildkite. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between AWS Lambda and Buildkite work in WEXTL?
WEXTL exposes actions and triggers for AWS Lambda and Buildkite 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 triggersBuildkite 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.
Buildkite modules
- Add a Cluster Maintainer Makes a user or a team a maintainer of a cluster. Use User or Team ID with the UUID of the user from List Members or of the team from List Teams.
- Add a Pipeline Webhook Registers a Buildkite webhook on the repository of a pipeline and reports Success with the Pipeline.
- Add a Team Member Puts a member of the organization into a team under a given Role. Returns the team membership with its Created at time and User.
- Add a Team Pipeline Links a pipeline to a team at a chosen Access Level. Returns the link with its Created at time.
- Add a Team Suite Gives a team access to a test suite at a chosen Access Level and returns the link with its Created at time.
- Archive a Pipeline Archives a pipeline. Unarchive a Pipeline reverses it.
- Cancel a Build Cancels a build of a pipeline and returns the canceled build with its State and Number.
- Cancel a Job Cancels one job of a build and returns it with its Type, Name and Step key.
- Create a Build Triggers a build for a Pipeline at a Commit on a Branch. Add Environment Variables and Meta Data, or Pull Request fields, to shape the run.
- Create a Build Annotation Writes an annotation with a Body on the page of a build, with a Style and a Context. Turn on Append to extend an existing one.
- Create a Cluster Creates a cluster with a Name to group agents and queues. Use Emoji and Color to style it, and Maintainers (JSON) to set who maintains it.
- Create a Cluster Secret Stores a secret Value in a Cluster under a Key that builds use to read it. Add a Policy to attach an access policy.
- Create a Hosted Queue Sets up a queue on Buildkite hosted agents of the chosen Instance Shape, under a Key, inside a Cluster.
- Create a Job Annotation Writes an annotation with a Body on one job, with a Style and Priority. Turn on Append to extend an annotation that has the same Context.
- Create a Pipeline Sets up a pipeline from a Name, a Repository and a Configuration (YAML). Use Default Branch to name the main branch, Tags to label it and Skip Queued Branch Builds to drop queued builds of a branch when a newer build starts.
- Create a Pipeline Schedule Schedules recurring builds of a pipeline on a Cron Line, labeled with Label. Set Branch and Commit to choose what each scheduled build runs.
- Create a Pipeline Template Saves a Name and Configuration (YAML) as a template. Turn on Available to offer it when people create pipelines.
- Create a Pipeline Trigger Gives a pipeline an incoming trigger under a Label. Use Build (JSON) for the build settings, Verification (JSON) for a verification secret, and choose the Type carefully because it cannot be changed after creation.
- Create a Rule Adds an organization rule of one Type with the Value (JSON) that defines it.
- Create a Self-Hosted Queue Sets up a queue under a Key for agents you run yourself, inside a Cluster. Turn on Use GitHub App Token to use that token for checkouts.
- Create a Team Starts a team in the organization under a Name. Turn on Members Can Create Test Suites to let its members create suites.
- Create a Test Suite Creates a test suite in Test Engine with a Name. Use Team IDs to give teams access to it and Show API Token to get the suite API token back once.
- Create an Agent Token Issues a token that lets agents register in a Cluster. Use Allowed IP Addresses to limit where it works from, Expires At to set an end date, and Allowed Queue IDs or Allow All Queues for queue access. The token value is shown only once.
- Create Invitations Invites people by their Emails to join the organization, with a Role and optional Teams.
- Delete a Build Annotation Removes an annotation from the page of a build in Buildkite.
- Delete a Cluster Deletes the cluster that groups agents and queues in your organization.
- Delete a Cluster Secret Removes a secret that was stored for the agents of a cluster.
- Delete a Job Annotation Deletes an annotation that appears on the page of one job.
- Delete a Job Log Removes the log output that a job produced.
- Delete a Pipeline Deletes a pipeline that builds a repository in your Buildkite organization.
- Delete a Pipeline Schedule Removes a recurring schedule from a pipeline.
- Delete a Pipeline Template Removes a pipeline template from the templates of your Buildkite organization.
- Delete a Pipeline Trigger Removes an incoming trigger from a pipeline.
- Delete a Queue Removes an agent queue, hosted or self-hosted, from its cluster.
- Delete a Rule Deletes one rule that is set on the organization.
- Delete a Team Disbands a team defined in your organization.
- Delete a Test Suite Deletes a test suite recorded in Test Engine for your organization.
- Delete an Artifact Deletes an artifact that a job uploaded.
- Disable the GitHub Webhook Processing Stops Buildkite from acting on GitHub webhooks for a pipeline.
- Enable a Test Turns a test back on after it was muted or skipped. The returned test has its Scope and Name.
- Enable the GitHub Webhook Processing Lets Buildkite act on GitHub webhooks for a pipeline again.
- Find a Test Looks up a test in a Test Suite through its Scope and Name, returning matching tests with their ID and Web url.
- Get a Build Fetches a single build. Turn on Include Jobs to add its jobs, or Include Test Engine Data to add Test Engine data to the output.
- Get a Cluster Opens a cluster and reports its Default queue id, Name and Description.
- Get a Cluster Maintainer Pulls one maintainer entry of a cluster, showing whether the Actor type is a user or a team and its Actor id.
- Get a Cluster Secret Returns the settings of a cluster secret, such as its Key, Description and Policy.
- Get a Job Loads one job and returns its Type, Name and Step key.
- Get a Job Log Downloads the output a job logged, with its Content, Size and Header times.
- Get a Member Opens an organization member and shows their Role and Sso mode.
- Get a Pipeline Retrieves a pipeline and shows its Name together with its URL and Web url.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with AWS Lambda and Buildkite integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting AWS Lambda and Buildkite.
References
List of sources used to gather information about the AWS Lambda and Buildkite integration.
- AWS Lambda and Buildkite integration source code, module specs and credentials implementation.
- Our AWS Lambda and Buildkite integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AWS Lambda and Buildkite, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- AWS Lambda integration information
- Buildkite integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted AWS Lambda and Buildkite integration page documentation. Used sources, the role of AI, and how the team validates the result.