README.md in elasticity-3.0.2 vs README.md in elasticity-3.0.3

- old
+ new

@@ -1,12 +1,12 @@ [![Gem Version](https://badge.fury.io/rb/elasticity.png)](http://badge.fury.io/rb/elasticity) -**(February 15, 2014)** Taking requests! I have a few ideas for what might be cool features though I'd rather work on what the community wants. Go ahead and file an issue! +**(April 10, 2014)** Taking requests! I have a few ideas for what might be cool features though I'd rather work on what the community wants. Go ahead and file an issue! Elasticity provides programmatic access to Amazon's Elastic Map Reduce service. The aim is to conveniently abstract away the complex EMR REST API and make working with job flows more productive and more enjoyable. -[![Build Status](https://secure.travis-ci.org/rslifka/elasticity.png)](http://travis-ci.org/rslifka/elasticity) 1.9.3, 2.0.0 +[![Build Status](https://secure.travis-ci.org/rslifka/elasticity.png)](http://travis-ci.org/rslifka/elasticity) 1.9.3, 2.0.0, 2.1.0, 2.1.1 Elasticity provides two ways to access EMR: * **Indirectly through a JobFlow-based API**. This README discusses the Elasticity API. * **Directly through access to the EMR REST API**. The less-discussed hidden darkside... I use this to enable the Elasticity API. RubyDoc can be found at the RubyGems [auto-generated documentation site](http://rubydoc.info/gems/elasticity/frames). Be forewarned: Making the calls directly requires that you understand how to structure EMR requests at the Amazon API level and from experience I can tell you there are more fun things you could be doing :) Scroll to the end for more information on the Amazon API. @@ -35,9 +35,14 @@ # Create a job flow with your AWS credentials jobflow = Elasticity::JobFlow.new('AWS access key', 'AWS secret key') # Omit credentials to use the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variables # jobflow = Elasticity::JobFlow.new + +# NOTE: Amazon requires that all new accounts specify a VPC subnet when launching jobs. +# If you're on an existing account, this is unnecessary however new AWS accounts require +# subnet IDs be specified when launching jobs. +# jobflow.ec2_subnet_id = 'YOUR_SUBNET_ID_HERE' # This is the first step in the jobflow - running a custom jar step = Elasticity::CustomJarStep.new('s3n://elasticmapreduce/samples/cloudburst/cloudburst.jar') # Here are the arguments to pass to the jar