4.52.02.04 - Edge for Private Cloud release notes

You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info

On July 25, 2025, we released a new version of Apigee Edge for Private Cloud.

Update procedure

This section describes how to install this release if you are updating from the previous release of Edge for Private Cloud. If you need to update from an earlier release, see Applying Multiple Patch Versions.

Updating this release will update the components listed below:

  • edge-gateway-4.52.02-0.0.60308.noarch.rpm
  • edge-management-server-4.52.02-0.0.60308.noarch.rpm
  • edge-message-processor-4.52.02-0.0.60308.noarch.rpm
  • edge-postgres-server-4.52.02-0.0.60308.noarch.rpm
  • edge-qpid-server-4.52.02-0.0.60308.noarch.rpm
  • edge-router-4.52.02-0.0.60308.noarch.rpm
  • apigee-cassandra-3.11.16-0.0.2596.noarch.rpm
  • apigee-cassandra-client-3.11.16-0.0.2544.noarch.rpm
  • apigee-lib-4.52.02-0.0.1028.noarch.rpm
  • apigee-setup-4.52.02-0.0.1150.noarch.rpm
  • apigee-qpidd-8.0.6-0.0.2537.noarch.rpm

You can check the RPM versions currently installed to see if they need to be updated by entering:

apigee-all version

To update your installation, perform the following procedure on the Edge nodes:

  1. On all Edge nodes:

    1. Clean the Yum repositories: 
      sudo yum clean all
    2. Download the latest Edge 4.52.02 bootstrap_4.52.02.sh file to /tmp/bootstrap_4.52.02.sh: 
      curl https://software.apigee.com/bootstrap_4.52.02.sh -o /tmp/bootstrap_4.52.02.sh
    3. Install the Edge 4.52.02 apigee-service utility and dependencies: 
      sudo bash /tmp/bootstrap_4.52.02.sh apigeeuser=uName apigeepassword=pWord

      Where uName and pWord are the username and password you received from Apigee. If you omit pWord, you will be prompted to enter it.

    4. Use the source command to execute the apigee-service.sh script: 
      source /etc/profile.d/apigee-service.sh
    5. Update the apigee-setup utility: 
      apigee-service apigee-setup update
  2. On all cassandra nodes execute the update.sh script: 
    /opt/apigee/apigee-setup/bin/update.sh -c cs -f configFile
  3. On all Edge nodes, execute the update.sh script for the edge process: 
    /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
  4. On all Qpid nodes, execute the update.sh script: 
    /opt/apigee/apigee-setup/bin/update.sh -c qpid -f configFile

Bug fixes

This section lists the Private Cloud bugs that were fixed in this release.

Issue ID Description
429056579 Fixed qpid's wait_for_ready script.

Security issues fixed

No new security issues have been added in this release.

Changes to supported software

Support has been added for Amazon-Linux-2023.7(AL2023.7).

See Edge for Private Cloud supported software for a complete list of supported software.

Deprecations and retirements

There are no new deprecations or retirements in this release.

New features

This section lists the new features in this release.

Issue ID Description
390047431

Support for Amazon-Linux-2023(AL2023) added.

Edge for Private Cloud API hub connector integration

This release includes support for Apigee API Hub connector for Private Cloud integration, enabling organizations to sync both API metadata and runtime analytics to Google Cloud API Hub. The integration includes a new Apigee API Hub connector binary and enhancements to the message processor, which exports runtime data to a network file system (NFS). The API Hub for Private Cloud connector consumes this data and publishes it to API Hub. There are no bug fixes or changes to existing Apigee Edge for Private Cloud behaviour. For more information on Edge for Private Cloud API Hub connector integration, see API Hub connector integration overview and flow.

Key Highlights:

  • New Apigee API Hub connector binary
  • Enhancements to the message processor to export runtime data to NFS
  • Full support for API metadata and runtime data publishing to API Hub
  • Opt-in based activation using standard Apigee API Hub connector for Private Cloud API Flow
  • New API integration with the connector to support uploading environments and proxy bundles
  • A new IAM permission (roles/apihub.admin) is now required for the connector's service account to enable the new API functionality

Personally identifiable information (PII) masking

This feature ensures data privacy and compliance by allowing you to mask sensitive data within API proxy and shared flow bundles before they are synchronized to API Hub.

  • Default masks: The connector automatically applies a built-in list of XPath expressions (default masks) to mask known PII sources in policy configurations (such as hardcoded basic authentication passwords, private keys in JWT/JWS policies).
  • Custom masks: You can configure additional custom masks by setting the conf_uapim_connector.uapim.mask.xpaths property in the /opt/apigee/customer/application/uapim-connector.properties file, allowing you to target customer-specific sensitive fields.

Organization reconciliation

The connector now provides a defined process for reconciling (or backfilling) an existing Apigee organization's entire API metadata set to API Hub.

  • Process: Reconciliation is achieved by temporarily opting out an organization from the connector's configuration (clearing the runtimeDataPubsub and metadataPubsub property values) and then immediately opting it back in (restoring the values).
  • Function: This action forces the connector to perform a complete fetch and full resync of all metadata for the specified organization, resolving potential data inconsistencies.

Known issues

See Known issues with Edge for Private Cloud for a complete list of known issues.

Applying multiple patch versions

This section describes how to apply multiple patch versions, in case you are updating from a version of Edge for Private Cloud that is earlier than the previous patch release version.

Each patch release contains updates to specific components of Edge for Private Cloud, such as edge-management-server. To apply multiple patch versions, you need to update each Edge component that was included in a patch release later than your currently installed version. You can find these components by looking at the Edge for Private Cloud release notes for all versions later than your current version, and checking the list of RPMs for those releases. See Apigee Release Notes for links to all Edge for Private Cloud release notes.

Note: You only need to update each component once, by installing the RPM for the latest version of the component included in the patch releases. Follow the instructions in the release notes for that version to update the component.

Note: Upgrading a component automatically installs the latest patch version of a component. If you want to upgrade to a patch version that is not the latest, you need to maintain your own tarball copy of Apigee's repo using Apigee mirror, and use this mirror for Apigee installations. For more information, refer to Using a local Edge repository to maintain your Edge version.