EMR will create and maintain rules for all managed security groups for master, slave and service access (when in private subnet). EMR will add all the required ingress and egress rules to the groups
When you specify managed security groups for a cluster, you must use the same type of security group, default or custom, for all managed security groups. For example, you can't specify a custom security group for the master instance, and then not specify a custom security group for core and task instances.
If visible_to_all_users is set to false, the cluster, after it's created, is not visible even to terraform
what
visible_to_all_users
totrue
why
EMR will create and maintain rules for all managed security groups for master, slave and service access (when in private subnet). EMR will add all the required ingress and egress rules to the groups
When you specify managed security groups for a cluster, you must use the same type of security group, default or custom, for all managed security groups. For example, you can't specify a custom security group for the master instance, and then not specify a custom security group for core and task instances.
If
visible_to_all_users
is set to false, the cluster, after it's created, is not visible even to terraformreferences