1 Answer
- Newest
- Most votes
- Most comments
0
To make it user-friendly could you provide a list of friendly names of the different valid VPC, Subnet, SGs combinations then in the template use mappings to get the specific values in the resource definition. Also, the default friendly name could be "None" for networking, then you can use Conditions to control whether to include networking.
You could make it more dynamic by having the Friendly name be the stack name that created the network components and import those values using dynamic references.
Relevant content
- asked 6 years ago

Thanks for your answer. Problem is I don't have a list of VPC, Subnet, and SGs as these are varies depending upon the AWS Account as these accounts are third-party.
This is a good idea to use ListAWS::EC2::VPC::Id as this list out all available VPC but we cannot make it optional.