EMR instantiation will fail without explicitly specified subnet

rossf7 / elasticrawl

Launch AWS Elastic MapReduce jobs that process Common Crawl data.

MIT License

49 stars 13 forks source link

EMR instantiation will fail without explicitly specified subnet #25

Open e271828- opened 7 years ago

e271828- commented 7 years ago

I believe this will primarily affect newer AWS accounts. Elasticity supports ec2_subnet_id, so I've fixed this with pull #24 by allowing configuration of an explicit subnet ID.