EDB Postgres Service Broker for Pivotal Cloud Foundry

This documentation describes the EnterpriseDB (EDB) Postgres Service Broker tile for Pivotal Cloud Foundry (PCF).

The EDB Postgres Service Broker tile registers a service broker on PCF and exposes a service plan on the Marketplace. Developers can provision a PostgreSQL database by creating instances of the service plan using Apps Manager or the cf Command Line Interface (CLI).


The EDB Postgres Service Broker provides a single service plan which provisions a PostgreSQL database on a shared PostgreSQL server.

When a developer creates an instance of the service plan, the EDB Postgres Service Broker creates a PostgreSQL database on the PostgreSQL server. Each service instance connects to a single database that is secure from other databases on the server.

When a developer binds a service instance to an application, the binding call provisions credentials and delivers them to the application. When a developer unbinds a service instance, the unbinding call disables the database user role if there are no other bindings.

When a developer deletes a service instance, the EDB Postgres Service Broker deprovisions the PostgreSQL database and deletes all resources.

Product Snapshot

The following table provides version and version-support information about EnterpriseDB Postgres Service Broker for Pivotal Cloud Foundry:

Element Details
Version v1.0.14
Release date July 20, 2016
Software component version EnterpriseDB Postgres Service Broker v1.0.14
Compatible Ops Manager version(s) v1.5.x, v1.6.x, v1.7.x
Compatible Elastic Runtime version(s) v1.4.x, v1.5.x, v1.6.x, v1.7.x
IaaS support AWS, Azure, OpenStack, and vSphere


To install the EDB Postgres Service Broker tile on your PCF deployment, you must have a PostgreSQL 9.x server running. You can use a generic PostgreSQL 9.x server or the EDB Postgres Advanced Server. Customers interested in using the EDB Postgres Advanced Server can obtain a 60-day free trial license from the EDB website.

The EDB Postgres Service Broker uses a PostgreSQL table for its metadata.


Please provide any bugs, feature requests, or questions to the Pivotal Cloud Foundry Feedback list.

Create a pull request or raise an issue on the source for this page in GitHub