There were changes introduced recently to make sure the service respected the
properties.system_database.external.validate_hostname.value in
p-runtime, but in doing so it seems there were some un-intended consequences such as this issue here.
There are 2 ways in which you can resolve this issue:
1. Uncheck
"Enable hostname validation" in the PAS tile under "Databases" and apply changes to the PAS tile.
2. For AWS RDS database you can add the AWS/RDS Root CA bundle to the
Bosh -> Security section of the BOSH tile.
The AWS/RDS Root CA bundle can be found here:
AWS SSL/TLS
1. Download the
CombinedCABundle pem file which includes the AWS RDS Root CA and all associated leaf certs.
2. Add the contents of the pem file to the Security tab in the BOSH Director tile
3. Apply Changes to BOSH Director and TAS tile. Once BOSH has updated the clock_global VMs with the new certificates, the push-usage-service errand should be able to connect to the RDS database.