Apigee deprecations and retirements

Deprecation of monetization tax engine

Support for the apigee-analytics-collector command-line utility

Apigee recommends that Private Cloud customers submit API traffic statistics manually, as described in Submitting API traffic statistics to Apigee.

Support for Node.js proxies and secure vaults

Since 2013, Apigee has supported the use of Node.js proxies within Apigee Edge through the use of Trireme, which enables you to run your Node.js code within Apigee Edge for Private Cloud and expose it as an API.

Apigee recommends Private Cloud customers take the following steps:

• Migrate data in secure vaults to Encrypted Key Value Maps (KVM) to access sensitive data from an API proxy.
• Migrate Trireme (Node.js) based API proxies to a native Node.js environment outside of Apigee.

Support for OAuth V1 features.

Since IETF RFC 6749 has become the standard that replaced OAuth 1.0a, the maintainers of the OAuth v1.0a standard recommend that users switch to OAuth v2.0.

Deprecated policies include:

• OAuthv1.0a policy
• GetOAuthV1Info policy
• DeleteOAuthV1Info policy

For improved security, Apigee recommends that Private Cloud customers migrate to using the OAuth v2 policies as soon as possible.

Support for the Concurrent Rate Limit feature

The Concurrent Rate Limit policy was designed to be used with slow backends, however, the architecture used by it affected the performance of the APIs.

Since the Concurrent Rate Limit's announcement, Apigee has added newer capabilities such as chaining proxies together and shared flows. If you are experiencing slower performance with Concurrent Rate Limit policy, you can try using Spike Arrest instead.

You can read more details in our usage notes page.

Using such features along with policy, will allow you to protect slow/sluggish backends without impacting the performance of the APIs.

Migrate proxies using the Concurrent Rate Limit policy to the Quota policy and/or the Spike Arrest policies.

Support for Istio by integrating with Istio Mixer

In March this year, the Istio community announced deprecation for Istio Mixer. The Istio Mixer component is critical for the functioning of the Apigee adapter for Istio, which is why we redesigned the Istio adapter to use native Envoy filters (see envoy filter and HTTP filters) to integrate with Apigee.

Apigee announced the beta release of this feature in the API management for services that use Envoy blog post, in addition to the Apigee Adapter for Envoy overview).

Apigee recommends that you migrate to Apigee adapter for Envoy as soon as possible.

Support for the Teams early access feature

The early access program for the Teams feature in Apigee has been canceled, and the Teams feature will be removed from Private Cloud.

If you are using Teams, Apigee recommends replacing the team entities and the permissions associated with those teams with custom roles. The roles can be granted to the same set of users that comprised the team to replicate the desired team structure.

Deprecation of sponsored hosting for Drupal portals

On the retirement date, Apigee will no longer provide sponsored hosting of Drupal-based developer portals. Customers wishing to continue using Drupal must assume their hosting responsibilities, see the Drupal 7 Transition FAQ.

Deprecation of monetization variance reports

On the retirement date, Apigee will no longer support monetization variance reports on Apigee Edge.

Deprecation of Personal space

On the retirement date, Apigee will no longer support Personal space on Apigee Edge. Copy your OpenAPI Specifications from your personal space to one of your other organizations.

Retirement of Monitoring Dashboard (Beta)

On May 29, 2018, Apigee retired support for the Monitoring Dashboard. For more information, see Monitoring Dashboard (Beta).

Deprecation of OAuth 1.0a

On the retirement date, Apigee will no longer support OAuth 1.0a. Please migrate any OAuth 1.0a usage in your API proxies to OAuth 2.0, and extend your OAuth 2.0 usage with signature verification (for message-level integrity checks) according to your needs.

Affected OAuth 1.0a policies include the OAuth v1.0a policy, Get OAuth V1 Info policy, and Delete OAuth V1 Info policy. Edge includes corresponding OAuth 2.0 policies.

Update TLS configuration for a virtual host API

The Update TLS configuration for a virtual host API lets Edge for the Cloud customers update the TLS configuration properties for a virtual host.

Cloud customers can now create and update a virtual host, not just modify the TLS properties of the virtual host. Therefore, this API has been deprecated. Cloud customers can now use the following APIs with virtual hosts:

• Create a virtual host
• Update a virtual host

Apigee service broker for Pivotal Cloud Foundry EOL

Apigee service broker for Pivotal Cloud Foundry (PCF) will reach End of Life (EOL) on the retirement date shown here.

If you are currently using the service broker, you need to take the following actions before the retirement date:

1. Uninstall the service broker tile from OpsManager.
2. Delete any service instances that you may have created.
3. Rewire any routes (to API proxies) that may have been created for your apps.

Edge Installer for Pivotal Cloud Foundry EOL

The Apigee Edge Installer for PCF reached End of Life (EOL) on the retirement date shown here. For more information, see this community post.

Deprecation of "Trireme"-based Node.js support

As of the retirement date, existing Trireme is deprecated and will be retired on the date indicated. Please migrate existing Node.js applications deployed on Apigee Edge to Hosted Targets. For assistance, see Migrating an existing Node.js proxy to a Hosted Targets proxy.

For more information, see Trireme-based Node.js End of Life.

Apigee announces the deprecation of the Apigee Edge API Backend-as-a-Service (API BaaS) feature.

The API BaaS end of life (EOL) will be June 30, 2019. Apigee will continue to operate and support API BaaS until June 30, 2019, subject to the terms of our deprecation policy. Read more in this blog post, in the Deprecation and End of Life announcement, and in Guidance for migrating from Apigee API BaaS.

Note that the API BaaS Android push notifications functionality is reliant on Google Cloud Messaging (GCM), which will reach end of life on April 11, 2019. Please be advised that we will not upgrade the Apigee API BaaS solution to use the new Google Firebase Cloud Messaging (FCM) system, as this would require customers to migrate to this new messaging system while also planning to migrate off Apigee API BaaS altogether before June 30, 2019.

We recommend that Android push notification customers start their planning to migrate off of Apigee API BaaS for this functionality before April 11, 2019.

Retirement of monetization billing document generation

Apigee no longer supports the generation of billing documents from Apigee Edge Monetization.

The specific tasks that are retired and no longer supported for use with monetization include:

• Adding bank accounts
• Configuring billing documents
• Managing billing documents

Retirement of BaaS Eval Orgs

On June 18, 2018, BaaS Eval orgs will no longer be accessible. This is being done as part of the BaaS EOL process, which you can read more about in this blog post and in the Deprecation and End of Life announcement.

Retirement of TLS 1.0 and 1.1 - Extension

Apigee will retire support for TLS versions 1.0 and 1.1 in the public cloud on the following dates.

• PCI customers: June 29, 2018
• Non-PCI customers: July 31, 2018

For more information, see TLS 1.0 and 1.1 retirement.

November 9, 2018

Apigee Test End of Life

Apigee Test has been an Apigee labs project for some time. It provides the ability to synthetically monitor, check and notify the availability of you API endpoints. Apigee has decided to discontinue this service and will be decommissioning the Apigee Test site 45 days from the date of this notice.

Stackdriver’s black-box monitoring system, Uptime Checks, provides basic functionality of Apigee Test. Please consider utilizing its services if it works for your use cases. You can also use the in-app “Send Feedback” link to submit feature requests for your use case(s) to that Google product team.

Apigee announces that it is discontinuing the use of Dedicated Instances for HIPAA compliance pack customers in AWS.