Is there a workaround to telling Juju to use a predefined security group on an AWS bootstrap? Due to permissions constraints/etc. our automation needs to work with predefined security groups that are made manually.
juju bootstrap --config vpc-id-force=true --config vpc-id=vpc-for-juju --to “subnet=subnet-for-juju” --constraints “security-group-ids=sgs-for-juju” aws
… would be ideal, but this is not the case.
Is there a workaround for this? Is there a manner to request the above? I believe this would be helpful for those working in constricted environments.