VMware Tanzu Service Broker for AWS: Change default RDS instance creation Availability Zone after tile is being deployed

Products

• Cloud Services Products

Issue/Introduction

Users would like to change default RDS instance creation Availability Zone after VMware Tanzu Service Broker for AWS tile is being deployed.

Resolution

There are two places where you can configure the instance creation region and AZ in the tile, you can also specify the AZ at provision time.
 

From the tile

1. Default Region and Default Availability Zone in the AWS config tab in the tile. This will affect all service offerings.



2. specifically for RDS in the RDS Config tab. There you can specify what Default region and Default AZ override you want to use for RDS



Those would manage the defaults for all service offerings (1) and RDS specifically (2). If changing region also, you’ll have to make sure the Subnet group and Security groups specified in the RDS config are correct for the chosen region. And any change done in the tile needs apply changes to be performed in order for those changes to take place in the broker. This will update the broker, which will incur in some downtime for the broker (meaning, no provision/deprovision/bind/unbind/etc operations can be performed until the broker is back online).

In theory this doesn’t affect current service instances, bindings or service keys. The changes performed in the tile will affect only new instance creation. 

At provision time

If you’d like to change the AZ on an instance by instance basis instead, you can try passing it as a parameter at create time, for example:

cf create-service aws-rds-postgres basic my-test-2 -c '{"CreateDBInstance" : {"AvailabilityZone": "us-west-2b", "EngineVersion":"12"}}'