juju-core (1.13) does not support the old pyjuju configuration variables
So I took the Go sources and tweaked a new region in
launchpad.net/goamz/aws/aws.go with the necessary API endpoints (GreenQloud).
Now juju bootstrap does not immediately say;
error: The AWS Access Key Id you provided does not exist in our records
Which it used to say immediately before making the change. Now it takes approx 15 seconds for it to give the same error. I added debug to
launchpad.net/juju-core/provider/ec2/ec2.go -> SetConfig() and verified that it is passed through ok.
Any hints on what else could be possibly making requests to Amazon API instead of the GreenQloud endpoints I specified?