We don't have documentation to instruct user that they have the possibility to run into the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1365398 if they are using a shared aws account(as us) and didn't properly tag their instances. Given an aws account has different instances in different zones, it is vital that the user tag their instances with "Key=KubernetesCluster,Value=<clusterid>". Otherwise they may see their volumes provisioned in unepxected AZ.
Updated docs here: https://github.com/openshift/openshift-docs/pull/2783
The updates are already published at https://access.redhat.com/documentation/en-us/openshift_container_platform/3.6/html-single/installation_and_configuration/#available-dynamically-provisioned-plug-ins which contains following: For dynamic provisioning when using multiple clusters in different zones, tag each node with Key=kubernetes.io/cluster/xxxx,Value=clusterid where xxxx and clusterid are unique per cluster. In versions prior to 3.6, this was Key=KubernetesCluster,Value=clusterid.