Introduction to provisioning

You're viewing Apigee X documentation.
View Apigee Edge documentation.

This section describes the prequisites and process for installing and configuring Apigee with either an eval organization or a paid (non-evaluation) organization. We refer to the installation and configuration process as provisioning.

This section contains important information about Apigee orgs and the prerequisites for provisioning one.

Provisioning options

Before you begin, we recommend that you review the differences between Eval and Paid organizations, as described in Comparing eval and paid organizations. Then, choose the most appropriate method for you for provisioning an org:

Method Description Next Step
Apigee provisioning wizard
  • Easiest
  • Less prone to error
  • Some details are hidden or obfuscated by the wizard
Command line instructions
  • High level of control
  • No hidden tasks -- you do them all
Apigee Trial Provisioning Script
  • One step: define the values; the script does the rest
  • Does not support Windows
Apigee Terraform Modules Terraform modules and examples for end to end deployment patterns.

Comparing eval and paid organizations

Both paid and evaluation organizations have full functionality; the differences between them lay mostly in scaling and infrastructure allowances, as the following table shows:

Function Org Type Description
Paid/Production Evaluation
Lifespan Based on contract 60 days For an eval org, you will get a notification after 30 days that its lifespan is limited. After 60 days, Google deletes the eval org. You cannot extend its lifespan. For more information, see Apigee Pricing or contact Apigee Sales.
Requires VPC peering? Both require VPC peering.
Required peering network size /22 + /28 /22 For more information, see Peering ranges.
Proxy access External or private/local access External or private/local access By default, API proxies can be accessed internally only. You can, however, configure your load balancer to accept external requests for either an eval or paid account.
Supported instances Based on contract 1 The number of runtime instances.
Environments Based on contract 2

The number of runtime environments. Does not affect the number of environment groups.

Apigee creates two environments during provisioning, so an eval org must delete one to create a new one.

Runtime fault tolerance Regional Regional

Runtimes for production and evaluation orgs use regional clustering, which means that if a zone goes down, Apigee can re-route requests to the runtimes in other zones within the region.

For more information about regions and zones, see Regions and zones.

Analytics data Regional Regional

Analytics data is regional for both.

Customer managed encryption keys for runtime data Yes No
SLA Yes. See Apigee Service Level Agreement (SLA) No
Scalability and sizing Evaluation orgs have limited/restricted infrastructure. They are not suitable for performance/load testing.
Integrations and Connectors Based on contract
  • Maximum execution of 500 tasks per day across all the integrations
  • Maximum of 2 integrations can run in parallel
  • You can only use the connectors supported in the Apigee eval org's region
  • Maximum of 4 connections can be created

For additional information, see Apigee Pricing.