Template for Existing VPC Creates Security Group in the Default VPC

[scothren]

The aerospike-cluster-workload.template.yaml template creates a 'PseudoRandom' Security Group in order to have a unique value to include in the AutoScale Group name. It is done this way to avoid a circular dependency.

This Security Group is created in the default VPC rather than the existing VPC where the rest of the resources will be deployed.

Can this be changed to create the Security Group in the specified VPC instead?

Relevant code is here: https://github.com/aws-quickstart/quickstart-aerospike/blob/main/templates/aerospike-cluster-workload.template.yaml#L423

Alternatively, could this random value be generated differently? Maybe the Stack ID could be used instead?
https://stackoverflow.com/questions/57660653/how-to-create-some-random-or-unique-value-in-a-cloudformation-template

[sourabh3b]

Thanks for opening the issue, let me check with PM and see if we can prioritize this issue and include in our roadmap.

[medavisjr]

I see now that it's a duplicate, but issue #72 that I just posted has some additional details if needed.