You're viewing Apigee Edge documentation.
Go to the
Apigee X documentation. info
On August 26, 2025, we released version 4.53.01 of Edge for Private Cloud. This version of Edge for Private Cloud is also available for Apigee on Google Distributed Cloud air-gapped customers. For more information, see the product page and install Apigee on Google Distributed Cloud air-gapped.
Release summary
The following table summarizes the changes in this release:
| New Features |
This release includes the following new features:
For more information about these new features, see New features. |
| Retirements | None |
| Deprecations | None |
| Known Issues | For more information about known issues, see Known issues. |
Upgrade paths
For instructions on upgrading to Edge for Private Cloud 4.53.01, see Update Apigee Edge 4.52.02 or 4.53.00 to 4.53.01.
New features
This section lists new features in this release. Additionally, this release includes all features in the Edge UI, Edge Management, and Portal releases.
In addition to the following enhancements, this release also contains multiple usability, performance, security, and stability enhancements.
| Issue ID | Description |
|---|---|
| 428627002 | Pagination and batch size configuration for API proxies list page. |
| 436181459 | Support for native mTLS between Edge components and Cassandra. |
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.xpathsproperty in the/opt/apigee/customer/application/uapim-connector.propertiesfile, 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
runtimeDataPubsubandmetadataPubsubproperty 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.
Supported software
This release includes the following changes to supported software:
| Support Added | No Longer Supported |
|---|---|
|
The following software versions are no longer supported with this release:
|
For a complete list of supported platforms, see Supported software and supported versions.
Bug fixes
This section lists the Private Cloud bugs that were fixed in this release. Additionally, this release includes all bug fixes in the Edge UI, Edge Management, and Portal releases.
| Issue ID | Description |
|---|---|
| 417261430 | Fixed 503 errors when reverting target server from HTTPS (443) to HTTP (80). |
| 440040667 | New Edge UI can have http/2 protocol optionally disabled. |
| 383756839 | Upgraded multiple third party libraries. |
| 388535266 | Removed deprecated lib directory from edge components. | 366144787 | Enhanced monetization API to sync single entity. |
| 374354789 | Improved status message handling in the SAML response of apigee-sso. |
| 328166228 | Made Postgres port configurable for monetization. |
| 391852306 | Fixed monetization transaction rating failures after timezone changes. |
Security issues fixed
Fixed multiple security vulnerabilities in almost all components of Edge for Private Cloud 4.53.01.
Known issues
See Known issues with Edge for Private Cloud for a complete list of known issues.
Next step
To get started with Edge for Private Cloud 4.53.01, use the following links:
New installations:
For more information, see New installation overview
Existing installations:
For more information, see Update Apigee Edge for 4.53.01