Agentic Database Enablement

Service Overview

The EDB Agentic Database Enablement engagement guides your team through the identification, design, and functional implementation of EDB Hybrid Manager's agentic capabilities. Working directly with your DBAs, DevOps engineers, and SREs, an EDB Senior Consultant defines your automation targets, configures AutoPilot operations, establishes intelligent alerting and ChatOps workflows, and validates that each automation scenario delivers measurable operational value in your environment.

This engagement is outcome-focused: customers leave with working agentic automation — not just installed software — and the knowledge to extend it independently.

Scope of Service

Our consultant will work with your team through the following phases:

Onboard

• Kickoff meeting to align stakeholders, confirm environment access, and validate prerequisites
• Review current Postgres estate: cluster inventory, environments, monitoring posture
• Identify automation targets and define success criteria for each agentic use case

Discovery & Use Case Design

• Map database operations to AutoPilot automation tiers (recommendations → guided → fully automated)
• Define maintenance windows, scaling thresholds, and escalation policies
• Design ChatOps notification routing (alerts, automated task approvals, activity logs)
• For Large/X-Large: design CI/CD DevOps Co-Pilot integration and custom policy governance

Configuration & Implementation

• Configure AutoPilot settings per environment and cluster tier
• Set up auto-scaling rules for CPU, memory, and storage
• Configure automated minor upgrade schedules within maintenance windows
• Establish monitoring alert routing to ChatOps channels (Slack, PagerDuty)

Validation & Enablement

• Demonstrate and validate each configured automation scenario with the customer team
• Walk through key operational procedures: automated upgrade cycle, scaling event, alert response
• Transfer knowledge: review configuration, explain operational controls, document customizations

Project Closure

• Formal sign-off review against agreed scope and success criteria
• Deliver engagement summary and next-steps recommendations

Deliverables

• Configured and operational agentic automation for the agreed cluster scope
• Documented automation configuration (AutoPilot settings, policies, ChatOps routing)
• Validated automation scenarios demonstrating end-to-end operation
• Engagement summary with configuration notes and recommended next steps

Roles and Responsibilities

EDB Project Manager: Responsible for engagement planning, schedule management, stakeholder communication, and project closeout.

EDB Solution Architect: Leads use case design, defines automation architecture, and reviews configuration against EDB best practices.

EDB Senior Consultant: Technical lead responsible for all configuration, implementation, validation, and knowledge transfer activities.

Customer Team: Responsible for providing environment access, defining business requirements, and participating in validation sessions. Key stakeholders include:

• Database Administrator (DBA)
• DevOps / Platform Engineer
• SRE or Operations Lead
• Security / Compliance Representative (if applicable)

Assumptions

• A kickoff call will be conducted to confirm scope and schedule before work begins.
• This engagement is delivered remotely unless otherwise agreed.
• Customer's EDB Hybrid Manager instance is deployed and operational prior to engagement start.
• EDB Postgres AI software licenses are in place for all clusters in scope.
• Customer will designate a primary point of contact with knowledge of the Postgres estate and environment access.
• Customer will make appropriate technical personnel available throughout the engagement.
• Application testing and load testing are not in scope.
• Customer will provide timely feedback on all deliverables. Deliverables without commentary within 5 business days will be deemed accepted.
• Customer will not provide Personal Data as defined by applicable law.
• Air-gapped environments require advance notice; additional scope may apply.

Prerequisites

• EDB Hybrid Manager (version 1.3 or later) is deployed and accessible.
• Customer has administrative access to Hybrid Manager and target database clusters.
• Target database clusters are registered in Hybrid Manager.
• Customer has completed HM network connectivity requirements for all clusters in scope.
• For ChatOps integration: customer has configured and can provide webhook credentials for Slack, PagerDuty, or ServiceNow as applicable.
• For CI/CD Co-Pilot: customer has access to their GitHub or GitLab repository and can configure webhooks.
• Customer's security team has approved EDB HM access to target systems.

Engagement Activities