New versions and self-update support for Elasticache and RDS services

New versions are available for Elasticache and RDS services on Cloud.gov. Cloud.gov customers can also now update the versions of their services themselves, rather than needing Cloud.gov support to make these changes for them.

New versions for RDS

Version 16 for PostgreSQL databases is now supported and is now the default version for all PostgreSQL database plans.

See the RDS service documentation for more information.

Update RDS database versions

Updating the version of your RDS databases is now supported, whereas previously database version upgrades had to be performed by Cloud.gov support.

To update a MySQL database to version 8.4:

cf update-service ${SERVICE_NAME} \
    -c '{"version": "8.4", "allow_major_version_upgrade": true}'

To update a PostgreSQL database to version 16:

cf update-service ${SERVICE_NAME} \
    -c '{"version": "16", "allow_major_version_upgrade": true}'

See the RDS service documentation for more information.

New engines and versions for Elasticache

Valkey has been added as a supported engine for Elasticache services. Valkey 8.2 can now be specified as the target engine and version when creating or updating Elasticache services.

To create an Elasticache service using Valkey 8.2:

cf create-service aws-elasticache-redis \
    ${SERVICE_PLAN_NAME} \
    ${SERVICE_NAME} \
    -c '{"engine": "valkey", "engineVersion": "8.2"}'

See the Elasticache service documentation for more information.

Update Elasticache versions

Updating the version of your Elasticache service is now supported, whereas previously Elasticache version upgrades had to be performed by Cloud.gov support.

To update an Elasticache service to use Valkey 8.2:

cf update-service ${SERVICE_NAME} \
    -c '{"engine": "valkey", "engineVersion": "8.2"}'

See the Elasticache service documentation for more information.