Developer-on-Duty On-Demand Access With PagerDuty & Apono

Apono’s integration with PagerDuty enables the creation of access policies that are synced with PagerDuty on-call groups, validating that the requester is on-call, and allocating the minimum amount of resources needed to resolve the incident

Easily create declarative access flows that gain contextual authorization information from PagerDuty

Automatically revoke standing privileges, reduce risk to pre-incident status.

01. Break Glass Scenarios

Empower first-responders with on-demand permissions to the relevant Kubernetes Namespace.Logging incident context, access received and timeline.

02. Contextual Automatic Access Workflow

Reduce friction between departments and reducing MTTR.

03. Request & Approve via ChatOps

Grant and request access using ChatOps workflows (Slack, Teams).

04. Just-In-Time Task Based Permissions

Granting developers the temporary permissions they need for only the task at hand.

DevOnDuty Break Glass Access

The contextual data given by Apono’s PagerDuty Integration, in conjunction with IDP and Chatops integrations allows the creation of contextual automated access flows.

When

DevOnDuty

requests

Read/Write

Acme_namespace

from

Customer_namespaces

grant access for

4 Hours

with

DevOps

approval.

Automate Access To PagerDuty

Review Access

View a detailed access audit of who was granted access to which instances with what permission level and why.

15 Minutes Deployment
No Secrets Stored
Full Access Visibility