EC2_* style Amazon environment variables not consulted
Bug #1174874 reported by
David Britton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Ian Booth |
Bug Description
dpb@helo:.juju$ export |grep EC2
declare -x EC2_ACCESS_
declare -x EC2_SECRET_
dpb@helo:.juju$ tail ~/.juju/
# secret-key: <secret>
## https:/
aws:
type: ec2
admin-secret: 8125b1da537abcd
control-bucket: juju-878abcdefg
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/environme
This is on a src deployment bzr revno 1206
Changed in juju-core: | |
assignee: | nobody → Ian Booth (wallyworld) |
Changed in juju-core: | |
status: | Confirmed → Fix Committed |
Changed in juju-core: | |
milestone: | none → 1.11.1 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The environment keys that juju looks for for amazon credentials are: ACCESS_ KEY
AWS_ACCESS_KEY_ID
AWS_SECRET_
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=".. ." KEY=".. ." KEY_ID= "$EC2_ACCESS_ KEY" ACCESS_ KEY="$EC2_ SECRET_ KEY"
export EC2_SECRET_
export AWS_ACCESS_
export AWS_SECRET_