AWS Cognito and Better Stack Integration

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

Keep AWS Cognito and Better Stack matched by integrating their events and actions. When developer tools events happen in AWS Cognito, update the Better Stack automatically - without any line of code in visual workflow builder.

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

Learn about AWS Cognito and Better Stack

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

  • AWS Cognito

    • Developer Tools
    • 45 searches
    • 88 actions

    Amazon Cognito User Pools. Manage users, groups, app clients and identity providers with SigV4.[5]

  • Better Stack

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

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

How to connect AWS Cognito to Better Stack

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

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

WEXTL exposes actions and triggers for AWS Cognito 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.

Better Stack triggersAWS Cognito actions

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.

AWS Cognito modules

  • Add a User Pool Client Secret Creates a secret for an app client of a user pool. Output has the Client Secret ID and the Secret Value.
  • Add Custom Attributes Extends the schema of a user pool with new custom attributes. Use Custom Attributes to supply one SchemaAttributeType object per attribute.
  • Admin Add User To Group Puts a user of the pool into a group, naming the user by Username and the group by Group Name.
  • Admin Confirm Sign Up Confirms a pending registration for a Username without the user entering a code. Use Client Metadata to pass key-value data on to your Lambda triggers.
  • Admin Create User Creates a user in a pool under a chosen Username. Leave Temporary Password empty and Cognito generates one, and use Message Action to suppress or resend the welcome message. Output includes the User Status.
  • Admin Delete Software Token Deletes the software token that a user has set up for MFA sign-in.
  • Admin Delete User Deletes a user account from a Cognito user pool, acting as an administrator on the pool.
  • Admin Delete User Attributes Removes the attributes listed under User Attribute Names from one user of a pool.
  • Admin Disable Provider For User Unlinks a federated sign-in provider from a user. Use User to give the ProviderName, ProviderAttributeName and ProviderAttributeValue of the link.
  • Admin Disable User Disables a user so the account is switched off in the pool.
  • Admin Enable User Re-enables a user whose account was switched off in the pool.
  • Admin Forget Device Makes Cognito forget a remembered device of a user, found by Device Key.
  • Admin Get Device Reads one remembered device of a user by Device Key. Output has its Created Date, plus Last Authenticated.
  • Admin Get User Looks up a user in a pool by Username. Output has their User Attributes, Enabled flag and User Status.
  • Admin Get User Auth Factors Lists the sign-in factors a user has set up, returned as Factors.
  • Admin Initiate Auth Starts a sign-in on behalf of a user with the Auth Flow of your choice. Use Auth Parameters for values such as the username and password, and Session to continue an earlier challenge. Output has a Challenge Name or an Authentication Result.
  • Admin Link Provider For User Links a federated user to an existing native user. Use Destination User for the native account and Source User for the federated one.
  • Admin List Devices Lists the remembered devices of a user. Output has the Device Key and Last Authenticated of each. Use Limit to read only part of the list.
  • Admin List Groups For User Shows the groups a user belongs to, with each Group Name, Role ARN and Precedence. Use Limit to read fewer groups.
  • Admin List User Auth Events Reads the sign-in activity recorded for a user. Each event has an Event ID, Event Type and Event Response, up to the Limit.
  • Admin Remove User From Group Removes a user from a group in a Cognito user pool, ending the membership.
  • Admin Reset User Password Forces a password reset for a user in the pool. Use Client Metadata to pass data on to your Lambda triggers.
  • Admin Respond To Auth Challenge Answers a challenge raised by Admin Initiate Auth, such as MFA, by giving the Challenge Name and Challenge Responses. Reuse the Session it returned. Output includes the Authentication Result.
  • Admin Set User MFAPreference Sets which MFA methods a user has turned on and which is preferred. Use SMS MFA Settings, Software Token MFA Settings and Email MFA Settings, each with Enabled and PreferredMfa.
  • Admin Set User Password Sets a fixed Password for a user. Turn on Permanent to keep it, otherwise it is temporary and the user must change it at the next sign-in.
  • Admin Set User Settings Sets the MFA delivery options of a user. Use MFA Options to give the delivery medium and attribute name pairs.
  • Admin Update Auth Event Feedback Marks a recorded sign-in event as Valid or Invalid with Feedback Value. Use Event ID to say which event is being rated.
  • Admin Update Device Status Marks the device with a Device Key as remembered or not remembered, using Device Remembered Status.
  • Admin Update User Attributes Changes attributes of a user with User Attributes, a list of name and value pairs. Use Client Metadata to pass data on to your Lambda triggers.
  • Admin User Global Sign Out Signs a user out everywhere by invalidating every session the user has in the pool.
  • Associate a Software Token Begins authenticator-app MFA setup for a user, using either an Access Token or the Session of a sign-in challenge. Output has the Secret Code for the app and a new Session.
  • Change Password Changes the password of the user who owns the Access Token. Use Proposed Password to set the new one.
  • Complete a Web Authn Registration Finishes passkey registration by sending the Credential response created by the authenticator, along with the Access Token of the user.
  • Confirm a Device Confirms a new device for a user by its Device Key. Use Device Name for a friendly name and Device Secret Verifier Config for the SRP verifier. Output has User Confirmation Necessary.
  • Confirm a Forgot Password Completes a forgotten-password flow by sending the Confirmation Code the user received together with a new Password for the Username. Add a Secret Hash when the app client has a secret.
  • Confirm a Sign Up Verifies a new registration with the Confirmation Code the user was sent. Use Force Alias Creation to take over an alias that already exists.
  • Create a Group Adds a group to a user pool under a Group Name. Use Role ARN to link an IAM role for members and Precedence to rank groups, where a lower number wins.
  • Create a Managed Login Branding Creates the branding of the managed login pages for an app client. Set Use Cognito Provided Values to true to inherit Cognito defaults, or supply Settings and Assets of your own. The response includes the Branding ID.
  • Create a Resource Server Registers an OAuth 2.0 resource server under an Identifier URI and a Name. Use Scopes to list the custom scopes, each with a ScopeName and ScopeDescription.
  • Create a Terms Creates a terms agreement for an app client, named with Terms Name. Use Terms Source to point to HTML in S3 or supply plain text, and set Enforcement to OPTIONAL or REQUIRED. You get the Terms ID.
  • Create a User Import Job Prepares a bulk import of users, labelled with a Job Name and logging through the CloudWatch Logs Role ARN. The Job ID and its Status are in the response.
  • Create a User Pool Creates a Cognito user pool named by Pool Name. Use Auto Verified Attributes, Username Attributes and MFA Configuration for sign-in rules, and Deletion Protection to guard the pool. The response gives the pool its ID.
  • Create a User Pool Client Adds an app client to a pool under a Client Name. Set Generate Secret to true for a client secret, and use Refresh Token Validity, Access Token Validity and ID Token Validity for token lifetimes. The response includes the Client ID.
  • Create a User Pool Domain Sets up a domain for a pool, either a prefix or a custom FQDN entered as Domain. Use Custom Domain Config to attach the certificate for a custom domain. Output includes the CloudFront Domain.
  • Create a User Pool Replica Copies a user pool into the AWS region given as Region Name. The replica comes with its own ID, Name and Status.
  • Create an Identity Provider Adds a federated provider to a pool from a Provider Name, a Provider Type such as SAML, Google or OIDC, and its Provider Details. Use Attribute Mapping to map provider attributes onto pool attributes.
  • Delete a Group Deletes a group from a Cognito user pool.
  • Delete a Managed Login Branding Deletes a managed login branding configuration from a user pool.
  • Delete a Resource Server Removes an OAuth resource server from a user pool.
  • Delete a Terms Deletes a terms agreement from a Cognito user pool.

Explore alternative integrations

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

Automate AWS Cognito and Better Stack on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting AWS Cognito and Better Stack.

How do I connect AWS Cognito and Better Stack?

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

Example: when the "Watch Events" trigger in Better Stack fires, WEXTL can "Add a User Pool Client Secret" in AWS Cognito. AWS Cognito has 133 actions (including Add a User Pool Client Secret, Add Custom Attributes, and Admin Add User To Group). 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 Cognito trigger actions in Better Stack, and Better Stack in AWS Cognito?

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 Cognito and Better Stack?

No. AWS Cognito-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 Cognito integrate with Better Stack in real time?

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

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

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

Explore AWS Cognito and Better Stack, or get started