AWS Lambda and Better Stack Integration

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

Build developer tools workflows between AWS Lambda and Better Stack 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 Better Stack

Detailed info you need to know about AWS Lambda and Better Stack 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]

  • Better Stack

    • Developer Tools
    • 2 triggers
    • 59 searches
    • 77 actions

    Uptime monitoring, incident management and status pages.[6]

How to connect AWS Lambda to Better Stack

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

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

WEXTL exposes actions and triggers for AWS Lambda and Better Stack 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 triggersBetter Stack 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.

Better Stack modules

  • Change the Incident Status Moves an incident to a new state: Action offers Acknowledge, Resolve and Reopen. Use By to record who made the change. The updated incident is returned.
  • Change the Role of a Team Member Gives an existing team member a different Role, taken from your list of roles. Use Member to say whose role changes.
  • Create a Catalog Attribute Gives a catalog relation another attribute under a Name. Turn on Primary to match it against the incident metadata key of the same name, and give a Position to order it, lowest first.
  • Create a Catalog Record Stores one record in a catalog relation. Fill Attributes with one row per attribute, each row holding its values.
  • Create a Catalog Relation Defines a catalog relation under a Name, with an optional Description. Set Match Rule to apply a record when any primary value or every primary value matches the incident metadata.
  • Create a Heartbeat Sets up a heartbeat that expects a ping every Expected Every seconds and counts one as missed after the Grace Period. Choose an Escalation Policy to decide who is alerted, or alert the on-call person with the e-mail, SMS or Call switches.
  • Create a Heartbeat Group Starts a group for heartbeats under a Name. Sort it among the other groups with Position, or begin with every heartbeat inside it paused by using Paused.
  • Create a Monitor Starts a monitor that checks a chosen Monitor Type against a URL or Host. Use Check Frequency and Regions to set how often and where it runs, and Escalation Policy to decide who is alerted.
  • Create a Monitor Group Sets up a home for monitors under a Name. Turn on Paused to pause every monitor in that group.
  • Create a Severity Defines a severity level that decides how people are notified when an incident of that level opens. Pick channels with Send SMS, Call, Send E-mail, Send Push Notification and Send Critical Alert, and file it under a Severity Group.
  • Create a Severity Group Adds a named group for severities, shown in the dashboard. Use Position to order it in the list, lowest first.
  • Create a Status Page Creates a status page for your company from a Company Name, Time Zone and Subdomain, which must be unique across Better Stack. Add a Custom Domain, a Design, History Days or a Password to shape who sees what.
  • Create a Status Page Group Creates a named group for status pages, shown in the dashboard. Use Position to place it in the list.
  • Create a Status Page Report Publishes a report with a Title and the first status update Message. Choose a Report Type, either a manual incident or planned maintenance, and turn on Notify Subscribers to e-mail them.
  • Create a Status Page Resource Adds an item to a status page based on its Resource Type, shown there under the Public Name. Use Mark as Down When and Mark as Degraded When to define how an incident affects it.
  • Create a Status Page Section Sets up a section for grouping the items of a status page. Leave Name blank to hide its header, and use Position with Fixed Position to place it exactly.
  • Create a Status Page Subscriber Subscribes an E-mail address to the updates of a status page.
  • Create a Status Update Posts a follow-up on a status page report with the text from Message. Use Affected Resources for a manual report and leave it out for maintenance. Turn on Notify Subscribers to send an e-mail.
  • Create an Escalation Policy Group Makes a group for escalation policies, shown in the dashboard under its Name. Use Position to place it in the list, lowest first.
  • Create an Incident Opens an incident on behalf of a Requester E-mail, described by its Summary. Add a Name, a longer Description and an Escalation Policy, or alert the on-call person with Send E-mail, Send SMS or Call.
  • Create an Incident Comment Posts a Comment on an incident, with Markdown supported. Set Tag Member to notify a colleague about it. The new comment is returned.
  • Create an Incoming Webhook Creates a webhook endpoint that raises incidents from outside requests. Give it a Name and an Escalation Policy, and set Recovery Period for how long to wait after a resolving request. Start, Acknowledge and Resolve rules decide when each happens.
  • Create an On-Call Event Puts people on call for a stretch of time on a schedule, between Starts At and Ends At. Everyone chosen as On-Call Users must belong to the schedule team. Turn on Override so the event beats regular scheduled ones.
  • Create an On-Call Rotation Rotates On-Call Users through a schedule, each person on call for the Rotation Length counted in the chosen Interval. Rotations run from Start At to End At. Use Working Hours to restrict when anyone is paged.
  • Create an On-Call Schedule Creates a new on-call schedule under a Name, which can then hold events and rotations.
  • Delete a Catalog Attribute Deletes an attribute that belongs to a catalog relation.
  • Delete a Catalog Record Removes a record that belongs to one catalog relation.
  • Delete a Catalog Relation Deletes a catalog relation, the set of attributes and records matched against incident metadata.
  • Delete a Heartbeat Removes a heartbeat that expects regular pings.
  • Delete a Heartbeat Group Deletes a group that can pause and organise heartbeats together.
  • Delete a Monitor Deletes a monitor that checks a website, server or port.
  • Delete a Monitor Group Removes a group that holds monitors and can pause them together.
  • Delete a Severity Removes a severity level used to decide how people are notified of new incidents.
  • Delete a Severity Group Deletes a dashboard group that holds severity levels.
  • Delete a Status Page Removes the status page on which visitors check the health of your services. Check first, it is final.
  • Delete a Status Page Group Deletes a dashboard group that collects status pages.
  • Delete a Status Page Report Removes a report, either an incident or planned maintenance, from a status page.
  • Delete a Status Page Resource Deletes an item from a status page, found by Status Page and Resource.
  • Delete a Status Page Section Removes a section that groups the items of a status page.
  • Delete a Status Page Subscriber Unsubscribes an e-mail address from the updates of a status page.
  • Delete a Status Update Deletes one update that was posted under a status page report.
  • Delete an Escalation Policy Removes an escalation policy, the setting that decides who gets alerted.
  • Delete an Escalation Policy Group Deletes a dashboard group used to organise escalation policies.
  • Delete an Incident Removes an incident from your Better Stack account. Plan on it being final.
  • Delete an Incident Comment Deletes a note that was posted in the thread of an incident.
  • Delete an Incoming Webhook Removes an incoming webhook that raises incidents from outside requests.
  • Delete an On-Call Event Deletes a single on-call shift that was added to a schedule.
  • Delete an On-Call Rotation Removes the rotation configured on an on-call schedule.
  • Delete an On-Call Schedule Deletes an on-call schedule that people can be placed on through events and rotations.
  • Get a Catalog Attribute Reads an attribute of a catalog relation, including whether it is primary and where it is positioned.

Explore alternative integrations

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

Automate AWS Lambda and Better Stack on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Lambda and Better Stack.

How do I connect AWS Lambda and Better Stack?

Connect your AWS Lambda and Better Stack 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 Better Stack?

Example: when the "Watch Durable Executions" trigger in AWS Lambda fires, WEXTL can "Change the Incident Status" in Better Stack. AWS Lambda has 1 trigger (including Watch Durable Executions). Better Stack has 136 actions (including Change the Incident Status, Change the Role of a Team Member, and Create a Catalog Attribute). Add filters and transforms between steps when you need them.[1]

Can AWS Lambda trigger actions in Better Stack, and Better Stack 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 Better Stack?

No. AWS Lambda-to-Better Stack 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 Better Stack in real time?

Yes. Trigger-based automations start the moment AWS Lambda (or Better Stack) 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 + Better Stack 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 Better Stack?

You can build your AWS Lambda + Better Stack 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 Better Stack integration.

  1. AWS Lambda and Better Stack integration source code, module specs and credentials implementation.
  2. Our AWS Lambda and Better Stack integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for AWS Lambda and Better Stack, 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. Better Stack 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 Better Stack integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore AWS Lambda and Better Stack, or get started