
# PagerDuty Runbook Automation Self-Hosted

Commercial runbook and operations-automation platform deployed as a customer-operated cluster in AWS.

Canonical page: https://launchinyourcloud.com/directory/pagerduty-runbook-automation-self-hosted/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## PagerDuty Runbook Automation Self-Hosted

Commercial runbook and operations-automation platform deployed as a customer-operated cluster in AWS.

- Listing: https://launchinyourcloud.com/directory/pagerduty-runbook-automation-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Commercial PagerDuty Runbook Automation Self-Hosted license required; Rundeck Community is a separate Apache-2.0 edition.
- Licensing model: commercial-only
- Installation: Commercial RPM/DEB/WAR or official Docker image on customer AWS infrastructure; obtain a current licensed Helm artifact before using the older EKS recipe
- Architecture: Customer-operated Runbook Automation application with load balancing, database, object storage and execution nodes.
- Operations: Customer manages EKS or VMs, database, storage, networking, TLS, execution nodes, backups, upgrades and license delivery.
- Product website: https://www.pagerduty.com/platform/automation/runbook-automation/
- Source review: 2026-11-18; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

Commercial Runbook Automation Self-Hosted is distinct from PagerDuty SaaS and Rundeck Community. The EKS tutorial’s linked commercial Helm directory returned 404; use current licensed package/container documentation and obtain a pinned chart if needed. Official Docker images before 6.3.0 require the scoped CA trust-store remediation.

Runbook Automation Self-Hosted is commercial software requiring a license. Rundeck Community is separately Apache-2.0 licensed and is not the selected edition.

The AWS architectures run persistent application and execution services backed by customer database and object storage.


### Category fit

- workflow-automation: Automates operational runbooks, scheduled jobs and controlled actions through customer-operated execution services.

- devops: Provides operations automation, job orchestration, access control and integrations for delivery and incident workflows.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.rundeck.com/docs/administration/install/aws.html (checked 2026-11-18). 


### Cloud deployment evidence

- Runbook Automation Self-Hosted on AWS (aws): https://docs.rundeck.com/docs/administration/install/aws.html
  PagerDuty documents a customer-operated HA architecture using AWS load balancing, RDS and S3; a separate guide deploys the product to customer EKS.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.


### Sources

- Deploy Runbook Automation on Amazon EKS: https://docs.rundeck.com/docs/learning/howto/how2-terra-rd-eks.html

- Runbook Automation Self-Hosted on AWS: https://docs.rundeck.com/docs/administration/install/aws.html

- Deploy Rundeck on AWS with Terraform: https://docs.rundeck.com/docs/learning/howto/how2-terra-rd-aws.html

- Runbook Automation licensing: https://docs.rundeck.com/docs/administration/license.html

- Rundeck and Runbook Automation editions: https://docs.rundeck.com/docs/about/introduction.html

### Licensing sources

- https://docs.rundeck.com/docs/administration/license.html

- https://docs.rundeck.com/docs/about/introduction.html

### Infrastructure sources

- https://docs.rundeck.com/docs/administration/install/aws.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 7 documented, 5 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The vendor confirms a separate commercial Self-Hosted product, but the reviewed PagerDuty Marketplace leads did not establish an exact offer entitling that software. SaaS subscriptions, professional services and remotely hosted runners are different scopes. Request the applicable self-hosted offer/order ID, seller, licence terms and current commercial artifact. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://www.pagerduty.com/platform/automation/process-software/ (reviewed 2026-11-18).

- Cloud commitment eligibility: Sources checked — unresolved. A commercial Runbook Automation licence file and AWS deployment do not establish cloud-commitment credit. Confirm the actual self-hosted order, procurement route and buyer agreement. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/license.html (reviewed 2026-11-18). Supporting source: AWS commitment qualification is product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Edition-dependent. Runbook Automation’s commercial SSO integration uses OAuth2/OIDC authorization-code login, with configuration guidance for Okta, Ping and Azure AD and required signing-key discovery. Confirm identity/role mapping for the selected IdP; this is distinct from Rundeck Community authentication. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/security/sso/ (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The OIDC SSO guide does not establish a commercial self-hosted SCIM endpoint or user/group lifecycle. PagerDuty account provisioning and SSO profile synchronization are not evidence of Runbook Automation SCIM support. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/security/sso/ (reviewed 2026-11-18). Supporting source: Authentication providers are not a provisioning endpoint — https://docs.rundeck.com/docs/administration/security/authentication.html.

- Compliance attestations: Sources checked — unresolved. PagerDuty says Runbook Automation Self-Hosted can operate inside the customer firewall to meet stricter requirements such as FedRAMP. That is deployment/control guidance, not evidence that the self-hosted product or buyer’s automation system has that authorisation. Obtain the actual report/certificate and include local database, runners, plugins, job targets, identity and operations in the assessment. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://www.pagerduty.com/platform/automation/process-software/ (reviewed 2026-11-18).

- Security controls: Documented. The commercial SSO guide configures OIDC login and signing-key validation. Release 6.3.0 hardens webhook token storage and official container trust stores. Operators must separately control job permissions, key storage, runner credentials and target access. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/security/sso/ (reviewed 2026-11-18). Supporting source: 6.3.0 security changes — https://docs.rundeck.com/docs/history/6_x/version-6.3.0.html. Supporting source: Container CA trust-store advisory — https://docs.rundeck.com/docs/history/cves/2026-10-emudhra-ca.html.

- Air-gapped operation: Edition-dependent. PagerDuty explicitly identifies Runbook Automation Self-Hosted for air-gapped networks and operation entirely inside the customer’s infrastructure. Prepare the commercial application/runner/plugin artifacts, local database, identity, certificates and job targets. A valid commercial licence is still required; agree its offline issuance/renewal and expiry process rather than assuming the SaaS or cloud-runner flow is disconnected. Scope: Commercial Runbook Automation Self-Hosted with prepared local dependencies; SaaS and remotely hosted control planes are excluded. Source: https://www.pagerduty.com/platform/automation/process-software/ (reviewed 2026-11-18). Supporting source: Local commercial licence installation — https://docs.rundeck.com/docs/administration/license.html.

- Deployment artifact / IaC: Documented. The current guide names the commercial image rundeckpro/enterprise:6.3.0 with an external database, and recommends a reviewed derived image in a private registry. DEB installation separately uses package rundeckpro-ent. The EKS tutorial’s linked commercial Helm directory returned 404; obtain a current chart rather than substituting its Community example. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/install/docker.html (reviewed 2026-11-18). Supporting source: Customer AWS EC2/load balancer/RDS/S3 architecture — https://docs.rundeck.com/docs/administration/install/aws.html. Supporting source: Commercial DEB package repository — https://docs.rundeck.com/docs/administration/install/linux-deb.html. Supporting source: EKS tutorial and obsolete chart link — https://docs.rundeck.com/docs/learning/howto/how2-terra-rd-eks.html.

- Minimum footprint / sizing: Documented. Commercial Runbook Automation minimum is 4 CPUs/16 GB RAM with 12 GB heap per application instance; recommended is 8 CPUs/32 GB with 24 GB heap. Java 17 is the minimum from 6.0. Production uses an external supported database; H2 is for testing. HA replicas, logs and job runners add resources. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/install/system-requirements.html (reviewed 2026-11-18).

- License pricing: Documented. Commercial Runbook Automation Self-Hosted requires a licence file and quote. Rundeck Community’s Apache 2.0 licence does not license the commercial SSO/cluster features in this listing. Price runners, support and the purchased entitlement separately. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/administration/license.html (reviewed 2026-11-18).

- Operating cost estimate: Sources checked — unresolved. Specify concurrent jobs, execution duration, runner pools and job-target work, HA application instances, external database HA, log/object retention and commercial licences. The per-instance minimum is not a complete AWS bill for 100 users or 1 TB of logs. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://docs.rundeck.com/docs/administration/install/system-requirements.html (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. The official release notes identify Runbook Automation/Rundeck 6.3.0 and its security fixes. The public Rundeck OSS tag v6.3.0 was published October 22, 2026; that repository timestamp is not asserted as a separate commercial-package publication time. Verify the licensed image/package version and rebuild official containers for the CA fix. Scope: PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition. Source: https://docs.rundeck.com/docs/history/6_x/version-6.3.0.html (reviewed 2026-11-18). Supporting source: Commercial Docker remediation requirements — https://docs.rundeck.com/docs/history/cves/2026-10-emudhra-ca.html.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Runbook Automation Docker CA trust-store remediation (security-advisory): Official Docker images before 6.3.0 trust compromised eMudhra intermediates. The vendor directs self-hosted operators to pull and redeploy fixed images. Scope: Official Runbook Automation/Rundeck and Runner Docker images before 6.3.0. SaaS is excluded; host-installed RPM/DEB/WAR deployments depend on OS and Java trust stores. Conditions: An on-path attacker could exploit trusted compromised intermediates for outbound TLS. The vendor reports no known exploitation; this is not a flaw in Runbook Automation code. Action: Redeploy the updated 6.3.0+ official images rather than patching a disposable container. For host installations update and verify both OS and Java trust stores and restart. Source: https://docs.rundeck.com/docs/history/cves/2026-10-emudhra-ca.html; reviewed 2026-11-18.



