auser/poolparty

security_group does not use the access_key and secret_access_key given to the using block

Opened this issue · 1 comments

Given:
using :ec2 do
access_key 'something...'
secret_access_key 'mysecret...'
security_group do ...

security_group fails with :access_key_id not given. It's trying to instantiate a new instance of EC2 instead of using the instance from the using block. If it's going to make a new instance it should at least use the keys given to the containing block. This problem is easy to reproduce if you do not set ENV['EC2_ACCESS_KEY'] in your .profile or on the command line.

I believe this is fixed. Right?