I am unable to reproduce this error in our upcoming 6.4.1 environment. when I drill into the JobServer instances, they all have a Name attribute which is set to the master stack name. They also have similar settings for other CFN attributes as tags. This may still be an issue in our current 6.3.1 release, but it looks like it will be fixed in 6.4.1.