Using CFn auto-generated resource name in CFn template

[oonisim]

Problem

CloudFormation (CFn) has a limitation that when the AWS resource name is hard-coded, instead of letting CFn auto-generate, the updating the template and making change via changeset can fail as in https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-custom-name/.

While working on Netflix/metaflow#251, added p2/p3 instances to the CFn template and re-run the change set failed due to the limitation.

Request

Please consider letting CFn auto-generate the AWS resource names.