AppsPricingBlogTry it
AWS logo
PagerDuty logo

Connect AWS to PagerDuty

Automate workflows and sync data between AWS and PagerDuty with AI-powered automation

5-minute setup
Enterprise secure
No coding required

Why Connect AWS & PagerDuty?

Intelligent Automation Workflows

Leverage 12 available triggers from AWS to execute 24 targeted actions in PagerDuty automatically.

Eliminate Manual Data Entry

Replace time-consuming manual processes with intelligent automation that keeps AWS and PagerDuty perfectly synchronized.

Real-time Business Intelligence

Create a unified data flow between AWS and PagerDuty for instant insights and improved decision-making across your tech stack.

Available Triggers & Actions

AWS logo

AWS

Triggers (12)

New Scheduled Tasks

Creates a Step Function State Machine to publish a message to an SNS topic at a specific timestamp. The SNS topic delivers the message to this Mazaal AI source, and the source emits it as a new event.

polling
New SNS Messages

Creates an SNS topic in your AWS account. Messages published to this topic are emitted from the Mazaal AI source.

polling
New Inbound SES Emails

The source subscribes to all emails delivered to a specific domain configured in AWS SES. When an email is sent to any address at the domain, this event source emits that email as a formatted event. These events can trigger a Mazaal AI workflow and can be consumed via SSE or REST API.

polling
New Deleted S3 File

Emit new event when a file is deleted from a S3 bucket

polling
New DynamoDB Stream Event

Emit new event when a DynamoDB stream receives new events. See the docs here

polling
New Records Returned by CloudWatch Logs Insights Query

Executes a CloudWatch Logs Insights query on a schedule, and emits the records as invidual events (default) or in batch

polling
New Restored S3 File

Emit new event when a file is restored into an S3 bucket

polling
New S3 Event

Emit new S3 events for a given bucket

polling
New S3 File

Emit new event when a file is added to an S3 bucket

polling
New Update to AWS RDS Database (Instant)

Emit new event when there is an update to an AWS RDS Database.

webhook
Redshift - New Row

Emit new event when a new row is added to a table. See the documentation

polling
Redshift - Updated Row

Emit new event when a row is updated, based on a selected timestamp column. See the documentation

polling

Actions (23)

CloudWatch Logs - Put Log Event

Uploads a log event to the specified log stream. See docs

DynamoDB - Create Table

Creates a new table to your account. See docs

DynamoDB - Execute Statement

This operation allows you to perform transactional reads or writes on data stored in DynamoDB, using PartiQL. See docs

DynamoDB - Get Item

The Get Item operation returns a set of attributes for the item with the given primary key. If there is no matching item, Get Item does not return any data and there will be no Item element in the response. See docs

DynamoDB - Put Item

Creates a new item, or replaces an old item with a new item. If an item that has the same primary key as the new item already exists in the specified table, the new item completely replaces the existing item. See docs

DynamoDB - Query

The query operation finds items based on primary key values. See docs

DynamoDB - Scan

The Scan operation returns one or more items and item attributes by accessing every item in a table. See docs

DynamoDB - Update Item

Updates an existing item's attributes, or adds a new item to the table if it does not already exist. See docs

DynamoDB - Update Table

Modifies the settings for a given table. Only one type of modification is permitted per request. See docs

EventBridge - Send Event to Event Bus

Sends an event to an EventBridge event bus. See documentation

Lambda - Create Function

Create a Lambda function from source code. This action creates a zip file and deploys it to AWS Lambda. See the docs

Lambda - Invoke Function

Invoke a Lambda function using the AWS API. See the docs

List AWS Region Options

Retrieves available options for the AWS Region field.

Redshift - Create Rows

Insert rows into a table. See the documentation

Redshift - Delete Rows

Deletes row(s) in an existing table in Redshift. See the documentation

Redshift - Query Database

Run a SELECT query on a database. See the documentation

Redshift - Update Rows

Update row(s) in an existing table in Redshift. See the documentation

S3 - Download File to /tmp

Downloads a file from S3 to the /tmp directory. See the documentation

S3 - Generate Presigned URL

Creates a presigned URL to download from a bucket. See the documentation

S3 - Upload Base64 As File

Accepts a base64-encoded string and a filename, then uploads as a file to S3. See the documentation

S3 - Upload Files

Upload files to S3. Accepts either a file URL, a local file path, or a directory path. See the documentation

SNS - Send Message

Sends a message to a SNS Topic. See docs

SQS - Send Message

Sends a message to an SQS queue. See the docs

PagerDuty logo

PagerDuty

Triggers (2)

New On-Call Rotation

Emit new event each time a new user rotates onto an on-call rotation

polling
New or Updated Incident

Emit new event each time an incident is created or updated

polling

Actions (24)

Acknowledge Incident

**Deprecated** — use **Update Incident** instead. Acknowledge an incident. See the documentation

Add Note to Incident

Add a text note to an incident. Notes are visible in the incident timeline and useful for documenting investigation steps, resolution details, or handoff notes. Use **List Incidents** or **Get Incident** to find the incident ID. See the documentation

Create Incident

Trigger a new incident on a PagerDuty service. Use **List Services** to find a service ID and **List Escalation Policies** to find a policy ID. Use **List Priorities** to find priority IDs. Set incidentKey to a stable value derived from the alert source (e.g. a hash of title + service ID) to prevent duplicate incidents on retry — PagerDuty deduplicates open incidents with the same key on the same service. See the documentation

Create Schedule Override

Override a schedule layer to assign a specific user for a time window. Use **List Schedules** to find a schedule ID and **List Users** to find the user ID. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Always include the UTC offset — do not assume UTC; using the wrong offset will place the override in the wrong time slot. See the documentation

Create Service

Create a new PagerDuty service. A service represents a system or application that generates incidents. Use **List Escalation Policies** to find a valid escalation policy ID (required). Set autoResolveTimeout to 0 to disable auto-resolve. Set acknowledgementTimeout to 0 to disable re-triggering after acknowledgment. See the documentation

Find Oncall User

Find the user on call for a specific schedule. See the documentation

Get Event Orchestration for Service

Get the active event orchestration routing rules configured for a service. Event orchestration routes incoming events to the right responders based on conditions. Use **List Services** to discover service IDs. See the documentation

Get Incident

Get full details for a single incident by ID, including its current status, urgency, assignments, and html_url. Use **List Incidents** to find the incident ID. See the documentation

Get Service Analytics

Get incident volume and MTTR (mean time to resolve) metrics for one or more services over a time range. Use **List Services** to discover service IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. See the documentation

List Escalation Policies

List escalation policies in the PagerDuty account. Supports both exact name match (name) and substring search (query), plus team filtering. Use policy IDs with **Create Incident**, **Create Service**, and **Update Escalation Policy**. See the documentation

List Escalation Policy ID Options

Retrieves available options for the Escalation Policy ID field.

List Incident Change Events

List change events (deployments, config changes) correlated to an incident. Change events show what changed in your systems around the time the incident was triggered. Use **List Incidents** or **Get Incident** to find the incident ID. See the documentation

List Incident Workflows

List available incident automation workflows. Use workflow IDs with **Start Incident Workflow** to run automation on an active incident. Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. See the documentation

List Incidents

List and filter incidents by status, urgency, service, or team. Default statuses are triggered and acknowledged (open incidents). Use **List Services** to discover service IDs and **List Teams** for team IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. See the documentation

List Log Entries

List log entries (the audit trail of actions taken on an incident or across the account). When incidentId is provided, scopes results to that incident's log entries. Otherwise returns account-wide log entries. Use **List Incidents** or **Get Incident** to find incident IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Set isOverview: true to get only the most recent action per incident. See the documentation

List On-Call Schedule ID Options

Retrieves available options for the On-Call Schedule ID field.

List On-Calls

List on-call entries — who is on call right now or during a given time window. Filterable by schedule IDs or escalation policy IDs. Use **List Schedules** to discover schedule IDs and **List Escalation Policies** to discover policy IDs. Time params use ISO 8601 with explicit UTC offset, e.g. 2026-06-02T15:00:00-07:00. Set earliest: true to get one on-call entry per unique (schedule, escalation policy, escalation level) combination. See the documentation

List Priorities

List the priority levels configured for this PagerDuty account. Returns priority IDs and names (e.g. P1, P2, critical) useful for **Create Incident** and **Update Incident**. See the documentation

List Schedules

List on-call schedules in the PagerDuty account, optionally filtered by name. Returns schedule IDs and names useful for **List On-Calls** and **Create Schedule Override**. See the documentation

List Service ID Options

Retrieves available options for the Service ID field.

List Services

List services, optionally filtered by team or searched by name. Returns service IDs, names, status, and html_url. Use **List Teams** to discover team IDs for filtering. See the documentation

List Status Page Posts

List posts on a PagerDuty status page. Use **List Status Pages** to discover status page IDs. Set activeOnly: true to filter to currently active posts (client-side filter). Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. See the documentation

List Status Pages

List configured PagerDuty status pages. Use status page IDs with **List Status Page Posts** to retrieve posts on a specific page. Requires Business+ plan — accounts without this plan will receive empty results or a 402 error. See the documentation

List Teams

List teams in the PagerDuty account, optionally filtered by name. Returns team IDs and names useful for filtering incidents, users, and services. See the documentation

Integration Features

Real-time data synchronization
Bi-directional sync capabilities
Custom field mapping
Advanced filtering options
Error handling & retry logic
Activity monitoring & logs

Popular Workflows

When AWS trigger → Create/Update in PagerDuty

Most Popular
AWSAWS

New Scheduled Tasks

PagerDutyPagerDuty

Acknowledge Incident

When PagerDuty trigger → Update AWS

Bi-directional
PagerDutyPagerDuty

New On-Call Rotation

AWSAWS

CloudWatch Logs - Put Log Event

How It Works

1

Connect Apps

Authenticate your AWS and PagerDuty accounts

2

Map Fields

Choose which data fields to sync between apps

3

Set Triggers

Define when and how data should be synchronized

Automate

Sit back and let AI handle the automation

Frequently Asked Questions

Integration Benefits

Real-time Data Sync

Automatic synchronization between AWS and PagerDuty with 14 public triggers available for instant updates.

Automated Actions

Execute 47 public actions automatically across both platforms without manual intervention.

Enterprise Security

Industry-standard encryption, OAuth 2.0 authentication, and SOC 2 compliance for secure data transfer.

Quick Setup

Connect AWS and PagerDuty in minutes with our guided setup wizard and pre-configured templates.

Custom Field Mapping

Map any field between AWS and PagerDuty with intelligent suggestions and validation.

Error Handling

Automatic retry logic, detailed error logs, and smart notifications keep your integration running smoothly.

PagerDuty logoAWS logo

Reverse Integration Available

Also connect PagerDuty to AWS for bidirectional automation

View Integration
AWS logo

All AWS Integrations

Explore all available AWS connections

View All Integrations
PagerDuty logo

All PagerDuty Integrations

Explore all available PagerDuty connections

View All Integrations

Ready to Connect AWS & PagerDuty?

Join thousands of users automating their workflows with Mazaal AI