EDB Postgres Ark Service Broker for PCF

WARNING: This tile requires a Trusty stemcell. The end of life date for Ubuntu Trusty is April 2019. If a security vulnerability is found on this stemcell after April, it will not be fixed.

This documentation describes the installation and usage of EDB Postgres Ark Service Broker for Pivotal Cloud Foundry (PCF). EDB Postgres Ark for PCF integrates with EDB Postgres Ark (Ark) on either an OpenStack or Amazon AWS host.



EDB Postgres Ark automatically provisions PostgreSQL or EDB Postgres Advanced Server databases in single instances, high-availability clusters, or application development sandboxes.

Key Features

In minutes, EDB Ark configures a cluster of database machines with:

  • Streaming replication
  • Connection pooling
  • Load balancing
  • Automatic failover (transaction or recovery time preferred)
  • Secure data encryption
  • Rotating user-scheduled backups
  • Point-in-time recovery
  • Elastic storage
  • Elastic scale out

Product Snapshot

The following table provides version and version-support information about EDB Postgres Ark.

Element Details
Tile version v1.0.1
Release date September 21, 2017
Software component version v2.0
Compatible Ops Manager version(s) v1.9.x, 1.10.x, 1.11.x, and 1.12.x
Compatible Elastic Runtime version(s) v1.9.x, 1.10.x, 1.11.x, and 1.12.x
Compatible Pivotal Application Services (PAS)* version(s) v2.0.0
EDB Postgres Ark version EDB Postgres Ark Service Broker for PCF supports provisioning of instances managed by version 2.2 of the Ark console.
BOSH stemcell version Ubuntu Trusty
IaaS support EDB Postgres Ark Service Broker for PCF supports provisioning of RHEL 7 and CentOS 6.x and 7.x instances on OpenStack and Amazon AWS.
IPsec support? No


EDB Postgres Ark Service Broker for PCF has the following pre-requisite:

Before deploying EDB Postgres Ark Service Broker for PCF, you must install and configure the EDB Postgres Ark server on an Amazon AWS or OpenStack host. When configuring Ark, you must enable at least one database engine; ideally, you should enable all of the engines that you plan to use with the tile before tile deployment.

For detailed information about deploying an Ark console on an AWS or OpenStack host, see the EDB Ark Administrative User Guide.


EDB Postgres Ark has the following known limitations:

  • Prior to launching a tile, you must connect to the Ark console as an Administrative user and enable all of the database engines that will be used by the tile. If you enable additional engines after launching the tile, you will be required to reconfigure and restart the tile.

  • When configuring an instance in the Pivotal Apps Manager, you will have the option to bind the instance to an application. You should not provide a value in the Bind to App field; if the graphical interface attempts to bind before the back-end cluster is running, the binding will fail. Instead, select Show Advanced Options and specify your service instance preferences. After the service instance has been created, you can use the Pivotal App Bindings dialog or bind-service command to bind an application to your instance.

  • When calling cf update-service, the optional –p NEW_PLAN functionality is not supported by EDB Postgres Ark Service Broker for PCF.


If you have a feature request, questions, or information about a bug, please send an email to support@enterprisedb.com.


EDB Postgres Ark Service Broker for PCF does not require a license, but licenses may be required for software managed by EDB Postgres Ark. Please consult each software vendor for their licensing requirements.

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