You're viewing **Apigee Edge** documentation. [Go to the **Apigee X** documentation](http://cloud.google.com/apigee/docs). info On October 11, 2024, we released version 4.53.00 of the Edge for Private Cloud Feature Release. > [!NOTE] > For more information, see the following resources: > > - *[Edge for Private Cloud 4.53.00 documentation](https://docs.apigee.com/private-cloud/v4.53.00)* > - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support) > - *Release notifications* : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications) ## Release summary The following table summarizes the changes in this release: | || |---|---| | [New Features](https://docs.apigee.com/release/notes/45300-edge-private-cloud-release-notes#new-features) | This release includes the following new features: - Support for RHEL 9, Rocky 9 and Oracle EL 9 - Support for Python 3 - FIPS-enabled (fresh install only) on RHEL 8 - Support for Cassandra 4.0.13 - Support for Nginx 1.26 For more information about these new features, see [New features](https://docs.apigee.com/release/notes/45300-edge-private-cloud-release-notes#new-features). | | Retirements | None | | Deprecations | None | | [Known Issues](https://docs.apigee.com/release/notes/45300-edge-private-cloud-release-notes#known-issues) | For more information about known issues, see [Known issues](https://docs.apigee.com/release/notes/45300-edge-private-cloud-release-notes#known-issues). | > [!NOTE] > **Note:** In OPDK 4.53.00, the internal cryptography provider has been updated from Bouncy Castle (BC) to **Bouncy Castle FIPS (BCFIPS)** to enable FIPS support. > > This change may impact customers who utilize or explicitly load cryptography providers in Java Callouts with the string "BC", as the previous provider is no longer accessible. > > Any custom implementations relying on the old provider will need to be carefully reviewed and re-implemented using the Bouncy Castle FIPS provider and its corresponding methods, which can be accessed using the string **"BCFIPS"**. ## Upgrade paths For instructions on upgrading to Edge for Private Cloud 4.53.00, see [Update Apigee Edge 4.52.02 to 4.53.00.](https://docs.apigee.com/private-cloud/v4.53.00/update-apigee-edge-45202-45300) ## 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. **Supported Software:** This release supports RHEL 8, 9, Rocky In addition to the following enhancements, this release also contains multiple usability, performance, security, and stability enhancements. | Issue ID | Description | |---|---| | 346681821 | Support for RHEL 9 | | 297937736 | Support for Python 3 | | 328635735 | Support for Cassandra 4.0.13 | | 366142705 | Support for Nginx 1.26 | For additional information, refer to the [Nginx 1.26 changes in Apigee Edge 4.53.00](https://docs.apigee.com/private-cloud/v4.53.00/nginx-45300) and [Edge for Private Cloud on FIPS-enabled RHEL 8.X](https://docs.apigee.com/private-cloud/v4.53.00/fips-considerations-rhel-8). > [!NOTE] > **Note:** In Apigee Edge for Private Cloud 4.53.00, the methods for uploading private keys into Apigee keystores have been consolidated into one option. The only supported format for uploading private keys (or private key/certificate pairs) into Apigee will be PKCS12/PFX. > > If you have a private key and certificate file, you can use `openssl` to package them inside a PKCS12. For details and sample commands, refer to the [instructions on converting certificates to a supported format](https://docs.apigee.com/how-to-guides/converting-certificates-to-supported-format#packaging-pem-key-and-certificate-files-into-pkcs12pfx). > > If you have a JAR file, simply extract the JAR file to get the private key and certificate, and then package them into PKCS12. ## Supported software This release includes the following changes to supported software: | Support Added | No Longer Supported | |---|---| | This release adds support for the following software versions: - RHEL 8.10, RHEL 9, Rocky 9 and OEL 9 - Cassandra 4.0.13 - Python 3 - Nginx 1.26 | The following software versions are no longer supported with this release: - Cassandra 3.11.16 - Python 2 - Nginx 1.20.1 - RHEL 7 - CentOS 7 - OEL 7 | For a complete list of supported platforms, see [Supported software and supported versions](https://docs.apigee.com/release/supported-software). ## 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. > [!NOTE] > **Note:** The bug lists are primarily for users checking to see if *their* support tickets have been fixed. They are not designed to provide detailed information for all users. | Issue ID | Description | |---|---| | 352648971 | SNI Configuration for Non-Standard SSL Ports: The router now supports serving the configured fallback cert/key over non-standard SSL ports for clients that do not support SNI. Enable this feature by setting `conf_load_balancing_load.balancing.driver.nginx.fallback.server.nonstandard.ports.enabled` to true on router nodes. | | 321070652 | Fixed a bug that was preventing the edge-management-server from starting on FIPS-enabled RHEL 8. | | 362909723 | Upgraded the Postgres driver to version 42.5.5. | | 132680256 | PGP signatures added for all RPMs distributed via software.apigee.com. | ## Security issues fixed There were no security issues fixed in this release. ## Known issues See [Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud) for a complete list of known issues. ## Next step To get started with Edge for Private Cloud 4.53.00, use the following links: **New installations:** [New installation overview](https://docs.apigee.com/private-cloud/v4.53.00/installation-overview) **Existing installations:** [Update Apigee Edge 4.52.02 to 4.53.00](https://docs.apigee.com/private-cloud/v4.53.00/update-apigee-edge-45202-45300)