AWS Elastic Beanstalk - How To Upgrade Existing Environment from Ruby 2.1 to Ruby 2.2 -

aws elastic beanstalk - cannot clone latest platform or eb upgrade ruby 2.1 ruby 2.2

i've been smashing head on one. in may, aws announced ruby elastic environments offer ruby-2.2 (e.g. ruby-2.2-(passenger-standalone) or ruby-2.2-(puma)). can't upgrade existing ruby-2.1 environments ruby-2.2. appears have recreate them completely...that seems silly? else out there experiencing this? missing simple?

extra information

i've been gleefully using ruby-2.1-(passenger-standalone) several months in staging , production environments. i'd upgrade them latest ruby-2.2 platform. aws documentation says pretty trivial, in fact of documentation appear state can use eb clone <env-name> --update. flag doesn't exist in eb cli 3.4.5 i'm using :( additionally, web console has clone latest platform option menu item, yet disabled.

it appears can latest ruby-2.2 instances create brand new environment scratch. that's tremendously annoying.

so here's i've tried...

$ eb status environment details for: staging   application name: xyz   region: us-west-2   deployed version: fbe7   environment id: someid   platform: 64bit amazon linux 2015.03 v1.4.3 running ruby 2.1 (passenger standalone)   tier: webserver-standard   cname: bla.bla.bla.elasticbeanstalk.com   updated: 2015-06-26 22:48:59.689000+00:00   status: ready   health: green 

great, confirms i'm using ruby 2.1. let's try upgrade:

$ eb upgrade environment on recent platform version. 

okay, that's nice, platform itself:

$ eb platform select appears using ruby. correct? (y/n): y  select platform version. 1) ruby 2.2 (puma) 2) ruby 2.2 (passenger standalone) 3) ruby 2.1 (puma) 4) ruby 2.1 (passenger standalone) 5) ruby 2.0 (puma) 6) ruby 2.0 (passenger standalone) 7) ruby 1.9.3 (default 1): 2 

so now, here's platform settings:

$ eb platform show current default platform: ruby 2.2 (passenger standalone) new environments running:  64bit amazon linux 2015.03 v1.4.3 running ruby 2.2 (passenger standalone)  platform info environment "staging": current: 64bit amazon linux 2015.03 v1.4.3 running ruby 2.1 (passenger standalone) latest:  64bit amazon linux 2015.03 v1.4.3 running ruby 2.1 (passenger standalone) 

so new environments take advantage of ruby-2.2 editions. that's great, have retire configured ruby-2.1 editions in lieu of newly created ruby-2.1 edition? come on?

i found solution this, using aws cli (not eb cli):

aws elasticbeanstalk update-environment --solution-stack-name "64bit amazon linux 2016.03 v2.1.0 running ruby 2.3 (puma)" --environment-name "dev-bg-123456" --region "us-east-1" 

the aws cli can installed homebrew:

brew install awscli