- Install and configure the Apigee service broker
- The Apigee service broker provides access to Apigee Edge from within a Cloud Foundry app. When installing it, you'll configure it with values for connecting to Apigee Edge.
- Creating an Edge API proxy to manage client calls to your Cloud Foundry application
- Use the Cloud Foundry CLI to proxy a sample Cloud Foundry application with an Apigee Edge API proxy.
To use Apigee Edge with Cloud Foundry, you'll need the following:
- An Apigee Edge account (Public Cloud or Private Cloud) with an organization where API proxies can be created. To create an Apigee Edge account, see Creating an Apigee Edge account. For more information about Apigee organizations, see Organization structure.
- Version 3.1.1 of the Apigee Edge Service Broker for PCF. You can install the tile using instructions in this documentation.
- A recent version of the cf command line interface. Your version must include required support for route-services operations. This integration works with v6.20.0.
- A Pivotal Cloud Foundry Elastic Runtime (v2.1 to v2.2) deployment with Route Services enabled.
- Node.js v4.x or later. Cloud Foundry includes Node.js as a system buildpack, so you can install and run the service broker without Node installed locally, if necessary.
- Apigee utility scripts to generate an authorization token. The service broker will create the (reverse) proxy on Apigee Edge for the app's route. This requires authenticating with Apigee Edge; ideally this is done with an authorization token, generated with scripts Apigee provides. Plain username and password may also be used if necessary.
- Apigee Edge Microgateway, depending on the service plan you are using.
- The cf CLI v6.20.0 or later, which includes support for