You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On December 06, 2024, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.52.02 documentation](https://docs.apigee.com/private-cloud/v4.52.02)*
> - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - *[Edge for Private Cloud support timeline](https://docs.apigee.com/release/apigee-edge-release-process#apigee-edge-for-private-cloud-support-timeline)*
> - *Release notifications* : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications)

## 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](https://docs.apigee.com/release/notes/4520201-edge-private-cloud-release-notes#applying-multiple-patch-versions).

Updating this release will update the components listed below:

- apigee-cassandra-3.11.16-0.0.2585.noarch.rpm
- apigee-postgresql-14.5-0.0.2756.noarch.rpm
- apigee-qpidd-8.0.6-0.0.2533.noarch.rpm
- edge-analytics-4.52.02-0.0.40121.noarch.rpm
- edge-gateway-4.52.02-0.0.60260.noarch.rpm
- edge-management-server-4.52.02-0.0.60260.noarch.rpm
- edge-message-processor-4.52.02-0.0.60260.noarch.rpm
- edge-postgres-server-4.52.02-0.0.60260.noarch.rpm
- edge-qpid-server-4.52.02-0.0.60260.noarch.rpm
- edge-router-4.52.02-0.0.60260.noarch.rpm
- edge-mint-gateway-4.52.02-0.0.40465.noarch.rpm
- edge-mint-management-server-4.52.02-0.0.40465.noarch.rpm
- edge-mint-message-processor-4.52.02-0.0.40465.noarch.rpm
- apigee-setup-4.52.02-0.0.1139.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 <var translate="no">uName</var> and <var translate="no">pWord</var> are the username and password you received from Apigee. If you omit <var translate="no">pWord</var>, 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 Qpid nodes, execute the `update.sh` script:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c qpid -f configFile
   ```
4. On all Postgres nodes, execute the `update.sh` script:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c ps -f configFile
   ```
5. On all Edge nodes, execute the `update.sh` script for the `edge` process (including monetization):

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
   ```

## Bug fixes

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

| Issue ID | Description |
|---|---|
| 372070691 | Removed the redundant JNA library from Cassandra. |
| 362799717 | Fixed a failure in deleting cached data. |
| 361792608 | Fixed a bug where the presence of defunct schemas, such as *edgenotification*, was causing issues in Cassandra. |
| 361436097 | Added validation checks to Cassandra's `drop_old_tables` command to prevent execution if the Cassandra cluster contains multiple schema versions. |
| 370115540 | Resolved an intermittent failure when using the `setup.sh` script to install or configure Cassandra. |
| 375487499 | Restored the functionality of the rebuildIndex APIs. |
| 362909723 | Upgraded the Postgres driver to version 42.5.5. |
| 379179891 | Cassandra now sets the replication factor of system tables to match the cluster topology. |
| 381092556 | Added validations to check for the presence of directories in scripts across multiple components. |
| 372068460 | Set an Apigee-owned data directory as TMPDIR for Cassandra. |
| 373673550 | Improved the `wait_for_ready` action of QPID. |
| 360376605 | Fixed an issue preventing Edge for Private Cloud users in the AWS environment from using Monetization APIs. |

## Security issues fixed

The following is a list of known security issues that have been fixed in this release.
To avoid these issues, install the latest version of Edge Private Cloud.

| Issue ID | Description |
|---|---|
| 344961470 | Patched the QPID management portal to address an XSS vulnerability. |

## Changes to supported software

Support has been added for the following:

- Red Hat Enterprise Linux (RHEL) 8.10
- Oracle Enterprise Linux (OEL) 8.10

## Deprecations and retirements

There are no new deprecations or retirements in this release.

## New features

This section lists new features in this release.

| Issue ID | Description |
|---|---|
| 352648971 | Introduced a feature where the router serves the configured fallback cert/key over non-standard SSL ports for clients that do not support SNI. Enable this feature by setting the configuration `conf_load_balancing_load.balancing.driver.nginx.fallback.server.nonstandard.ports.enabled` to <var translate="no">true</var> on router nodes. Refer to [Using SNI with Edge](https://docs.apigee.com/api-platform/system-administration/using-sni-edge#supportingsniforrequestsfromedgetothebackend) for more details. |

## Known issues

See [Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud-known-issues)
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](https://docs.apigee.com/release/notes/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](https://docs.apigee.com/private-cloud/v4.52.02/installation-overview#local-repo).