Service Access Security Group: Besides the firewall settings mentioned in the 2 security groups mentioned. Internet traffic between AWS EMR
Service servers(you dont have any control over this, completely managed by AWS
) and your Slave EMR
instance, has to be allowed.
This security group contains 2 entries
HTTPS* (8443) TCP (6) 8443 ElasticMapReduce-Slave-Private(sg-id)
HTTPS* (8443) TCP (6) 8443 Default Security Group of VPC
Without this EMR
will not work with DataPipeline
. Neither Datapipeline
specifies a way to list this in pipeline definition. AWS
team is aware of this.
So, as a workaround please use the custom template provided by AWS
, and clone, edit accordingly to your needs.
Thanks, @blamblam for pointing that out. The previous steps assume, servers have already been created in the private subnets, and you need to allow communication automatically.
For launching in private subnet, we will include one more setting, Subnet Id
, this will launch your EMR in private subnets.
Hope, that helps.