This topic describes the changes in this minor release of VMware Tanzu Service Broker for AWS.

For product versions and upgrade paths, see Upgrade Planner.

v1.4.20

Release Date: May 4, 2023

Resolved Issues

This release fixes the following issue:

  • There are no longer attempts to add an ACL to newly created S3 buckets, because AWS has blocked this behavior. As a side effect, the log delivery group is no longer added to the ACL.

Known Issues

This release has the following issues:

  • The help text for the RDS Aurora engine field incorrectly suggests using aurora_mysql with an underscore. The correct name is aurora-mysql with a hyphen.

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.19

Release Date: July 27, 2022

Resolved Issues

This release fixes the following issue:

  • Updates the Amazon Relational Database Service (RDS) Certificate Authority (CA) bundles for new regions and cloud offerings. The updated bundle includes all RDS CAs from AWS Commercial, AWS Gov, and AWS China regions.

Known Issues

This release has the following issues:

  • The help text for the RDS Aurora engine field incorrectly suggests using aurora_mysql with an underscore. The correct name is aurora-mysql with a hyphen.

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.18

Release Date: July 29, 2021

Features

New features and changes in this release:

  • You can configure extra binding URI parameters on MySQL, MariaDB, Aurora, and Postgres plans using the Additional custom query params on binding URI field. You can use these parameters as hints for application database connectors that are not properly connecting.

Resolved Issues

This release fixes the following issue:

  • You can now provision Aurora MySQL v5.7 and later instances. You must specify “aurora-mysql” as the engine name. AWS changed the name of the aurora engine starting in v5.7 compatible versions.

  • You can now provision Postgres v10 and later instances. AWS changed the naming convention of the parameter group family starting in Postgres v10.

  • Fixed an issue where you could no longer bind to SQL server instances. This issue occurred when the broker was pushed to a TAS for VMs with newer golang buildpacks, and was due to changes in go/sql standard libraries.

Maintenance Changes

Maintenance changes in this release:

  • Upgrades versions of all database driver libraries. These dependencies require a TAS for VMs foundation with a golang v1.14 and later buildpack. This is not considered to be a breaking change because Go v1.14 is already out of general support.

  • Extended End of General Support (EOGS) to February 28, 2022.

Known Issues

This release has the following issues:

  • The help text for the RDS Aurora engine field incorrectly suggests using aurora_mysql with an underscore. The correct name is aurora-mysql with a hyphen.

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.17

Release Date: June 8, 2021

Breaking change Switch to stemcell Xenial 621.x so that you are running on a stemcell that will be supported in the future.

Maintenance Changes

Maintenance changes in this release:

  • Extended End of General Support (EOGS) to December 31, 2021.

  • Validated compatibility with newer versions of Tanzu Operations Manager and VMware Tanzu Application Service for VMs including the long-term support (LTS) versions.

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.16

Release Date: February 3, 2020

Resolved Issues

This release fixes the following issue:

  • Fixes an issue where the Engine field on the RDS Config pane did not appear in Tanzu Operations Manager v2.7 and later. Because this field appeared in Tanzu Operations Manager v2.6 and earlier, the prior behavior is restored. However, you must not modify the Engine field because it is not supported.

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.15 - End of General Support

Caution This release is no longer supported because it has reached the End of General Support (EOGS) phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: January 31, 2020

Resolved Issues

This release fixes the following issue:

  • Fixes an issue where service plan fields did not appear in Tanzu Operations Manager v2.7 and later.

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

  • The Engine field does not appear in Tanzu Operations Manager v2.7 and later.

v1.4.14 - End of General Support

Caution This release is no longer supported because it has reached the End of General Support (EOGS) phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: November 14, 2019

Features

New features and changes in this release:

  • Added Amazon RDS 2019 Certificate Authority (CA) certificates. For instructions on how to update your CA certificates, see the AWS RDS documentation.

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

  • Some service plan fields do not appear in Tanzu Operations Manager v2.7 and later.

  • The Engine field does not appear in Tanzu Operations Manager v2.7 and later.

v1.4.13 - End of General Support

Caution This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: July 22, 2019

Features

New features and changes in this release:

  • Updates PCF Service Broker for AWS to use Cloud Foundry Command Line Interface (cf CLI) tool v6.45.0.

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

  • Some service plan fields do not appear in Tanzu Operations Manager v2.7 and later.

  • The Engine field does not appear in Tanzu Operations Manager v2.7 and later.

v1.4.12 - End of General Support

Caution This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: May 10, 2019

Features

New features and changes in this release:

  • Updates PCF Service Broker for AWS to use Xenial stemcells. Trusty stemcells are no longer supported.

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.11 - End of General Support

Caution This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: April 17, 2019

Resolved Issues

This release fixes the following issue:

  • Fixes an issue where using the latest Go buildpacks caused deployment of the broker to fail.

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.10 - End of General Support

Caution This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: November 28, 2018

Resolved Issues

This release fixes the following issue:

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.9 - End of General Support

Caution This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: August 3, 2018

Resolved Issues

This release fixes the following issue:

  • Fixes an issue when creating service keys with a Temporary Credentials Timeout during AWS configuration of the tile in Tanzu Operations Manager. If Temporary Credentials Timeout was a non-zero value, the timeout did not work because of changes in Amazon’s validation logic.

Known Issues

This release has the following issue

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.8 - End of General Support

This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: June 8, 2018

Features

New features and changes in this release:

  • The broker uses MySQL for PCF v2 when creating a backing store. Existing v1 databases are untouched and require manual migration

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.7 - End of General Support

This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: April 3, 2018

Features

New features and changes in this release:

  • Adds support for partition lookup when using custom endpoints.json
  • Allows a service to be unbound when the associated bind user no longer exists
  • Updates minimum stemcell version to 3468

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.6 - End of General Support

This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: February 13, 2018

Resolved Issues

This release fixes the following issues:

  • Fixes Oracle DB binding issue
  • Fixes Aurora DB instances not being created in specified VPC and subnets

Known Issues

This release has the following issue:

  • When creating an object with PostgreSQL, you must first assign the group’s role. For more information about this issue with object ownership, see Known issue with RDS for PostgreSQL.

v1.4.5 - End of General Support

This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: November 17, 2017

  • Updated minimum stemcell version to 3445
  • Updated blue-green deploy of broker to persist failed instances for debugging
  • Fixed issue where bind was failing for non-commercial AWS partitions
  • Fixed issue where create-service-key was failing for non-commercial AWS partitions due to incorrect ARN format
  • Fixed issue where create-service-key was failing for accounts containing 100 or more policies
  • Added RDS CA certificates for ca-central-1, us-east-2, eu-west-2, ap-south-1, us-gov-west-1, and cn-north-1

v1.4.3 - End of General Support

This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: October 12, 2017

  • Fixed Service Broker deployment issue when using MySQL v5.6.x

v1.4.2 - End of General Support

This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: August 11, 2017

This version requires Go Buildpack v1.8.3 or later and stemcell 3363.29 or later.

  • Fixed default MySQL privileges and change grants on other MySQL compatible databases
  • Fixes for C2S (Certificate, Regions)
  • Added region for GovCloud
  • Updated Regions dropdown for new regions

v1.4.0 - End of General Support

This release is no longer supported because it has reached the EOGS phase. To stay up to date with the latest software and security updates, upgrade to a supported version.

Release Date: June 26, 2017

This version requires Go Buildpack v1.8.3 or later and stemcell 3363.25 or later.

  • The service broker can use an HTTP/HTTPS Proxy, configured in Tanzu Operations Manager settings
  • Encryption can be enforced on S3 buckets through a policy setting
  • Updated golang version to 1.8
  • Upgraded to the latest AWS Golang SDK v1.8.19
  • Updated to the 3363 stemcell
  • Fixed the default custom privileges on PostgreSQL service plans for upgrades
check-circle-line exclamation-circle-line close-line
Scroll to top icon