Getting started with Cloud Foundry integration
The following topics walk you through the process of setting up and using the Apigee service broker. The steps here cover:
- 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 you can create API proxies. To create an Apigee Edge account, see Creating an Apigee Edge account. For more about organizations, see Understanding organizations.
- A recent version of the
cfcommand 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 1.7 installation 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.
Help or comments?
- If something's not working: Ask the Apigee Community or see Apigee Support.
- If something's wrong with the docs: Send Docs Feedback
(Incorrect? Unclear? Broken link? Typo?)