EC2_* style Amazon environment variables not consulted

[David Britton]

dpb@helo:.juju$ export |grep EC2
declare -x EC2_ACCESS_KEY="SECRET_KEY_HERE"
declare -x EC2_SECRET_KEY="ACCESS_KEY_HERE"
dpb@helo:.juju$ tail ~/.juju/environments.yaml
    # secret-key: <secret>

  ## https://juju.ubuntu.com/get-started/amazon/
  aws:
    type: ec2
    admin-secret: 8125b1da537abcdefg9b583d4
    control-bucket: juju-878abcdefg29b8d463a1
    default-series: precise
    #secret-key: "SECRET_KEY_HERE"
    #access-key: "ACCESS_KEY_HERE"
dpb@helo:.juju$ juju status
error: environment has no access-key or secret-key
dpb@helo:.juju$

If I uncomment the entries in the .juju/environments.yaml file, all works fine.

This is on a src deployment bzr revno 1206

[John A Meinel (jameinel)]

The environment keys that juju looks for for amazon credentials are:
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY

I think it would be reasonable to also look for EC2_ACCESS_KEY and EC2_SECRET_KEY, but you should be able to use the above two. In my config, I actually have:

export EC2_ACCESS_KEY="..."
export EC2_SECRET_KEY="..."
export AWS_ACCESS_KEY_ID="$EC2_ACCESS_KEY"
export AWS_SECRET_ACCESS_KEY="$EC2_SECRET_KEY"